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

71–80 of 245 posts

Re: Rails 7.1 Released

#71

Post by RomanPushkin »

gherkinnn wrote: post #57
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.

None? They ignored multiple instances of community feedback. Broke countless current PRs and upstream libraries. And moreover, going forward I expect another surprise from them. Another surprise that I ain't gonna like.

Rails backend is in a good shape, but I don't like being dependent on a dictator's decisions on the frontend. I don't understand why Rails team don't understand that.

But from the other side I'm thankful to DHH, because now I use more Elixir, and Crystal. Those are awesome tools, and 37signals-free world feels so much better. It's not toxic.

Re: Rails 7.1 Released

#73

Post by itake »

nerdwaller wrote: post #13
itake wrote: post #7

Earlier quoted context omitted.

Coding in rails since 2012 here. I lost faith in rails at 5.2. Active storage was so terrible.

What is terrible about active storage?

My memory is fuzzy, but...

1. all data flow through the rails app (no pre-signed s3 upload or download links for direct uploading).

2. no support for CDNs (I think newer rails versions added support)

3. blobs and attachments were unnecessary abstractions.

3a. Querying was annoying (extra joins) and easy to add n+1 queries.

3b. In my app, images are moderated and it was unclear where to put the moderation metadata (on blobs? attachments? create a new table? why so many tables?) or `deleted_at` type columns.

4. GraphQL gem didn't support it: https://github.com/rmosolgo/graphql-ruby/issues/1777

Re: Rails 7.1 Released

#74

Post by diogenes4 »

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.

Same reason as always—it's useful for rapid prototyping. It's not like the frontend was ever rails's strong suit.

Re: Rails 7.1 Released

#75

Post by crystaln »

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.

For quick scripts sure.

For writing an application or something that actually require design and libraries? Why bother? You need to be meticulous anyway, why not be meticulous in code?

Re: Rails 7.1 Released

#76

Post by crystaln »

Rapzid wrote: post #52
crystaln wrote: post #25

Earlier quoted context omitted.

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.

20 years on…

“Just use another framework when you need performance” they say.

Re: Rails 7.1 Released

#77

Post by yxhuvud »

stevebmark wrote: post #14
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.

Goodreads is an example of a Rails victim like yours. They customized the app on top of Rails, and it's been so bad that Goodreads is dead in the water and has not received major tech updates despite Amazon throwing engineers at it. Ruby is a dangerous language to refactor, so often you're locked for a long time. See also: Every blog post about Rails upgrades ever (see also: Stockholm syndrome)

> despite amazon throwing engineers at it

Yeah, that is one way of phrasing it. Another way to phrase it is that Amazon took it over, turned it into an ingestion funnel to their book store, and has done as little as possible after that.

Re: Rails 7.1 Released

#78

Post by pdntspa »

eikenberry wrote: post #8
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.

> 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.

Rails is really flexible, though.

Re: Rails 7.1 Released

#79

Post by mplewis »

0xblinq wrote: post #63
technion wrote: post #34

Earlier quoted context omitted.

You'd be surprised how many candidates would prefer to just take another job. If for no other reason than resume building with the word react.

Then that was not a good candidate from the get go? What about hiring people that really care about the product they're building and not just tool fanatics?

One good reason to avoid a job doing Hotwire is so that you can take a job doing React for a similar amount, where your experience applies better and where you'll gain more transferrable experience.

In short, it's probably better for your career to work on React.

Post reply on HN