3 ms·

I know you're being downvoted but I 100% agree with you. I don't want 100,000 Hex packages. I want a few thousand packages that solve problems really well and p

I know you're being downvoted but I 100% agree with you. I don't want 100,000 Hex packages. I want a few thousand packages that solve problems really well and people rally around and collaborate on them. NPM and RubyGems are casualties of people seeking open source fame and I hope we can avoid that in Elixir.

angersock 11y ago
Eh, worst case, we can make another hex that enforces good test coverage and documentation. :)
MrBra 11y ago
This is totally nonsense. Any among those 100000 could become the most used library in their specific field at some point in time, and the fact that you can choose to contribute to whichever you like more, or create your own is the beauty of OSS. If you fear this will weaken devs ability to focus their strength on just one common solution, and be inefficient, then you really don't know how OSS works. What you want to impose, is something that already happens spontaneously in OSS (one gem taking over the other, unless they provide very different features or to do things in a drastically different manner).
- angersock 11y ago
  Counter-argument: the entire Javascript ecosystem.
danneu 11y ago
> NPM and RubyGems are casualties of people seeking > open source fame and I hope we can avoid that in Elixir. No, they're casualties of people actually using the platform, the platform's low publishing barrier, and the ecosystem's preference for focused libraries over monolithic bouncy castles. Rallying around one library sounds cool until you see that the top three competing solutions in another ecosystem each have more contributors and activity. Then you realize you're not in the elite ecosystem, just the smaller one that has one library like my tiny Texas hometown.
- rubiquity 11y ago
  Yeah because those 20+ half-baked MongoDB drivers on npm are totally better than emongo (Erlang) and mongo (Elixir).
  - danneu 11y ago
    I don't use Mongo, but I don't see any competitive alternatives to node-pg.

angersock 11y ago

Eh, worst case, we can make another hex that enforces good test coverage and documentation. :)

MrBra 11y ago

This is totally nonsense. Any among those 100000 could become the most used library in their specific field at some point in time, and the fact that you can choose to contribute to whichever you like more, or create your own is the beauty of OSS. If you fear this will weaken devs ability to focus their strength on just one common solution, and be inefficient, then you really don't know how OSS works. What you want to impose, is something that already happens spontaneously in OSS (one gem taking over the other, unless they provide very different features or to do things in a drastically different manner).

angersock 11y ago
Counter-argument: the entire Javascript ecosystem.

danneu 11y ago

> NPM and RubyGems are casualties of people seeking > open source fame and I hope we can avoid that in Elixir. No, they're casualties of people actually using the platform, the platform's low publishing barrier, and the ecosystem's preference for focused libraries over monolithic bouncy castles. Rallying around one library sounds cool until you see that the top three competing solutions in another ecosystem each have more contributors and activity. Then you realize you're not in the elite ecosystem, just the smaller one that has one library like my tiny Texas hometown.

rubiquity 11y ago
Yeah because those 20+ half-baked MongoDB drivers on npm are totally better than emongo (Erlang) and mongo (Elixir).
- danneu 11y ago
  I don't use Mongo, but I don't see any competitive alternatives to node-pg.