3 ms·

"Unlike method invocation, inheritance violates encapsulation" Item 16 of Effective Java 2nd Edition. To the original article, I would improve the wording so th

by xixixao 13y ago

"Unlike method invocation, inheritance violates encapsulation" Item 16 of Effective Java 2nd Edition. To the original article, I would improve the wording so that it is clear whether the author is against class hierarchies in Javascript or classes in Javascript. It is not clear to me. One practical example: In Javascript (CoffeeScript), null values can propagate for a very long time. Calling a non-existent method throws an error immediately, while using a nonexistent field (because it changed in the super class) is not that easy to track down. From my CoffeeScript experience, almost any inheritance brought us a headache when we rapidly iterated on our code - but that doesn't mean that CS class construct isn't useful in defining recipes for well-encapsulated objects.

a3n 13y ago
Aside: Your invocation of Effective Java made me look for Effective Javascript, and it does exist. Amazon users give it five stars: http://www.amazon.com/Effective-JavaScript-Specific-Software-Development/dp/0321812182 http://www.amazon.com/Effective-JavaScript-Specific-Software... Can anyone comment on how well this books fulfills the expectations implicit in a book calling itself "Effective X?" Or just how effective the book is with respect to accepted javascript practice?
- dangoor 13y ago
  I haven't personally read it (shame on me!) David Herman and I spoke from time-to-time while I was at Mozilla and he's very smart, a very clear communicator and he knows the language as only a language lawyer can. He's actually a member of TC-39 (the ECMAScript committee) and had a big hand in the modules coming in ES6. By every account I've seen, it's a great book and the only reason I haven't read it is that I've already been bitten by all of JS' pitfalls once or twice :) The real reason I'm posting a comment, though, is to give you a link to the JS Jabber episode in which they talk to Dave about the book: http://javascriptjabber.com/044-jsj-book-club-effective-javascript-with-david-herman/ http://javascriptjabber.com/044-jsj-book-club-effective-java... That episode will give you a good idea of what the book is like.
- geekingfrog 13y ago
  It's a very good book. It explains a lot of 'why' and inner working of good practices. It's also fairly comprehensive, ranging from - some evilness (type inference with ==, eval and its performance toll) - functions and higher order functions - objects and prototypes. Some good explanations of the all prototype and constructor thing - array, dictionnary and some things to know about their prototypes - api design and concurrency It's 200 pages full of content, I recommend it.

by xixixao 13y ago

a3n 13y ago

Aside: Your invocation of Effective Java made me look for Effective Javascript, and it does exist. Amazon users give it five stars: http://www.amazon.com/Effective-JavaScript-Specific-Software-Development/dp/0321812182 http://www.amazon.com/Effective-JavaScript-Specific-Software... Can anyone comment on how well this books fulfills the expectations implicit in a book calling itself "Effective X?" Or just how effective the book is with respect to accepted javascript practice?

dangoor 13y ago
I haven't personally read it (shame on me!) David Herman and I spoke from time-to-time while I was at Mozilla and he's very smart, a very clear communicator and he knows the language as only a language lawyer can. He's actually a member of TC-39 (the ECMAScript committee) and had a big hand in the modules coming in ES6. By every account I've seen, it's a great book and the only reason I haven't read it is that I've already been bitten by all of JS' pitfalls once or twice :) The real reason I'm posting a comment, though, is to give you a link to the JS Jabber episode in which they talk to Dave about the book: http://javascriptjabber.com/044-jsj-book-club-effective-javascript-with-david-herman/ http://javascriptjabber.com/044-jsj-book-club-effective-java... That episode will give you a good idea of what the book is like.
geekingfrog 13y ago
It's a very good book. It explains a lot of 'why' and inner working of good practices. It's also fairly comprehensive, ranging from - some evilness (type inference with ==, eval and its performance toll) - functions and higher order functions - objects and prototypes. Some good explanations of the all prototype and constructor thing - array, dictionnary and some things to know about their prototypes - api design and concurrency It's 200 pages full of content, I recommend it.