3 ms·
An implementation of classes with prototypes: http://journal.stuffwithstuff.com/2010/08/01/class-in-the-front-proto-in-the-back/ http://journal.stuffwithstuff.
by matheusmoreira 7y ago
An implementation of classes with prototypes:
http://journal.stuffwithstuff.com/2010/08/01/class-in-the-front-proto-in-the-back/ http://journal.stuffwithstuff.com/2010/08/01/class-in-the-fr...
- deleted 7y ago[deleted]
- masklinn 7y ago> This is the best of both worlds: prototypes are easier for the language implementer to code and classes are easier for the user to use. Of course you also get the worst of both worlds: the performances of prototypes and the split world of classes.
- munificent 7y agoAlso true!
- jonnytran 7y agoCan you explain how this is so much different in terms of performance? Since users doesn't have direct access to the prototypes, they're not doing arbitrary manipulation or creating long chains of them.
- wool_gather 7y agoNote for completeness, that blog is by the author of this book.