News for hackers. Stuff that matters.
Re:Why Ruby on Rails still matters by jes5199 on Friday February 21, 2025 @11:42PM (#43136180)
it’s been quite a few years since I’ve worked in Rails, but I miss it sometimes. None of the other platforms ever completely replicated the functionality of a standard Rails environment circa 2009, so we reinvent the wheel every time. Basic stuff, too: ORM hooks, validations. It’s always a relief when I get to work with someone who has also worked on Rails before, because it means we have a shared vocabulary - there’s no equivalent thing among Python programmers, or JVM programmers, or anywhere else that I’m aware of
Re:Why Ruby on Rails still matters by ehnto on Friday February 21, 2025 @11:51PM (#43136223)
Laravel for PHP has a similar scope, community and exposure I would say.

Having mostly done agency work my whole life I have seen a lot of frameworks, in a lot of languages. Rails and Laravel are the standouts for just QoL experience, and Getting Shit Done.

They're engineered to get out of the way, and modular or extensible enough to enable deeper modifications easily.

Re:Why Ruby on Rails still matters by danhaywood on Saturday February 22, 2025 @12:03AM (#43136267)
For JVM, Apache Causeway provides similar capabilities (in fact, even more abstracted than RonR). Full disclosure: I'm a committee on that project.

https://causeway.apache.org

Re:Why Ruby on Rails still matters by troad on Saturday February 22, 2025 @01:07AM (#43136499)
In an era where everything and their mother is getting rewritten in Rust, surely we should be able to get a proper, fully featured, batteries included web framework out of it too. But it seems like all Rust web frameworks are either extremely low level (so low level that I don't see their value add at all), or extremely unfinished. Last I checked, even things like "named routes" or TLS were exotic features that required manual (and incompatible!) workarounds.

It's kind of fascinating to me that all the frameworks in 'slow', dynamic languages (Rails, Laravel) are feature packed and ready to roll, and everything in 'fast', static languages is so barren by comparison. The two seem almost exactly inversely proportional, in fact.

A batteries-included web framework in Rust with comparable built-in functionality to Rails, and comparable care for ease-of-use, would be game changer.

Re:Why Ruby on Rails still matters by simonask on Saturday February 22, 2025 @05:21AM (#43137755)
As a rustacean, I completely agree. A big chunk of the Rust ecosystem is obsessed with performance, and sees static typing as the way to achieve that. This approach generates extremely efficient code, but blows up compile times and creates a messy hell of generics (and accompanying type check errors).

I think there is a space for a more dynamic and high-level web framework in Rust, with an appropriate balance between leveraging the powerful type system and ease of use.

Re:Why Ruby on Rails still matters by darkhorse13 on Saturday February 22, 2025 @02:52AM (#43137064)
Django is exactly that for Python.
Re:Why Ruby on Rails still matters by jes5199 on Saturday February 22, 2025 @12:44PM (#43141203)
then why do I keep ending up having to support hand-rolled SqlAlchemy and FastAPI