Is it not true to say that almost every website requires something that any given CMS won't cater for?
On Fri, Oct 1, 2010 at 5:13 AM, Ruben Reusser <[email protected]> wrote: > I saw this post the other day and was wondering what you all think about the > approach - and if you have any experience with this approach it would be > nice to hear what problems you ran into. There are some great Java CMS's out > there one can build on top of too > > http://www.metaltoad.com/blog/framework-dead-long-live-cms > > If you don't know already, the framework is dead. That is to say, unless you > have money to burn, frameworks like Zend, CakePHP, Django, Struts, .NET, and > even Rails should not be considered as a foundation for building anything > but the most unique and game changing websites*. The age of the framework > for building websites is gone and it has been replaced by the open-source > CMS or Content Management System. > > In this declaration I am not promoting any particular CMS (although I'm > partial to Drupal myself), simply letting anybody who hasn't heard the news > that just about every website needs more than CRUD (Create Read Update > Delete), a shared database connection and other simple tools frameworks > provide. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
