DEV Community 👩‍💻👨‍💻

Discussion on: Rails 5.2 Active Storage: Previews, Poppler, and Solving Licensing Pitfalls

citizen428 profile image
Michael Kohl • Edited on

I spent part of my recent talk at RubyConf Taiwan talking about this. Rails is still an excellent choice for a web framework for various reasons:

  1. Language: Ruby is a ton of fun to code in. I started in 2003/04 and still enjoy it tremendously. Yes, it's not the fastest, we all know that. But I always felt like too many people complain about this, without considering that pure request times are only part of a web app. What about optimizing and minimizing markup and CSS? Optimizing images? Using a proper CDN and caching aggressively? HTTP/2? rel="preload" and the loadCSS polyfill? You guys are doing an awesome job here on this site, and a lot of that doesn't come from any framework, but from caring <3
  2. Framework: Rails can't be all bad, otherwise there wouldn't be a Rails inspired framework for almost every language. Plus it's still evolving. Do I agree with every design decision they make? No, of course not. But Rails doesn't get much in your way trying to implement your own architecture on top of it, especially if you include certain modules/follow certain interfaces (i.e. what Ryan Bigg is doing with the rom-rb based ApplicationModel in his "Exploding Rails" book.
  3. Community: The Ruby/Rails communities are pretty great IMHO. They care about things like testing and software architecture, which is why we have so many talks on how to write maintainable Rails apps, or alternative architectures like Trailblazer. And let's not forget the new kids on the block, Roda, Hanami, the dry-rb stack, Hyperloop etc. If there ever was a great time to be a Ruby web developer it's now, on or off the Rails :)

Oops, this got a bit long and I'd still have quite a bit to say, maybe I should turn this comment into a post at one point...