Live data from Hacker News

I Miss Rails

chanind.github.io

31–40 of 522 posts

Re: I Miss Rails

#31
>> I’m not suggesting that we give up React and es7 and go back to writing server-templated web-apps like it’s 2012 again

Actually I have gone back to server-template development using Django for selected projects, after many years working with React, which I still love.

Server side templated development with Django can be extremely fast in terms of development time, very direct and effective.

There no need to use React for all the things.

Sometimes React is the right tool, sometimes server side templated is the right tool.

Re: I Miss Rails

#32
post #11
post #4

Why miss it, come on back, the water's still warm and the dev is still as fast as ever in Rails. Honestly, the JS stacks all seem vastly more annoying on so many levels. It seems like the JS ecosystem changes so fast because it knows better is possible, so it just tries to reinvent itself over and over. The JavaScript world starts with this weird prototype based language with a syntax that looks like it might be some…

Oddly I never considered starting a new project with it, but now I'm questioning why that is. I guess I just don't see many new projects started in Rails, and nowhere I've worked the past few years uses it. I stopped using it after Rails 3, but I'll give it a try again in the next side-project I work on and see how it goes.

Rails is used heavily even for new projects under the GOV.UK umbrella. The emphasis on accessibility and usability of government sites/applications weigh in favour of more-traditional stacks.

Re: I Miss Rails

#33
post #11
post #4

Why miss it, come on back, the water's still warm and the dev is still as fast as ever in Rails. Honestly, the JS stacks all seem vastly more annoying on so many levels. It seems like the JS ecosystem changes so fast because it knows better is possible, so it just tries to reinvent itself over and over. The JavaScript world starts with this weird prototype based language with a syntax that looks like it might be some…

Oddly I never considered starting a new project with it, but now I'm questioning why that is. I guess I just don't see many new projects started in Rails, and nowhere I've worked the past few years uses it. I stopped using it after Rails 3, but I'll give it a try again in the next side-project I work on and see how it goes.

> why that is

We as a profession seem to be perennial victims of availability bias.

We're naturally going to think of the stuff we've been reading about lately on the Internet first. Which is just never going to be the established and stable stuff that'll let you get your job done without producing any blog-worthy experiences in the process. "Went home after 8 hours without producing any fodder for war stories" doesn't make for an interesting tweet, let alone post on Medium.

Re: I Miss Rails

#34
post #25

Yep, 100%. In the process of converting a node/typescript API to rails. I'll never make this mistake again.

You’re going from TypeScript to Ruby?

Having tasted the joys of static type checks combined with a unified front/back data model, IMHO, that’s unthinkable.

Re: I Miss Rails

#35

> if the modern equivalent of Rails already exists, please let me know! You're in luck. Rails 5.2.3 was released 20 hours ago. More seriously, I feel rails is still excellent and I'm happy to work with it every day. I'd be interested to hear more about what makes rails not modern? I find it a very productive framework. EDIT: If you're talking about missing a JS equivalent of rails, do you know about Loopback? https:/…

I know this is the opposite of what you asked but I find Rails to be keeping pace with modernity much better than its conemporaries! Django seem to have given up on integrating websockets (ActionCable has been in Rails for literally years now), nor is there trivial integration for JS assets/asset pipeline functionality. I don't write much of either anymore, but I'd still reach for Rails the instant I need to get some…

for websockets, django has django-channels https://channels.readthedocs.io/en/latest/ . But I do agree, django has been a little late to this party.

Re: I Miss Rails

#36
post #4

Why miss it, come on back, the water's still warm and the dev is still as fast as ever in Rails. Honestly, the JS stacks all seem vastly more annoying on so many levels. It seems like the JS ecosystem changes so fast because it knows better is possible, so it just tries to reinvent itself over and over. The JavaScript world starts with this weird prototype based language with a syntax that looks like it might be some…

coming from the django-world, i had the same complain with rails. It was a little too fast for a me.

Re: I Miss Rails

#37
post #30
post #8

I’ll say this: I came to Rails from Node (and before that .NET but with a way smaller scope of responsibility), and I am thoroughly convinced the author is correct. I couldn’t estimate for shit in my first few months at this job (once I had ramped) because Rails makes things that would’ve taken at least twice as long easy to do, even without gems. Plus, I have seen not even a third of the compatibility issues between…

I believe Shopify is built on Rails and is (or was) a Rails monolith. It's worked well for them.

Shopify, Github, Gitlab are all built on rails. Even Twitter was on rails in its early days.

Re: I Miss Rails

#39
post #12

AWS Amplify is becoming the "Rails" of serverless. It already has impressive code generators for GraphQL.

I was just playing with Amplify the other day. I was super impressed with the graphql codegen. I think the Rails comparison makes sense with the exception of the vendor lock-in. I haven’t looked at the Serverless framework very closely, but I know it’s not tied to AWS. I wonder if that’s a better comparison to Rails?

Re: I Miss Rails

#40
I still write Rails applications regularly, some applications I've maintained since 3.0 to 5.x.

What's amazing, is I booted up a 4 year old project in minutes the other day at work. A co-worker was interested in using the project, it took 15 minutes to setup clean.

Overall, I find Rails is easily more maintainable and definitely enjoy it more than the Django and Flask apps I write regularly. Javascript (Node + React/Angular) breaks all the time when upgrading, so maintaining it is not super fun either...

Here's a project I wrote in Rails and deployed late last year:

https://hnprofile.com/

Works like a charm!

I even recommend Rails to new people starting out because I think it sets best practices.

Post reply on HN