| Rails has always given me conventions to follow when creating/writing apps - except for javascript. Rails never really had any conventions for writing javascript. Hopefully, you and your coworkers had good habits when writing/organizing your js, but rails never really gave you any guidance except to throw it in your apps/assets/js folder. > There is ES6/Typescript- that is the future. According to the sprockets-es6 github page, its goal is to have es6 functionality in sprockets 4 by default. > Node is still not ready. I'm not quite sure what you mean by this statement. It's very ambiguous. Anyways, you might want to look at MeteorJS. It's a rails-like framework in javascript. It's not ready yet if you want to use a database other than mongo. > I just feel let down. I want to get excited about Rails again, but give me a path. One of the lessons that I've learned working with OSS is that we as individuals & developers are responsible to create these paths. The people who develop Rails & other awesome oss are just regular janes/joes like you and me. > I don't really like Ember a whole lot, because the community is just not where it is with Angular and React The ember community is not as big as Angular's or React, but it definitely does exist & is very friendly helpful. IMO, Ember (along with Ember-Data & Ember-CLI) is the Rails of the js frameworks, it follows strong conventions and comes with a lot of magic right out of the box. You should check out their guide - perhaps they could have an overview that actually states the features that come out of the box. |