4 ms·

It sounds like you read a lot of articles about why JS is bad, but don't have a lot of experience with it. * 10-day design? Nobody is using Javascript 1.0 anym

by efdee 8y ago

It sounds like you read a lot of articles about why JS is bad, but don't have a lot of experience with it. * 10-day design? Nobody is using Javascript 1.0 anymore. * Typing is available to various extents thanks to Flow and/or Typescript. * Slowness... I don't know what you're referring to. Javascript isn't slow. * null vs undefined. What about them? They are two different things with different meanings. * Dependency hell. I assume you refer to the many small modules on NPM with dependencies on other modules. Not sure what the problem here is per se. Avoid them if you don't like dependencies. * NPM insecurity - what? I like JS on the backend because it's a nice, flexible language to work with, with a healthy and cheap (cost-wise) ecosystem. I get a lot of stuff done very quickly, and I can run my stuff pretty much everywhere.

whatshisface 8y ago
>NPM insecurity NPM packages can contain malicious code. There's no NPM review process, and you can't point to specific versions to lock in your own reviews (package administrators can change whatever files they'd like). There's no such thing as a verified-safe dependencies list because the file you reviewed last month might not be downloaded today.
- s_y_n_t_a_x 8y ago
  >and you can't point to specific versions Yes you can. >no such thing as a verified-safe dependencies list There are audits.
- efdee 8y ago
  You definitely can point to specific versions. That being said, most package managers can contain malicious code and very few of them actually review their packages. Besides, any company using NPM seriously probably has their own proxy in front of it, so there's no case of "the file might not be downloadable anymore" if that was already a problem with NPM itself.
mises 8y ago
NPM insecurity: lots of malicious packages discovered. Also, left-pad. Slowness: Yes, it is. Look at all the benchmarks comparing it to, say, go.

by efdee 8y ago

whatshisface 8y ago

>NPM insecurity NPM packages can contain malicious code. There's no NPM review process, and you can't point to specific versions to lock in your own reviews (package administrators can change whatever files they'd like). There's no such thing as a verified-safe dependencies list because the file you reviewed last month might not be downloaded today.

s_y_n_t_a_x 8y ago
>and you can't point to specific versions Yes you can. >no such thing as a verified-safe dependencies list There are audits.
efdee 8y ago
You definitely can point to specific versions. That being said, most package managers can contain malicious code and very few of them actually review their packages. Besides, any company using NPM seriously probably has their own proxy in front of it, so there's no case of "the file might not be downloadable anymore" if that was already a problem with NPM itself.

mises 8y ago

NPM insecurity: lots of malicious packages discovered. Also, left-pad. Slowness: Yes, it is. Look at all the benchmarks comparing it to, say, go.