I'd seen these posted before and remember thinking how good they looked and then promptly forgot enough I've not been able to find them again.
Some thoughts / constructive criticism: Why would I be incentivized to get the full ES7 book when there are already quality materials out there for me for free (i.e. ponyfoo's articles are amazing).
In contrast, I was very attracted to the article on building a list - it's pretty unique and shines a light on interesting CS & JS concepts.
My theory is that building an audience for a site like this is a mix of niche content and mass appeal content. I honestly have no idea what that mix is yet and what type of content to focus on, still figuring that out. Your feedback is massively appreciated! It will without a doubt influence the direction I take the site in!
As far as the value of this book over other resources, I would say the main separating factor is my writing style. If you like non-serious writing that leans much more towards helping you grok concepts than technical correctness then you will enjoy it. There is no stuff like "A monad is just a monoid in the category of endofunctors" to be found within my writing. Also there are lots of references :)
Thanks again for the feedback!
* Learn why ES6 modules are static and why its awesome
* Learn how to generators can be used to manage promises
On day 9 you will learn how to leak memory with closures.
On day 10 you will learn how to do unsafe numeric operations with IEEE 754 floating point precision numbers.
On day 11 you will learn that the pseudorandom generator in JS is VM specific and may not be secure.
On day 12 you will learn to leak memory by binding functions.
On day 13 you will learn to add timeouts to asynchronous operations so they don't last forever.
On day 14 you will learn what the floating point epsilon is and how number comparisons are unreliable.
anyways lol some of that is too real
jokes aside I think web development has come a long way and JS gets a bit of a bad rep. Full stack JS is insanely productive as a stack when you consider what you can build with it. It might be buggy and make you say "wat?" a lot but in exchange you can build insanely complex apps in timeframes that used to be the stuff of dreams. Granted many times what we build has no need to be so insanely complex, but when we really need it JS is there to make complicated things just magically easy to build.
Testing assumptions help, be it through quick REPL experimentation or a unit test.
Insanely complex apps on a buggy foundation? What could possibly go wrong...
On a more serious note, I know ruby, but I really want to learn JS - is this a good place to start? Or, is there a better place to start, and then come back here?
I'd recommend you check out other resources first then comeback. I highly recommend the You Don't Know JS books https://github.com/getify/You-Dont-Know-JS
You can easily run ES6 code in nodejs - http://stackoverflow.com/questions/36417585/how-to-execute-e...
(and obviously in everything else like reactjs, etc)