3 ms·
Has anybody read this book? I'm curious about the quality. It's one of those things that could either be really great or really misguided.
by brundolf 5y ago
Has anybody read this book? I'm curious about the quality. It's one of those things that could either be really great or really misguided.
- hparadiz 5y agoReferencing the few areas of it where I have domain knowledge I'm impressed. Lots of really good info. If nothing else it's a great starting point for research on various topics.
- pacomerh 5y agoAxel Rauschmayer has been writing JS books for a while, he's quite knowledgable. I would recommend
- amalive 5y agoHaven't read it but since it from the same author who writes these 'to the point' blogs - https://2ality.com/ https://2ality.com/ I believe the quality would be good.
- xer0x 5y ago+1 it looks great.
- sparsely 5y agoI glanced through it and it has some interesting stuff, but I suspect you'll write better code in 99% of jobs if you don't read it, and don't know about most of the techniques described
- welly 5y agoWhy do you think this? I'd be interested as to why you came to this conclusion.
- RobertKerans 5y agoYeah, it's good. Working with with learners, I always recommend his books (particularly the ES6 one) as reference once they're past the basics. He's very good and not someone who disseminates much information that isn't just practical explanations of and realistic usecases for spec. Slightly dry, but very concise. This one's [naturally] slightly more in depth, but it's IMO a necessary addendum to previous books/articles -- something that builds on them for slightly advanced usecases. Sibling comment says you'll write better code in 99% of jobs if you don't read it: I don't think that's true at all. Deep copying, for example isn't uncommon.