I’m familiar with the early history, I’ve dabbled in it in modern times, and of course I’ve seen all the ways it’s bad memed about ad-infinitum (and have to agree).
I didn’t really think I had to be able to write a book on it to say it doesn’t deserve the use it gets, and I don’t think it’s outrageous to imagine that there’s a connection with the hasty genesis. So, I mentioned that off-hand. If it’s actually unconnected my bad.
The memes are annoying because most of the complaints are superficial.
“Look, "b" + "a" + +"a" + "a" outputs "baNaNa"! JavaScript bad!” Yeah, that’s what happens. Just don’t do that thing that obviously doesn’t look right. Don’t use var, just like every modern JavaScript learning resource will tell you. Don’t use == if you don’t intend for type coercing to happen.
If you don’t write bad code on purpose, JavaScript is fine.
I’m familiar with the early history, I’ve dabbled in it in modern times, and of course I’ve seen all the ways it’s bad memed about ad-infinitum (and have to agree).
I didn’t really think I had to be able to write a book on it to say it doesn’t deserve the use it gets, and I don’t think it’s outrageous to imagine that there’s a connection with the hasty genesis. So, I mentioned that off-hand. If it’s actually unconnected my bad.
The memes are annoying because most of the complaints are superficial.
“Look,
"b" + "a" + +"a" + "a"outputs"baNaNa"! JavaScript bad!” Yeah, that’s what happens. Just don’t do that thing that obviously doesn’t look right. Don’t usevar, just like every modern JavaScript learning resource will tell you. Don’t use==if you don’t intend for type coercing to happen.If you don’t write bad code on purpose, JavaScript is fine.
If coding teaches you anything well, there’s no bound to the different ways you can screw up. Don’t use bad languages on purpose.