> you should consider that there is nothing wrong with having two subtly different, yet very good tools.
It's amusing that this needs to be said when writing for a particular audience.
It's amusing that this needs to be said when writing for a particular audience.
I don't think anyone would agree that having 110V, 220V, 50Hz and 60Hz is good. Or subtly different railway gauges. Or Windows and Unix style line endings.
There are a couple of upsides too - increased competition, backup in case one project goes in a crazy direction, etc.
But it's silly to pretend there's nothing bad about it.
Though anyway in this case I think "a marvel ahead of its time" is not a "subtle difference".
rails was first released in 2004. django in 2005, laravel in 2011. i used roxen (and it's predecessor spinner) in 1994!! that's literally a decade earlier. i think the only possibly competing tool available at the time was cl-http in lisp[0]. (AIDA/Web for smalltalk was created in 1996, as was WebObjects, Java EE came in 1999. that's all i could find so far)
[0]: at the time i was looking for a better alternative to the available ncsa and cern webservers. i remember ordering a student version or something like that of franz lisp so i could try it. and i was put off by having to write lisp code just to serve static files. that was what made me keep looking until i found spinner.
Yeah that's what I suspected (read to the end of my comment).
the ability to try different approaches to solve the same problem
avoiding lengthy arguments over how to implement a feature
the ability to take risks in the development
...
imagine we'd all be stuck with sendmail or perl.
of course when you get to the 10th video editor it starts getting ridiculous. there certainly are some areas where i wish some projects could join forces to create better results.
Checking more recent comments, it looks like a Holy War has broken out over whether there should be Holy Wars. Priceless!