This is the beauty of open source. Apache 1.3 is still widely used, and many products are still based on it. If the Apache Foundation no longer wants to maintain it, others are free to pick it up and carry on. I wouldn't be surprised if this happened sooner rather than later.
So after a project dies it forks off into a slew a Legacy systems all needed independent modifications and changes. That is the Ugly side of Open Source to me. A more beauty side is if the tools that did need to work on 1.3 once apache stopped 1.3 support went and modified their apps to work on newer web browsers.
Forking code to keep your project going is not the way, it is just a bad idea.
If it forces people to upgrade to a better alternative, then maybe it is. Think IE6 - would it be better to maintain that ongoing (considering that many of the things the Slashdot groupthink wants to fix with IE6 are the explicit reasons why some companies are keeping it around) or kill it dead and have people upgrade?
"Laugh while you can, monkey-boy."
-- Dr. Emilio Lizardo
Open Source (Score:4, Interesting)
This is the beauty of open source. Apache 1.3 is still widely used, and many products are still based on it. If the Apache Foundation no longer wants to maintain it, others are free to pick it up and carry on. I wouldn't be surprised if this happened sooner rather than later.
Re: (Score:3, Interesting)
So after a project dies it forks off into a slew a Legacy systems all needed independent modifications and changes. That is the Ugly side of Open Source to me. A more beauty side is if the tools that did need to work on 1.3 once apache stopped 1.3 support went and modified their apps to work on newer web browsers.
Forking code to keep your project going is not the way, it is just a bad idea.
Re:Open Source (Score:3, Interesting)
Yeah, because a project dying and all the people that still use it being left out in the cold is really an attractive alternative.
Not.
Re: (Score:3, Insightful)