> somehow JS devs have decided switch statements are bad
Nonsense. Though sometimes using an object can look cleaner depending on your use case.
> indenting with 2 spaces is the only way to go
I love 4 spaces and I use 4 in my JavaScript projects. Just because you've seen some subset of people use 2 doesn't mean it's the majority, what you have to use, etc.
> semi-colons should be banished
Absolutely, positively NO. Semi-colons are a requirement of the language. Some people elide them, incorrectly, because the JavaScript engines are good enough to still handle it. In my experience being playing a limited part in open source JavaScript eliding the semi colon seems to be a rarely done practice.
Regardless it's incorrect no matter how you slice it.
> "boilerplate" code should be hidden in libraries the magically wipe it away so your code looks "clean,"
This sounds more like a rails-ism than a JavaScript-ism. Though you'd be hard pressed to find libraries without implicit behaviors in every language. Some people take DRY way too far.
This point just seems more anecdotal than anything else.
> a make file. Who has time to wade through umpteen million build systems?
A lot of JavaScript devs use make. Nothing wrong with that.
I think the semicolon requirement is more for broken minifiers than actually making the unpacked code clear/correct. But that's just me, I guess, as I have worked with many line oriented languages, and have no reverence for C syntax.
Nonsense. Though sometimes using an object can look cleaner depending on your use case.
> indenting with 2 spaces is the only way to go
I love 4 spaces and I use 4 in my JavaScript projects. Just because you've seen some subset of people use 2 doesn't mean it's the majority, what you have to use, etc.
> semi-colons should be banished
Absolutely, positively NO. Semi-colons are a requirement of the language. Some people elide them, incorrectly, because the JavaScript engines are good enough to still handle it. In my experience being playing a limited part in open source JavaScript eliding the semi colon seems to be a rarely done practice.
Regardless it's incorrect no matter how you slice it.
> "boilerplate" code should be hidden in libraries the magically wipe it away so your code looks "clean,"
This sounds more like a rails-ism than a JavaScript-ism. Though you'd be hard pressed to find libraries without implicit behaviors in every language. Some people take DRY way too far.
This point just seems more anecdotal than anything else.
> a make file. Who has time to wade through umpteen million build systems?
A lot of JavaScript devs use make. Nothing wrong with that.