4 ms·
RailwayJS is cool, I used it for a long time, though I now use Locomotive as the latest git version is very good. It doesn't offer as many features but is clean
by jameswyse 14y ago
RailwayJS is cool, I used it for a long time, though I now use Locomotive as the latest git version is very good. It doesn't offer as many features but is clean and gets out your way.
- johnx123-up 14y agoPlease give little more information why http://locomotivejs.org/ http://locomotivejs.org/ is better than RailwayJS. Very much interested to know the reasons.
- jameswyse 14y agoI like locomotive because it stays out my way and allows me to work the way I want to. It's basically just Express 3 with an MVC layout, nicer routing, some nice helpers and a very clean and logical directory layout. It's how I would organise a new Express application if I was coding it from scratch! I really like the idea of locomotive's 'initializers' directory - Any files you put in here are loaded at boot, in order. I use files in here to set up things like configuration, databases, logging, etc. With railwayjs these all ended up in the environment files which was hard to maintain. The one thing I really didn't like in RailwayJS was the convention of putting all your database models inside one file (schema.js), I had to over-ride the built in ORM (JugglingDB) at the time because it was lacking features and define a customSchema() function to use mongoose, and this file ended up being really large and a bit of a mess. I tried separating things in to individual model files but I couldn't get it working without messing with RailwayJS code. Probably a lot of the problems I had are now resolved as this was a few months ago, but I'm sticking with Locomotive from now on :)