Proper error handling (mostly writing code that doesn't fire errors).
Being unable to fully understand or explain the 2 pillars of Javascript: Functional programming & Object Oriented Programming.
How important it is to refer to the bloody documentation before hopping on stackoverflow.
That not all tutorials, all books and all individuals relay accurate and most up-to-date information.
bind(), call() and apply()
High-order array functions like map() and specially reduce(). (It's very rare to see beginners use reduce() at all).
The this keyword and I don't really know why but some beginners tend to find it difficult why you call super() inside the constructor of a child class.
The Shadow DOM, it's not something you'd expect someone to know but it's ideal to learn about it after learning about the DOM and DOM manipulation.
Promises, the for/of loop, async/await , callbacks etc. etc. or writing asynchronous code, and handling/catching errors properly.
Destructuring and Spreading.
Garbage Collection.
Closures.
That stackoverflow is the solution to all your problems.
I think that's a pretty constructive list of the common and more difficult things that beginners don't really know or can't understand. Some of them don't have to do anything with JS but hey!
firefox devtools got really fast too and they also have a memory profiler. however, recently i had a lot of issues with the firefox devtools (code continuing to run while being paused at a breakpoint, leading to variable hovers showing different values every time you hover them, breakpoints vanishing) and it's missing some features the chrome devtools have (event breakpoints, dom manipulation breakpoints etc.)
Fair enough. Both of those features are things I'm not terribly skilled at evaluating — a personal shortcoming, certainly — but for what it's worth I just checked Firefox and it has panels for both.
I have to be honest I find the Chrome dev tools kind of bewildering to look at, at least at first glance. It does seem to be better about error reporting though — the one time I do use it is if I’m not getting clear messages in FF, sometimes Chrome will help.
Being unable to fully understand or explain the 2 pillars of Javascript: Functional programming & Object Oriented Programming. one more thing that probably fits into #4 of your list: the prototype chain
true, but i think it's worth mentioning that OOP in JS is vastly different from OOP languages such as e.g. java. understanding the concept of the prototype chain is imo more important than learning the syntactic sugar keyword class and what it does (i agree a lot with kyle simpsons opinion on this, it's very misleading for people coming from different programming languages)
it's very misleading for people coming from different programming languages
Depends on which different language we're talking about. JavaScript's classes work surprisingly similar to Python's or Ruby's classes. JavaScript and Python classes side-by-side
45
u/Mydrax May 28 '19 edited May 28 '19
The importance of using the Chrome DevTools.
Why Linters make your life easier.
Proper error handling (mostly writing code that doesn't fire errors).
Being unable to fully understand or explain the 2 pillars of Javascript: Functional programming & Object Oriented Programming.
How important it is to refer to the bloody documentation before hopping on stackoverflow.
That not all tutorials, all books and all individuals relay accurate and most up-to-date information.
bind(), call() and apply()
High-order array functions like map() and specially reduce(). (It's very rare to see beginners use reduce() at all).
The this keyword and I don't really know why but some beginners tend to find it difficult why you call super() inside the constructor of a child class.
The Shadow DOM, it's not something you'd expect someone to know but it's ideal to learn about it after learning about the DOM and DOM manipulation.
Promises, the for/of loop, async/await , callbacks etc. etc. or writing asynchronous code, and handling/catching errors properly.
Destructuring and Spreading.
Garbage Collection.
Closures.
That stackoverflow is the solution to all your problems.
I think that's a pretty constructive list of the common and more difficult things that beginners don't really know or can't understand. Some of them don't have to do anything with JS but hey!