3 ms·
I've known rails for years but haven't yet used it seriously. I felt it's good because setting up is easy and the velocity is high. Until now I use it every da
by namelosw 8y ago
I've known rails for years but haven't yet used it seriously. I felt it's good because setting up is easy and the velocity is high.
Until now I use it every day and I found it's really great and better than my previous impression:
1. Compared to JS there's always a specific way of doing things - how to validate, how to dispatch async Job, how to send emails and real-time notification etc.
2. Compared to Spring there's only a recommended default way you can easily start with. You don't struggle with SpringWeb vs WebFlux, different JMS implementations, Hibernate or query builders, etc.
- baroffoos 8y ago>1. Compared to JS there's always a specific way of doing things - how to validate, how to dispatch async Job, how to send emails and real-time notification etc. This is so important. When doing something on rails you always get instructions on the exact things you have to do where as JS always seems to either give you 500 different versions of the instructions or just expects you to work out how to set it up based on everything else in your project.
- mikewhy 8y agoI mean, we're comparing languages to frameworks here. Of course there's going to be multiple different solutions for a language while a framework will have fewer.