|
|
|
|
|
|
by FLUX-YOU
3140 days ago
|
|
|
>Can you/anyone give me 3 solid cases where the flaw was in javascript and not the programmers understanding of the language ? I can't. These were problems in various stages of JS's history, but not necessarily now: Browser differences in javascript by not having a good specification or strong governing body. Not having block-level scope despite convention in other C-like languages. Optional semi-colons. typeof inconsistencies. Another problem with JS changing so much is developers picking up the language at various points in that development. |
|
|
Its the browser implementation that was at fault. The ambiguity in specs was and is minimal to negligible for the past 8 years (since I started following). But like you said, not relevant today.
> Not having block-level scope despite convention in other C-like languages. > Optional semi-colons.
Its a feature, not a bug!
> typeof inconsistencies.
Maybe. Never faced it.
> Another problem with JS changing so much is developers picking up the language at various points in that development.
What I see constantly changing is JS frameworks and preprocessors, not the language itself. Newer folks tend to learn some JS framework first before the language itself (just like I did) and the constant change can hurt and impede progress and confidence. The language itself has been well documented and forgiving in my experience.
So yeah, point taken. You do not like JS. I do. Let's make peace with that.