5 ms·

Agreed. Rails API and whatever Javascript front-end you want is the best possible option out there. It's fast to develop, it's well documented since Rails has b

Agreed. Rails API and whatever Javascript front-end you want is the best possible option out there. It's fast to develop, it's well documented since Rails has been around forever, Ruby on the backend is sooo much nicer than Javascript, and you still get access to the front end trickery you need from modern Javascript. I have three languages I use. My web sites are done in Rails because it's fast and logical. One site has a Vue front end, only on a couple of pages where I need the JS fancy stuff. Most of my pure APIs are done in Flask because it's lighter weight. I use React Native for my native apps. I tried using Express.js for the APIs backing these apps but I could never get it all working right. I ended up rewriting it in Rails and now it's rock solid and fast as hell. I'd also like to mention most web development out there is still right in line with even old school PHP and does not need React or Angular or anything fancier than Rails. YAGNI.

h1d 8y ago
While I like ruby, your post is completely based on your experience. I have a Koa (express.js successor) with TypeScript and it's rock solid and since I don't like rails that much, I feel pretty loose there.
- spricket 8y ago
  Agree 100% Koa from the original devs of Express is amazing. Rails is worthless for modern webapps, there's just much better options
- mromnia 8y ago
  Isn't this comparing apples to oranges? I haven't used koa, but it seems to be same level of abstraction as express - basically a thin layer over HTTP with routing. Rails or Django are several levels higher - they include auth, database interaction, CRUD etc. I'm not saying that either approach is better, just that the comparison seems strange.
  - h1d 8y ago
    I'm only saying what the OP and I'm stating is worthless because they're based on experience.
  - benbristow 8y ago
    Rails doesn't include Auth. Devise does a great job of it though - https://github.com/plataformatec/devise https://github.com/plataformatec/devise
    - e12e 8y ago
      It does include "has_secure_password" and its friends (password/password_confirmation) though, which goes a ways towards including auth/authz even if one doesn't use devise, when coupled with before_action-s. It certainly comes with some facilities for getting off the ground: https://api.rubyonrails.org/classes/ActiveModel/SecurePassword/ClassMethods.html https://api.rubyonrails.org/classes/ActiveModel/SecurePasswo...

h1d 8y ago

While I like ruby, your post is completely based on your experience. I have a Koa (express.js successor) with TypeScript and it's rock solid and since I don't like rails that much, I feel pretty loose there.

spricket 8y ago
Agree 100% Koa from the original devs of Express is amazing. Rails is worthless for modern webapps, there's just much better options
mromnia 8y ago
Isn't this comparing apples to oranges? I haven't used koa, but it seems to be same level of abstraction as express - basically a thin layer over HTTP with routing. Rails or Django are several levels higher - they include auth, database interaction, CRUD etc. I'm not saying that either approach is better, just that the comparison seems strange.
- h1d 8y ago
  I'm only saying what the OP and I'm stating is worthless because they're based on experience.
- benbristow 8y ago
  Rails doesn't include Auth. Devise does a great job of it though - https://github.com/plataformatec/devise https://github.com/plataformatec/devise
  - e12e 8y ago
    It does include "has_secure_password" and its friends (password/password_confirmation) though, which goes a ways towards including auth/authz even if one doesn't use devise, when coupled with before_action-s. It certainly comes with some facilities for getting off the ground: https://api.rubyonrails.org/classes/ActiveModel/SecurePassword/ClassMethods.html https://api.rubyonrails.org/classes/ActiveModel/SecurePasswo...