3 ms·
Am I the only one who thinks they are propping up their successor? If you're going to learn Coffeescript, why bother with Rails at all? Just write cs both ser
by MatthewPhillips 16y ago
Am I the only one who thinks they are propping up their successor? If you're going to learn Coffeescript, why bother with Rails at all? Just write cs both server and client side. When some one builds a mature node.js MVC framework, Rails is going to be in trouble.
- ascendant 16y agoExpress is on the right path. I picked it up for the first time last weekend and liked it.
- MatthewPhillips 16y agoIt's not MVC though, right? I prefer something more lightweight like Express/Sinatra, but a lot of people are in love with MVC.
- JonnieCache 16y agoIt's pretty damn MVC. Just because it doesn't make you define classes with 'Controller' in the name doesn't mean it isn't MVC.
- MatthewPhillips 16y agoI'm with you now. The example on the homepage isn't MVC, but I see from the further documentation that you can incorporate views. Nice.
- ascendant 16y agoYeah, and the default template language (Jade) is a lot like HAML. In fact, I think there's HAML/SASS plugins, but I'm pretty new at Express so don't take that as gospel.
- deleted 16y ago[deleted]
- moxiemk1 16y agoIf your motivations are to make the most useful (to yourself) framework, then there is no problem in propping up your successor. Making the transition smooth is indeed the "Right Thing"