News for hackers. Stuff that matters.
Re:Too Many Tools and Frameworks (2015) by dom0 on Tuesday October 04, 2016 @05:49AM (#12634360)
> I suspect the best/healthiest ecosystem is probably somewhere in between that of Ruby and JavaScript. Rails may have ultimately hurt Ruby by its dominance, just as the current volatility in JavaScript tools seems to drive some people away (or at least add frustration).

I think this description matches the Python web ecosystem quite well. Historically there were the Z(ope)-ish projects, which still exist and are being used (and they work quite nice); Django obviously dominated for a long time, but in more recent years some healthy competition ensued (Flask and it's highly modular approach for example, but also Pyramid), which resulted in a lot of reworking and improvement for all frameworks. Django now vs. Django 2010 is a vast difference in developer and user friendliness. Some specialized frameworks popped up (Tornado comes to mind), but overall there isn't a heavy fragmentation of the ecosystem (bad) but no one dominator either (bad).

Re:Too Many Tools and Frameworks (2015) by oblio on Tuesday October 04, 2016 @07:30AM (#12634751)
The Java ecosystem is another good example IMO.

Web frameworks: Spring, Java EE, a lot of solid smaller ones.

Build tools: Ant (mostly legacy), Maven or Gradle.

Then for almost any niche there's usually 2-3 clear contenders, production-grade stuff.

For such a huge ecosystem Java is remarkably not-fragmented.

Re:Too Many Tools and Frameworks (2015) by collyw on Tuesday October 04, 2016 @05:50AM (#12634366)
Its nice that there is one (fairly) obvious choice to go for unless you have specific needs.