The trouble with Blogs, Wikis, and Forums

There are a lot of great tools out there for blogging, wikis, and forums. Some of them even look nice and are (somewhat) friendly to use. I like wordpress, I like blogger, I like phpBB (except for the appearance), punBB, and others forum tools. I like wikis quite a lot. I've tried a lot of … Continue reading The trouble with Blogs, Wikis, and Forums

Advertisement

The trouble with CMS frameworks

My last post was about the trouble with MVC frameworks, in my view, which briefly is: Multiple action handling Component/Template processing (related to the above) Front controller/Back controller, helpers and the associated bloat or complexity and code duplication. I noted that CMS frameworks attempt to handle some of this, most especially the component/template paradigm -- … Continue reading The trouble with CMS frameworks

The trouble with MVC frameworks

Here's the problem I have with so-called Model-View-Controller frameworks like Rails. They seem geared towards a single application per implementation. What do you do with a request that wants to work with multiple components? Or perform multiple actions. Then a REST-style request such as http://my-site/component/actionX?params=123 falls flat on it's face, because you've either got a … Continue reading The trouble with MVC frameworks

Leveraging existing knowledge and techniques — ideal framework requirement #3

Too many framework developers decide they're going to be too clever by half. As a result, writing plugins, extensions, modules, templates, models, views, controllers, classes, procedures, whatever you call them is always a unique experience. My rant about ORM (and templating) tools was one part of this. Writing records to a database is not rocket … Continue reading Leveraging existing knowledge and techniques — ideal framework requirement #3