3 ms·
> most of the interesting bits of Self were left by the wayside in the process A short summary of those interesting bits would be a nice read for us JS devs :)
by AriaMinaei 7y ago
> most of the interesting bits of Self were left by the wayside in the process
A short summary of those interesting bits would be a nice read for us JS devs :)
- kerkeslager 7y agoYou should check out JavaScript: The Good Parts by Douglas Crockford. I'm not sure about later editions, but the first edition, published in 2008, predates a lot of the changes which left behind the better features of Self. The last 10 years have seen a large influx of users who didn't ever bother to grok the older feature set of JavaScript, and demanded features they had learned in Java and other languages (i.e. class-based inheritance) and language developers have obliged. The result is a language with both systems, and there's enough inconsistencies between the two that it doesn't make sense to use both in the same codebase. My advice would be to stick with the class-based features that are more common/popular today because your coworkers will be familiar with them: mixing in prototypical and class-based systems will just result in an incoherent system. Learn the Self features because they're interesting, but be very cautious about introducing them into modern JS codebases.