As a disclaimer, I'd like to say that CMSMatrix is completely ignorant of many features of my favorite CMS, and fails to highlight its' major advantages. I suspect this is true of many of the packages I am not familiar with as well, as many developers would say that Feature X is not needed because Feature Y is flexible enough to cover all of its' use cases.
That said, I couldn't agree more with your point, and I think this has a lot to do with the relationship between established and emerging Free Software developers. A lot of CMS start specifically to host a blog or handle discussions for some school club or side-project at work. Some of the more advanced systems have a barrier to entry or an established way of doing things which new users are put off by.
I think Plone is a great example of this. Part of me decided a few years ago when I ended up at the first international plone conference that I would buy into the promises of the Zope3 component model's elegant MVC implementation, and how Plone and Archetypes could help me to live in a similar world to that which would exist with pure z3 in the meantime.
It's been a long and bumpy ride, and I haven't made a lot of money, but I have seen that I was right. When I was a member of a 12-man development team, our resources could easily have produced some very nice results with Plone and Archetypes. Unfortunately, the group went for some M-V-C php framework which wasn't even using PHP for templating, simply because more people apparently know the php language itself.
I wish I wasn't so broke, but I'm glad that I am not feeding myself by working on that system and continuing in that corporate culture. I only wish I'd been smart enough to come up with a prototype product management system when I had the chance.
Slashdot Mirror
As a disclaimer, I'd like to say that CMSMatrix is completely ignorant of many features of my favorite CMS, and fails to highlight its' major advantages. I suspect this is true of many of the packages I am not familiar with as well, as many developers would say that Feature X is not needed because Feature Y is flexible enough to cover all of its' use cases. That said, I couldn't agree more with your point, and I think this has a lot to do with the relationship between established and emerging Free Software developers. A lot of CMS start specifically to host a blog or handle discussions for some school club or side-project at work. Some of the more advanced systems have a barrier to entry or an established way of doing things which new users are put off by. I think Plone is a great example of this. Part of me decided a few years ago when I ended up at the first international plone conference that I would buy into the promises of the Zope3 component model's elegant MVC implementation, and how Plone and Archetypes could help me to live in a similar world to that which would exist with pure z3 in the meantime. It's been a long and bumpy ride, and I haven't made a lot of money, but I have seen that I was right. When I was a member of a 12-man development team, our resources could easily have produced some very nice results with Plone and Archetypes. Unfortunately, the group went for some M-V-C php framework which wasn't even using PHP for templating, simply because more people apparently know the php language itself. I wish I wasn't so broke, but I'm glad that I am not feeding myself by working on that system and continuing in that corporate culture. I only wish I'd been smart enough to come up with a prototype product management system when I had the chance.
You never enjoyed playing robber and shooting up the cops?