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

51–60 of 245 posts

Re: Rails 7.1 Released

#51

Post by abigail95 »

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…

What are you comparing Node to?

Other typical back ends are more complicated (except Go) Java, C#, Python for example

Re: Rails 7.1 Released

#52

Post by Rapzid »

crystaln wrote: post #25
roboben wrote: post #17

Earlier quoted context omitted.

I agree. What are options here? Rails in API-only mode?

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

The performance of Rails serializers is still a nightmare. God awful performance.

Re: Rails 7.1 Released

#53

Post by ulizzle »

bradgessler wrote: post #31
Pungsnigel wrote: post #19

Earlier quoted context omitted.

I love the new hotwire stuff. What don’t you like about thd front-end?

Asset pipeline is a hot mess: https://fly.io/ruby-dispatch/making-sense-of-rails-assets/ Propshaft should bring sanity back to it, but its going to be a while before that's mainstream.

That has been a hot mess for almost a decade now.

Re: Rails 7.1 Released

#54

Post by lolinder »

abigail95 wrote: post #51
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…

What are you comparing Node to? Other typical back ends are more complicated (except Go) Java, C#, Python for example

For Java, sdkman is great—essentially as convenient as nvm.

Python is a disaster.

Re: Rails 7.1 Released

#55

Post by Rapzid »

roboben wrote: post #38
crystaln wrote: post #36

Would anyone start a new project with Rails today? If someone suggested using Rails for a new project to me today, I would show them the door. There are so many more mature frameworks in more robust and performant languages. IMO the only reason to use Rails today is if you’re too uncurious to learn something better.

Please name a few with the same comfort of having most things built-in. One example: database migrations. In the JS world it is knex all over and it is much less comfortable than ActiveRecord.

Personally I would rather use Fastify+MikroORM.

Or Asp.Net.

Or Flask with SqlAlchemy + the migration and validation libs(marshmallow?)

Or whatever is good in Golang.

Re: Rails 7.1 Released

#56

Post by winrid »

roboben wrote: post #38
crystaln wrote: post #36

Would anyone start a new project with Rails today? If someone suggested using Rails for a new project to me today, I would show them the door. There are so many more mature frameworks in more robust and performant languages. IMO the only reason to use Rails today is if you’re too uncurious to learn something better.

Please name a few with the same comfort of having most things built-in. One example: database migrations. In the JS world it is knex all over and it is much less comfortable than ActiveRecord.

I wonder if anyone here has used ebean and the generated db migrations? I was looking for a java ORM that's like Django's ORM with the built in generated migrations tool which is great for a lot of projects - it seems like ebean is pretty much the best choice? and now with virtual threads I don't have to worry that it's not reactive.

Re: Rails 7.1 Released

#57

Post by gherkinnn »

RomanPushkin wrote: post #32

I hope to see the Hotwire dependency dropped one day. I love Rails and Hotwire, but I wish the latter were also a community tool. When TypeScript support was discontinued, DHH commented: > This project has been founded, funded, and maintained predominantly by the resources and investment of 37signals. We will set the direction as we see fit... With TensorFlow recently discontinuing support for Windows, it's very conc…

The Turbo incident was none. It just wasn’t. I would not have dropped TS but the change barely matters. I have only ever seen it used in a script tag and the code reads well enough in vanilla.

The actual incident was a horde of morons piling on top of that repo in the days that followed.

Re: Rails 7.1 Released

#58

Post by lettergram »

itake wrote: post #6
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 lost faith in rails JS integrations. I either do SSR with slim or do API only with a separate frontend. Rails changed direction too many times trying to do JS (coffee script, asset precompiling, webpack, etc)

I’ve taken a rails 4 through to rails 7. Kind of interesting each major version is basically denoted by a change in the way they handle JavaScript.

Rails 5 & 6 were rough, you forgot yarn! That was my biggest pain point. I still have Coffeescript code, we have been slowly converting as needed.

Rails 7 has been a lot better to deal with, we use vanilla JavaScript (outside the coffeescript lol). Makes it pretty easy tbh. We load partials as needed (via js) and the site is fast and light.

My recommendation is to stick close to html with rails or as mentioned, a separate front end. What we have works super well for us, but definitely custom

Re: Rails 7.1 Released

#59

Post by lolinder »

bdcravens wrote: post #40
crystaln wrote: post #23

Earlier quoted context omitted.

Loose typing is a nightmare. The youngins always learn the hard way.

20+ years of experience here, I happily reach for loosely typed languages in most circumstances.

Can you elaborate on what circumstances you're referring to?

The field is extremely diverse these days, and tools that are appropriate for small data science teams may not work as well in enormous monorepos maintained by thousands of developers (and vice versa). What's missing from most discussions of static/dynamic typing is context—each career is unique and what projects you've worked on will have a huge impact on your perception of which is preferable.

Re: Rails 7.1 Released

#60

Post by keyle »

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've never done rails, please tell me, why does "ruby on rails" need nodejs for?

Also it's fairly easy to install node. Too easy in fact. I wish it was much harder, and required a degree.

Post reply on HN