Mercurial loses a developer
Posted Oct 1, 2005 4:23 UTC (Sat) by drag
In reply to: Mercurial loses a developer
Parent article: Mercurial loses a developer
It's the classic developement in-house vs get a off-the-shelf product. Been going on for years. People get tired of supporting their own buggy creations made by overworked staff, then it becomes fasion to buy big projects, then the cost overruns, overhype, and empty promises drive them back to in-house solutions. rinse, repeat.. All very expensive, all a pain in the ass.
Maybe that's the partially why open source development model is such a success. You get a product that is probably still fairly small, or hopefully modular, that you can modify to fit your needs easily and quickly. In addition it's backed up by the distinct likelyhood that you'd be able to hire outside developers or, god forbid, consultants that are familar with it if need be.
So it's maybe the best of both worlds and avoids most of the pitfalls of either.
to post comments)