In your opinion, what is the most confusing part of JavaScript?
Tomasz Łakomy
・1 min read
Classic DEV Post from Dec 13 '18
107
25
CSS frameworks are either opt-in or invasive - why not "regional"?
Jesper Høy -
How do you set up a productive team despite management's interference?
Ayobami Ogundiran -
Has anyone used Eclipse Che? What are the main pros and cons you encountered?
Periklis Gkolias -
How would you build a desktop app nowadays?
Avalander -
Trending on 
How To Be A Good Software Engineer Mentor
Protecting your freelance work
Improving your Git workflow
10 simple Linux tips which save 50% of my time in the command line
What was your win this week?
Redesigning My Portfolio Site
What would your opinion be of a "reading position" indicator on DEV?
What Does Your IDE/Code Editor Look Like?
Auth With Twitter
Auth With GitHub
this
When I started writing JS it was hard to get an understanding of what
prototypeis and how it's used.Type coercion is definitely not obvious in JavaScript
IMHO, don't ever ever ever use
==in JavaScript. Always use===instead and forget about type coercion; just explicitly type-cast anything you need to.It's a very rare case when you work on a project alone. Other developers can use == and it's necessary to understand how type coercion works.
I agree that most of developers consider == as evil. But Kyle Simpson (You don't know JS author) don't hate type coercion. Moreover, he recomments to use == where necessary.
Source.
Closures. It's a complicated subject involving an understanding of how the execution context works and how variables are scoped and held within the JavaScript engine. It takes a lot of practice and theory for closures to finally click. It took me like six months to finally grok it.
Javascript has a lot of layers. Understanding what is controlling each piece can be hard to parse if you're new. I actually wrote something on this a while back.
The Layers of Javascript
Laurie ・ 3 min read
typeOf null = 'Object'
Newest confusion is parseInt. Just try and see what happens if you do
parseInt(0.000000347)The ecosystem. Every time I come back to JS the tooling is entirely different. Makes it frustrating to get things done.
How come they didn't actually go with 'smoosh'?
I have a few things that I considered confusing when I started learning JS..scope, hoisting, closures, callbacks
The ecosystem around it