Comment by mrmondo | Hacker News Reader

Comment by mrmondo | Hacker News Reader

Parent Full thread

As someone who's hosted and fixed a lot of CMS in recent years I'll say this: choose a solution that's fit for the individual purpose.

All CMS' suck, a bit like all OS' suck. As soon as you do anything non-standard their inherit flexibility becomes a burden. If you have skills in rails and need an off the shelf CMS find a popular one and use it you like but if you need to create a web 'application' look at Sinatra, rails or whatever but don't use a CMS as the foundation for an application.

Most of all, if my team and I have one take away: Stay far away from Drupal and people that preach its relevance. It is a world of hurt with an 'expert beginner' community. That has cost so many organisations more time and money than they ever anticipated.

Treat ever 'off he shelf' product with a degree of disposability - don't get locked in and never get into the trap that you've chosen 'the best'.

It's CMSes and OSes. You're looking for the plurals, so you definitely don't need to use a possessive apostrophe there because there's no ownership in the sentence.

Also, because they're acronyms you pronounce by enunciating the words, my instinct would be to use OS's (as you would pronounce the 's, O-S-es). But that's up for debate.

For example:

The OS's kernel blew up (possessive apostrophe, the OS owns the kernel)

He had a wide range of OSes to choose from (pluralization, there are many OSes)

Thank you for clarifying / pointing that out to me. I've never spent time to understand that an apostrophe used in this way made it possessive. I've taken that on board and will (hopefully) not make this mistake again.

Since we're picking on people for their grammar mistakes, let me throw my hat in the ring:

I'm more in favor of this convention (OS') when it comes to possessive apostrophes for word that end in an "S" which is to omit the trailing "S" and leave to the reader or interlocutor to infer the meaning from the context.

I've worked with Drupal 6 years ago. I think it was awesome if all you need is a web site with custom workflows in the content creation. It made you suffer, however, if you started to turn the web site into an app for the public (anything more than custom filters for your lists and I think you are in this territory). The problem is a typical web site (even in those days) almost always turned into an app.

Reply on news.ycombinator.com