3 ms·

>Can you provide any examples where Node does not provide a good ecosystem for backend programming? A decent URL parsing/matching lib not tied to a full web fr

>Can you provide any examples where Node does not provide a good ecosystem for backend programming? A decent URL parsing/matching lib not tied to a full web framework ? Disclosure - haven't done serious node work in a while but ~2 years ago when I was building something in with it all the published libs for this were complete garbage - looking at the code for the packages made me realize what sort of crap gets published to NPM and then actually used/referenced by community. I think it's better than PHP (took on a PHP integration job to help out a friend in trouble recently - that was going back to the dark ages with package management and module system). But it's the same tier in my eyes - filled with clueless newbies trying to lead other newbies - a community of blind leading the blind. In my eyes a sane/mature language like Python beats Node any day of the week quality/productivity wise and so does stuff built on top of JVM/CLR. As much as C#/Java devs like to obfuscate code with useless patterns I'd take a random C#/Java package over a random Node package any time - at least the developer managed to convince the type system to compile his code - wouldn't say that the authors could do the same for some of the NPM packages I saw.

jeffschofield 7y ago
FYI a URL parser was actually added around 2 years ago in v8.0.0. It's based on the WHATWG standard and matches the implementation in modern browsers. https://nodejs.org/api/url.html#url_url_parse_urlstring_parsequerystring_slashesdenotehost https://nodejs.org/api/url.html#url_url_parse_urlstring_pars...
- rubber_duck 7y ago
  Good to know. Maybe if I got back to it the core is more functional now. My impression is that it's soo easy to publish to NPM and the ecosystem is newbie friendly - this is good but it also creates a lot of noise and popularity/usage is not a valid indicator of reliability/quality (compared to other platforms). And because the core was so barebones you need to use third party solutions a lot more often so it compounds the issues.
toastal 7y ago
Any type system that allows null or any shouldn't be trusted any more than a dynamic language
- rubber_duck 7y ago
  It's not so much that I trust in the type system to prove correctness it's more that the type system and build system setup is a barrier to entry that puts a threshold on newbies publishing packages. Personally I've only seen such low quality code published and used in Node and PHP communities - because of the missing standard library and newbies creating noise with creating low quality libs or not knowing how to select/filter those and increasing their popularity. For example I recently had to deal with a grunt build system (could not chose a different task runner) and the quality of those plugins ...

jeffschofield 7y ago

FYI a URL parser was actually added around 2 years ago in v8.0.0. It's based on the WHATWG standard and matches the implementation in modern browsers. https://nodejs.org/api/url.html#url_url_parse_urlstring_parsequerystring_slashesdenotehost https://nodejs.org/api/url.html#url_url_parse_urlstring_pars...

rubber_duck 7y ago
Good to know. Maybe if I got back to it the core is more functional now. My impression is that it's soo easy to publish to NPM and the ecosystem is newbie friendly - this is good but it also creates a lot of noise and popularity/usage is not a valid indicator of reliability/quality (compared to other platforms). And because the core was so barebones you need to use third party solutions a lot more often so it compounds the issues.

toastal 7y ago

Any type system that allows null or any shouldn't be trusted any more than a dynamic language

rubber_duck 7y ago
It's not so much that I trust in the type system to prove correctness it's more that the type system and build system setup is a barrier to entry that puts a threshold on newbies publishing packages. Personally I've only seen such low quality code published and used in Node and PHP communities - because of the missing standard library and newbies creating noise with creating low quality libs or not knowing how to select/filter those and increasing their popularity. For example I recently had to deal with a grunt build system (could not chose a different task runner) and the quality of those plugins ...