The trouble with opensource is that the answer to “Does this software do X?” is invariably the same:
“Yes, you just have to download the 5 GB SDK, open the /…longestpathever…/conf.java, add this custom code {…} and redeploy.
(I’m currently trying to stay away from any kind of microblogging platform as an experiment. After a week, where I resisted the urge to tweet anything that happened to me, I HAD to let this blog post slip)
What’s the answer with closed source, instead?
Do you think it’s a better developing philosophy?
Sure, I’m not saying it’s a bad thing.
More of an inconvenience. Sometimes you look for something cooked and they keep throwing ingredients at you! :D
Of course “sure” wasn’t implying that I think closed source is better. It was more like “Sure, I see your point”
Dear Mike, I do really think that your statement about open source is at best incorrect. I mean, there are tons of open source software out there and some, on some platform, behave like you say and some other behave just out of the box. Moreover the same can be stated for proprietary software and even in case of some OS.
Cheers