(untitled)

Is there an updated list of good resources to learn Javascript well in the current year? References like Javascript: the good parts seem to be good but the language has seen several massive reworks since then so I assume that the list of good parts has changed. Also it predates the growth of big frameworks, which are really daunting for a beginner. Assume some experience with other programming languages, i.e. being well aquainted with both functional, OO, and procedural languages, and openness to learn language features rigorously (as a compiler designer would).

https://developer.mozilla.org/en-US/docs/Learn There.

I think you're looking for Eloquent Javascript: https://eloquentjavascript.net/ >Also it predates the growth of big frameworks, which are really daunting for a beginner. If you want to learn JS, the frameworks are irrelevant and you should avoid any general resource that focuses on them. Do not learn JS by learning to make a React application.

>>9177 +1 for "Eloquent Javascript", that should be the first JS book you read. After that "Javascript, the Definitive Guide" should be your second. >If you want to learn JS, the frameworks are irrelevant and you should avoid any general resource that focuses on them. Do not learn JS by learning to make a React application. I agree you have to learn vanilla JS to do DOM manipulation but I dont think there is any harm in taking a look at how jQuery and how frontend frameworks work just to get an idea of what you will eventually use.

>>9177 What about You don't Know JS series?

>>9169 The problem with only learning "the good parts" of JS is that you don't gain any understanding of why those parts do what they do, which can be a big headache when you have to read code that defines the subset of the language constituting its "good parts" to be different from the one you're familiar with. I highly recommend this series: https://github.com/getify/You-Dont-Know-JS YDKJS is the only book I've found about javascript that actually explains the navigation of and reasons behind the design choices that led to it becoming the giant, malformed creature it is today. Just a few caveats to consider while reading: 1) The author asserts that using `==` instead of `===` for comparisons makes perfect sense, contrary to standard usage. This is wrong because even if you fully understand `==` type coercion, it will still be unintuitive to everyone else reading your code, and is much harder to guard fully against unintended behavior in code that has to be maintained and edited later. 2) There are even newer versions of javascript since ES6 "and beyond", which include some important features the author barely touches (namely,

You can do yourself a solid and learn TypeScript down the road.

>>9396 Feel free to include resources on how to learn TypeScript.

>>9396 >>9403 This. Any good books on Typescript?

>>9404 The TypeScript HandBook is pretty good if you're already familiar with programming. http://www.typescriptlang.org/docs/home.html

If you do decide that you want to learn a framework at some point though, what would you recommend from a pure jobs perspective? React? I'm mostly learning Javascript to round off my skillset and become a bit more employable, or generally to be able to make a nice web frontend for things that I've written. The languages that I've had the most practical experience with are Python, Haskell, C++, and Julia (along with some minor messing around with Lisps and smalltalk).

to be honest as a Haskeller I'd probably be more likely to use purescript instead of typescript. Typescript looks nice, but from reading about it, I think I'd get an uncanny valley effect from the unsound & partial type system. I honestly prefer dynamic typing to an unsound static type system.

>>9440 Don't dismiss things just because you don't like the sound of them. I've also done a lot of Haskell and OCaml and yes, TypeScript's type system isn't entirely satisfactory or correct in some cases, but it's a massive improvement over plain JS and I can guarantee that you won't miss soundness nearly as much as stuff like ADTs and newtypes. If you only use libraries written in TS or that provide type declarations (all of the popular ones do) and compile with the --strict flag you won't even notice the optional typing cruft.

Have some books, Lainon

>>11680

>>11700 Well, I was going to post the rest of these books but they aren't uploading. I just get a blank post instead. Nice job, Appleman...

>>11701 Please provide more information in the bugs thread in /q/

>>9169 hi, is Head First JS Programming a decent book?

>>9169 Why do you want to know js? If you are a career comfy in other languages and just want to know what js is like the. YDKJS books offer nice insights, as many others have recommended. However if you need to be productive in JS you will be forced into choosing a framework and learning it straight after the basics.

>>9177 I am sorry but Eloquent JavaScript is deprecated

>>9177 Came here to post this. Very well written and with good practices that I still use to this day, I'm just not sure if it covers ES6 too well, but it's great for the basics. Also after that I recommend this one if you fancy some functional programming. https://mostly-adequate.gitbooks.io/mostly-adequate-guide/content/ >>13177 Why do you say that?