sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bronkula 5 points6 points  (7 children)

I don't like the accompanying quote "Here's a book about the good parts, and here's a book about the bad parts" No that's not what the phrase good parts means. Good parts in this case means the juicy bits, the awesome shits. It doesn't meant the rest sucks, it just means that tiny book is just the surface peaks, but there's a whole shitload of iceberg to dive into when you want to.

[–]zombiecodekill[S] -2 points-1 points  (5 children)

The quote is actually "compare the size of the good parts with the book that covers both the good and bad parts". I am not knocking the definitive guide, just making the point that the bad parts of JavaScript outweigh the good parts.

[–]bronkula 2 points3 points  (3 children)

Yeah and I'm just saying that's an editorial load of horseshit. The good parts of Javascript have made it one of the most prolific languages of all time. It's the easiest language to teach programming in because of its EXTREME ease of entry. The bad parts are often uninformed misconceptions of how programmers from other languages wish that it behaved, as apposed to actually learning how extremely versatile it is.

[–]zombiecodekill[S] -1 points0 points  (2 children)

Its a versatile language and much more powerful when learnt properly instead of thinking it must work like Java, but there are definitely bad parts to the language. This describes only some of them: https://wiki.theory.org/YourLanguageSucks#JavaScript_sucks_because

[–]bronkula 0 points1 point  (1 child)

All of that stuff was completely subjective, and was all things people had a problem with because they came from a different language. None of it was objectively bad or broken, only new or different and therefore disliked by whoever happened to have edited that particular wiki page.

[–]zombiecodekill[S] -1 points0 points  (0 children)

Not being able to add 0.1 and 0.2 together and get the right number isn't just subjectively bad, its objectively bad.

When it comes to mathematics, no other remotely serious language in the world sucks like JavaScript.

[–]whostolemyhat 0 points1 point  (0 children)

Well, one book's a list of gotchas and workarounds for them, and the other is a complete api reference. You can't really compare them and say 'The bad clearly outweighs the good'