You-Dont-Know-JS

The way to handle this case is to use Promise.race with 2 promises. The first promise is your logic. The second promise is rejected after a timeout. For more detail read the section "never calling the callback" from "you don't know js" book on "async" in chapter 3 https://github.com/getify/You-Dont-Know-JS/blob/master/async...

* Video: Practical JavaScript. I haven't gone through this myself but I've heard good things. https://watchandcode.com/p/practical-javascript * Comprehensive lesson-based: FreeCodeCamp. An easier, piecemeal option with plenty of hints and guides. Disclosure: My business partner is the CTO of FCC https://www.freecodecamp.com/ * Video: JavaScript30 by Wes Bos. 30 Vanilla JS Challenges. Wes is a fantastic teacher and this is his newest series. I haven't gone through it myself but I've taken his other lessons and been pleased, so I feel somewhat confident in recommending this. https://javascript30.com/ * You don't know JS: A series of free lessons on JS https://github.com/getify/You-Dont-Know-JS * $ Book: O'Reilly JS Pocket Reference. If you already know how to program, this can help you understand JS in a very short amount of time. Obviously

https://github.com/getify/You-Dont-Know-JS A series of 6 small books that cover the JS fundamentals in detail.

I keep a big list of links to high-quality tutorials on React and related topics ([0]). As part of that list, I have a page of links to Javascript learning resources ([1]). In particular, I highly recommend "Eloquent Javascript" ([2]), "You Don't Know JS" ([3]), and everything ever written by Dr. Axel Rauschmayer ([4]). [0] https://github.com/markerikson/react-redux-links [1] https://github.com/markerikson/react-redux-links/blob/master... [2] http://eloquentjavascript.net/ [3] https://github.com/getify/You-Dont-Know-JS [4] http://exploringjs.com/

Do not do this. Do not listen to anyone calling JavaScript a "chaotic disaster zone", or engaging in any such 1990s style language-wars childishness. I spent years programming C# before switching to JS, and it took me a long time to stop thinking in a object-oriented way and embrace the functional style that works best with JavaScript. If you want to learn JS and be a good JS programmer, you are best learning JS, not some other language. That's basic common sense. A great place to start is with the "You Don't Know JS" book series, which are all available online, for free: https://github.com/getify/You-Dont-Know-JS.

Nice, I'm going to jump strait into this then. Thanks! I did find the You Don't Know JS[0] book series extreamly helpful as a C++/Python coder who has only done enough JS to get by. But that is the extent of my prep for learning React Native. Interestingly, the YDKJS author (Kyle Simpson) is very down on the adoption and heavy usage of ES6 class notation and the over-reliance of the syntactic appearance of a OO-language class systems in JS. His argument is the abstraction will leak the in-its-own-right powerful delegation system of JS prototypes, so why not just learn/use raw objects or his OLOO (objects-linked-to-other-objects) pattern. I find it hard to mentally map the ES6 class to the equivalent object+prototype structure it is syntax sugar for, so just throw my hands up and for the most part pretend they are Python style open-objects

These are awesome for JS: https://github.com/getify/You-Dont-Know-JS

I've found the 'You Don't Know JS' series very helpful for understanding JS from the ground up. In book form or for free via !gh, https://github.com/getify/You-Dont-Know-JS.

That book definitely gave me a leg up on JavaScript, but I feel the real "ah ha!" moment came with this book, "You don't know JS, Scope and Closures". I can't recommend this book enough. https://github.com/getify/You-Dont-Know-JS/tree/master/scope...

The book from the "You Don't Know JS" series is very thorough: https://github.com/getify/You-Dont-Know-JS/tree/master/es6%2...

neat series of books. thanks for the tip https://github.com/getify/You-Dont-Know-JS

> functional languages get an amount of attention disproportionate to their usage and even this article is example - using js wouldn't get to the top of hn JavaScript topics do make it to the front of HN. For example, https://github.com/getify/You-Dont-Know-JS was the top article on June 24. If you mean that simply writing about using JavaScript without any particular angle probably wouldn't make it to the front page, you're right. But that's actually proportionate to the two languages' usage. It's similar to how "I drank some water" is less interesting than "I drank a rare Japanese whiskey" — absent of context, they're equivalent, but because everyone has done the former, the fact that you did it too is boring on its own.

Thank you for your recommendation. Do you know if the github repo include the entire content? https://github.com/getify/You-Dont-Know-JS

I do think it is meant to be a catchy marketing play on "You Don't Know X" but the author also describes it as a reference to the fact that "knowing" JavaScript can only ever be temporal: No matter how much you feel you've mastered JavaScript to this point, the truth is that JavaScript is never going to stop evolving, and moreover, the rate of evolution is increasing rapidly. This fact is almost a metaphor for the spirit of this series, to embrace that we'll never fully know every part of JS, because as soon as you master it all, there's going to be new stuff coming down the line that you'll need to learn.[1] [1] From Ch. 3 "Into YDKJS" of the first book Up & Going: https://github.com/getify/You-Dont-Know-JS/blob/master/up%20...