Quote:
Originally Posted by Neko
Just to clarify (and I'm not trolling, I just can't tell); is your position that there is never a real world use case for a CMS?
No. You need to read a few posts up to get the context. My position is I have never found a reason to use one.
Quote:
how are you arguing that rolling your own is better for "fast application development" than using a CMS
It's dead simple. You're allowed to re-use the code you write.
If I wrote an image gallery once, why wouldn't I be able to use it again in a different project? I would just copy it over and modify the bits and pieces that need to be modified.
If I were using a CMS the same thing would need to be done except the functionality of the image gallery is limited to whatever image gallery module I decided to pick. To change it would involve digging pretty deep in code written by 1 or more people.
As soon as it really needs custom functionality (something a bit more basic than let's say adding a new field to be output), then I have to deal with learning the entire image gallery code base, and I have to be very comfortable hacking away at the CMS itself in case I need something it doesn't offer.
What happens when the site you've been asked to make is using 8 different modules and 6 of them need to be heavily modified? That seems like an awful position to be in and I would hate life if I had to deal with that on a regular basis.