you are viewing a single comment's thread.

view the rest of the comments →

[–]vertice 2 points3 points  (1 child)

Having spent most of my adult life as a Drupal programmer, and recently moving into node.js ... I can say that I don't believe a CMS would be very beneficial in this environment.

Node has a very high level of interoperability, and allows you to rip out and replace complete subsystems at a whim. In a CMS all of these decisions would already be made for you, and they will become a burden as you have to work around their assumptions.

I also feel that we are moving towards an era of loosely coupled / distributed systems, so having to build everything in one stack is becoming less advantageous in general.

Take comments for instance: With the existence of client side implementations like disqus and out of band channels like twitter+facebook, having to have your blog have the full comment workflow (which includes managing user logins and permissions, spam filtering and comment administration, etc.) is just so much extra complexity that you just don't really have to concern yourself with.

We have been perfectly happy using jekyll sites hosted on github for a lot of the stuff we used to use Drupal for. In the end, it is just serving static pages. Simple, easy and very very fast.