3 ms·

JavaScript is a messy language, but ignoring that, the module ecosystem is a mess. There are many duplicated modules, many of them done in a half-assed manner b

JavaScript is a messy language, but ignoring that, the module ecosystem is a mess. There are many duplicated modules, many of them done in a half-assed manner by inexperienced developers and rarely updated. For example, the Node community absolutely loves MongoDB for inexplicable reasons, and support for other datastores is terrible. Despite Postgres supporting hstore for years and Node being popular for years, the two hstore modules are "node-postgres-hstore" (7 stars on github) which hasn't been updated in 1 year and "node-hstore" (17 stars on github) that hasn't been updated in 2 years. Everything I've seen indicates that this is typical for modules in Node. Meanwhile, Ruby and Rails support Postgres extremely well at this point. Similarly, node has several migration libraries, all of which are pretty limited. One of the popular ones, "node-migrate" by one of the most prolific node module developers, still has an open issue from 2 years ago about using timestamped migrations, with the developer commenting as if the concept is news to him (https://github.com/visionmedia/node-migrate/issues/2 https://github.com/visionmedia/node-migrate/issues/2)

clavalle 13y ago
>There are many duplicated modules, many of them done in a half-assed manner by inexperienced developers and rarely updated. This statement accurately describes the world of Ruby gems.
- integraton 13y ago
  That might be fun to claim, but the reality is that it's 2013, not 2007. The Ruby ecosystem is much more robust at this point.
  - dragonwriter 13y ago
    The greater robustness means that: 1. There are more high quality modules, so if you look hard enough, you are likely to find one for your tasks, 2. There is an even greater number of duplicative, half-assed, and poorly maintained modules than there were in 2007 (some of which existed but weren't half-assed or poorly maintained in 2007), and those are still quite often the first ones you'll run into when looking for something that does what you want.
julianlam 13y ago
> For example, the Node community absolutely loves MongoDB for inexplicable reasons, and support for other datastores is terrible Right, because everybody uses Postgres, right? All of the major database vendors are supported quite well, and just because hash storage in Postgres (which is already a stretch) is not as well maintained doesn't mean "support for other datastores is terrible).

clavalle 13y ago

>There are many duplicated modules, many of them done in a half-assed manner by inexperienced developers and rarely updated. This statement accurately describes the world of Ruby gems.

integraton 13y ago
That might be fun to claim, but the reality is that it's 2013, not 2007. The Ruby ecosystem is much more robust at this point.
- dragonwriter 13y ago
  The greater robustness means that: 1. There are more high quality modules, so if you look hard enough, you are likely to find one for your tasks, 2. There is an even greater number of duplicative, half-assed, and poorly maintained modules than there were in 2007 (some of which existed but weren't half-assed or poorly maintained in 2007), and those are still quite often the first ones you'll run into when looking for something that does what you want.

julianlam 13y ago

> For example, the Node community absolutely loves MongoDB for inexplicable reasons, and support for other datastores is terrible Right, because everybody uses Postgres, right? All of the major database vendors are supported quite well, and just because hash storage in Postgres (which is already a stretch) is not as well maintained doesn't mean "support for other datastores is terrible).