then again, i'm just trying to become an all-around better fullstack developer for my current employment situation - so i'm mostly using (and pull-requesting) frameworks rather than writing my own
given this perspective, i'm much more interested in the entire [and rapidly expanding] toolchain for modern js development - and learning the language's esoterica [and i am the sort of person who takes pleasure that stuff] as i become an all-around better js dev
This book isn't about the edge cases of how `==` works or how `>` works when comparing objects of different types. It's about the fundamentals of the language and the idioms and how to write effective code using them.
If you already know JS very well you can skip it or skim it - but if you're a 'framework developer' as a reader I guarantee that it will be worth your time. If your JS is already very good - you might want to consider spending your time learning another language or technology rather than being "more great" at JS unless you want to get involved in the specification process.
Well, depends how you define "master". To become a leading expert on it would mean taking time away from other skills, which probably wouldn't be wise. But if you're using JS quite a lot then learning it to an arbitrary level, let's say 80% of "master", well, that probably would be a good shout.
I suppose it depends on your skillset projection, do you see yourself spending a lot of the next five years with JS? If so, invest now in personal development. If not, maybe skim read it.
If you're going to make JS your primary language that you write on a daily basis, doesn't it make sense to invest more time into learning it than just whatever you might accidentally pick up through trial-and-error?
Most developers in most other languages do tend to take formal learning of the language, to a deep extent often, a more serious task, but with JS it seems many developers just kinda get whatever they get along the way.
I have found that approach to be good at getting and keeping yourself employed, but bad at giving you any confidence that you actually know what's going on. If you aren't really sure exactly why your code works, my theory is that you'll never know exactly why your code doesn't work either.
I'm just trying to provide resources for developers who want to take learning JS seriously, and challenge "all" of us to ask, "just how much DO I know JS?" The rest is up to you. :)