Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rails 7.1 Released

github.com

Post reply on HN
Print view View original

101–110 of 245 posts

Re: Rails 7.1 Released

#101

Post by tarsinge »

ywain wrote: post #5
roboben wrote: post #2

Currently stuck on a fairly large code base on rails 6 with a ton of react and trying to upgrade to the new “non”-JS way with Hotwire. Wish me luck Rails is great when you stick with the defaults and a land of pain as soon as you leave them.

I'm working on a fairly recent Rails 7 code base. We initially started using Stimulus, but are now considering switching to React for a few reasons: - if you're looking to hire frontend engineers, the candidate pool for React is a few orders or magnitude bigger - it's getting harder and harder to find vanilla JS packages that you can wrap in Stimulus controllers for common tasks, compared to finding React packages -…

If you have to hire dedicated frontend engineers maybe you have overgrown Rails or it’s not a good fit for your site? I find Rails is awesome when it fits in the model Fullstack engineers with designers, HTML-heavy with JS enhancements on specific views. It’s so simple and efficient when the views nicely match the URL routes and they are mostly HTML, even the designers can work on the codebase.

Re: Rails 7.1 Released

#102

Post by ivandenysov »

roboben wrote: post #2

Currently stuck on a fairly large code base on rails 6 with a ton of react and trying to upgrade to the new “non”-JS way with Hotwire. Wish me luck Rails is great when you stick with the defaults and a land of pain as soon as you leave them.

Try https://vite-ruby.netlify.app/guide/rails.html

It was almost a drop in replacement for webpack for me

Re: Rails 7.1 Released

#104

Post by gomoboo »

roboben wrote: post #33
crystaln wrote: post #25

Earlier quoted context omitted.

But why? So many more performant frameworks for this in strongly typed languages to boot.

Which ones? Never saw another one which comes with the same comfort of batteries included like rails. For example having database migrations built in etc.

ASP.NET (C#) has migrations: https://learn.microsoft.com/en-us/ef/core/managing-schemas/m...

Re: Rails 7.1 Released

#105

Post by tenderlove »

0xblinq wrote: post #66

Rails is great, and better than ever. I've spent most of my early years in the field working with Django and Laravel, then moved to frontend doing [all the usual stuff we do nowadays] and this year I was assigned back to a Rails + Hotwire project. I'm truly amazed how much simpler things are. I feel sad most of us have forgotten how easier things could be, and I'm terrified about new people joining this industry that…

This is great to hear. <3

Re: Rails 7.1 Released

#106

Post by 0xblinq »

ywain wrote: post #5
roboben wrote: post #2

Currently stuck on a fairly large code base on rails 6 with a ton of react and trying to upgrade to the new “non”-JS way with Hotwire. Wish me luck Rails is great when you stick with the defaults and a land of pain as soon as you leave them.

I'm working on a fairly recent Rails 7 code base. We initially started using Stimulus, but are now considering switching to React for a few reasons: - if you're looking to hire frontend engineers, the candidate pool for React is a few orders or magnitude bigger - it's getting harder and harder to find vanilla JS packages that you can wrap in Stimulus controllers for common tasks, compared to finding React packages -…

BTW, if you end up using React with Rails, consider https://inertiajs.com/. It works great with Rails.

Re: Rails 7.1 Released

#107

Post by bnt »

tauchunfall wrote: post #69
steve_gh wrote: post #41

Don't get me wrong, I love Rails, and have been using it off and on since Rails 2. It's a really good framework, and for someone like me who needs to stand up a website from time to time it really is the path of least resistance. What bugs me is the pain of setting up a new laptop to run Rails. I need node, which means npm. I'm a backend guy, I don't understand how to set up node, what order to do things in, etc. I d…

>I'm a backend guy, I don't understand how to set up node I understand that Node is mostly known as a frontend tool and Rails uses it for that, but as far as I remember Node was as least initially developed to bring JavaScript runtime to backends. Even without a package manager node is just a node.exe under Windows, and I think you just have to download and unpack npm and then put node and npm into your PATH environm…

I recently set up a new Win11 laptop and all it took was download Node and install it via the installer. You’re up and running in 90 seconds. Yarn was another 30 seconds (npm i yarn). Even Ruby works well with RubyInstaller, and you can normally develop Rails without WSL if you really want to.

Re: Rails 7.1 Released

#108

Post by 0xblinq »

steve_gh wrote: post #41

Don't get me wrong, I love Rails, and have been using it off and on since Rails 2. It's a really good framework, and for someone like me who needs to stand up a website from time to time it really is the path of least resistance. What bugs me is the pain of setting up a new laptop to run Rails. I need node, which means npm. I'm a backend guy, I don't understand how to set up node, what order to do things in, etc. I d…

The Ruby/Rails community is one of the best and most friendly I've seen. But the worst part of it, by far is the hate for JavaScript.

JavaScript is just a tool, like any other. And it's a very important one like it or not. And like it or not it's going to stay here for a long time.

Just have a bit of an open mind and try to learn the basics at least, it will make things easier.

Re: Rails 7.1 Released

#109

Post by tom_walters »

0xblinq wrote: post #66

Rails is great, and better than ever. I've spent most of my early years in the field working with Django and Laravel, then moved to frontend doing [all the usual stuff we do nowadays] and this year I was assigned back to a Rails + Hotwire project. I'm truly amazed how much simpler things are. I feel sad most of us have forgotten how easier things could be, and I'm terrified about new people joining this industry that…

Interesting to hear your comparison to Django and that you wouldn’t say they’re on par, at least for you, today. Any particular reasons for preferring Rails over Django?

Re: Rails 7.1 Released

#110

Post by bambax »

jshen wrote: post #21
eikenberry wrote: post #8

Earlier quoted context omitted.

> Rails is great when you stick with the defaults and a land of pain as soon as you leave them. You just described every framework. Frameworks are great if your application is fairly simple and aligns with its way of doing things. Libraries are where to look if you need a more complex, flexible setup.

I've worked on tons of old code bases over decades. I've never seen a library based one that's in good shape either. They usually evolve into some half baked homegrown framework that no one understands.

It seems that, at least in the enterprise world, eventually every software project evolves into a hairy monster "that no one understands", choke-full of traps and side-effects that turn around to bite you at the worst and least-predictable moment.

As a result, projects are frozen in time because everyone's afraid of touching anything, less it triggers Armageddon.

Maybe AI can help? Instead of copilot writing new code, or chat systems explaining a couple of lines, there could be an app that ingests a huge code base at once (spanning multiple languages and subsystems) and

- explains what each part does

- is able to spot potential side effects for each new addition

- suggests simpler ways of doing things / nice refactoring

There are some startups trying to address this but none seems to be there yet (I think); the market is huge though and people would pay through the nose for this.

Post reply on HN