Use Rails
jmduke.com
Use Rails
1–10 of 88 posts
Re: Use Rails
#2This goes hand-in-hand with the idea of using "boring" technology. If it's mission critical, I'd rather be using something battle-tested than the brand-new hot tech. There's re tooling, more documentation and likely more search-able solutions to whatever problems you may run into.
Re: Use Rails
#3I strongly agree with the article's points. While I haven't used Rails, I'm a Django developer and have never built something with Rails; I like the benefits of sticking with full-stack frameworks. Rails is a solid choice, but Django, especially when combined with htmx, also enables quick and robust application development.
It's refreshing to read about someone who prefers a straightforward approach (using boring technology) rather than dividing work across multiple teams and technologies. Using a single, full-stack framework not only simplifies the development process but also enhances the overall enjoyment when working :)
Re: Use Rails
#4For most web applications rails is fair enough, a boring technology (as well other boring stacks).
Although it got my attention that rails could work really well on production with SQLite (even more boring technology), for small sites.
Re: Use Rails
#5Most of my fortune is because of Rails.
Re: Use Rails
#6One strong point for productivity/getting stuff done fast in real world: good REPL. It's not just Rails of course, but worth noting when comparing interpreted languages to compiled ones. Rails console is not only a great development tool, it's also an invaluable way to tackle customer support problems quickly.
Re: Use Rails
#7These days I prefer using a NodeJS framework like AdonisJS over Ruby on Rails, but Rails had an important role in getting us here.
Re: Use Rails
#8Rails is great, as great as it ever was... I work with it on a daily basis, the only issue right now is the job market... And the fact that if you don't pair it with a shiny frontend framework like React, you'll have a tough time getting employment, this is more so for newcomers to the stack, in lieu of the radical experience requirements for jobs in the sector these days.
Re: Use Rails
#9One strong point for productivity/getting stuff done fast in real world: good REPL. It's not just Rails of course, but worth noting when comparing interpreted languages to compiled ones. Rails console is not only a great development tool, it's also an invaluable way to tackle customer support problems quickly.
There are several reasons I've come to prefer phoenix over rails but a big one is definitely the experience of using livebook with it. The first time I saw someone use that to simultaneously diagnose and document an incident just blew my mind. Now a few years in it's one of the few things in programming that ever really lived up to my expectations lol.
Re: Use Rails
#10I strongly agree with the article's points. While I haven't used Rails, I'm a Django developer and have never built something with Rails; I like the benefits of sticking with full-stack frameworks. Rails is a solid choice, but Django, especially when combined with htmx, also enables quick and robust application development. It's refreshing to read about someone who prefers a straightforward approach (using boring tec…
I would totally expand "Rails" to "Django or Rails or Laravel or any other well-maintained mature full-stack web framework in the language you are the most comfortable with".
There's a lot of awesome options for boring technology! Even javascript has next.js which is pretty boring at this point, even if it is missing some things.