Hacker News Reader

Just an opinion - none of us will be able to push Locomotive in an enterprise setting (which is precisely where CMS makes a lot of sense) without it supporting a relational DB.

Dont get me wrong - I get the value proposition of mongo - but in this case, it is taking away a lot and not giving me anything in return.

View on HN

We chose the tools that worked best for us and for our clients. LocomotiveCMS is already used by startups, web agencies, and big companies to design, deploy, and update sites every day. If Mongodb becomes a limiting factor, or if someone provides an equally elegant implementation on top of a RDMS, we'll happily switch. Until then, we'll focus on building our vision of the most elegant and friendly CMS possible.

could you elaborate on "equally elegant implementation on top of a RDMS" ? Genuinely want to know what advantage did mongo give you in a CMS setting.

Were you able to design a better architecture because of Mongo/nosql or was it developer productivity ?

Reply on news.ycombinator.com