https://www.linkedin.com/pulse/code-jav ... le-comment" onclick="window.open(this.href);return false;
Ничего святого блин нет, устроили какое то Judge Judy из серьезного предмета. А судьи кто? (С) Вот такие вот дуры беспросветные
For the record, I have seen no indication that Annette understood a word of my API design talk, which she quotes out of context in this post (OOPSLA 2006 invited talk; http://www.oopsla.org/2006/program/sess ... _bloch.htm" onclick="window.open(this.href);return false;). It takes creativity to design a good API, but the results of the design effort are a functional artifact. Also, she would do well to read my followup talk on the history of the API (SPLASH 2014 invited talk; http://2014.splashcon.org/event/plateau ... josh-bloch" onclick="window.open(this.href);return false;). In it, I explain that we (computer professionals) have always been free to reimplement each others' APIs without the consent of their creators, and how this has been crucial to the development of the field. A world where we did not have this freedom would be a nightmare for computer professionals. in place of interoperating components, we'd have proprietary silos, and it would be nearly impossible to compete with a strong incumbent. Progress would slow to a snail's pace. I hope I never live in such a world. Annette makes a fundamental error in her post: APIs are most definitely *not* code. They are abstract specifications that may be expressed in code in conjunction with prose or formal mathematics. Their sole function is to define a method of operation whereby one component of a computer system can operate another. Annette would also do well to take a look at the EFF's "Computer Scientist Brief" of November 7, 2014 (https://www.eff.org/files/2014/11/07/go ... _final.pdf" onclick="window.open(this.href);return false;) and to discuss its list of signatories with any competent computer scientist. It's not just a bunch of famous people; it's the founding fathers (and mothers) of our profession. In my experience the views set forth in this comment are overwhelmingly shared by my peers, in corporate R & D as well as academia.