Live data from Hacker News

Rails 7.1 Released

github.com

171–180 of 245 posts

Re: Rails 7.1 Released

#171
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…

Did you ever try Jump Start Rails or Bullet Train?

I’m thinking of building a side project with Rails and I’m wondering if they are worth it?

Re: Rails 7.1 Released

#172
post #5

Earlier quoted context omitted.

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're looking to hire frontend engineers, the candidate pool for React is a few orders or magnitude bigger Can't these candidates quickly learn Hotwire? Seems like its much simpler than React (less moving parts)

> Can't these candidates quickly learn Hotwire?

Main issue I've seen is Rails shops don't hire devs without Rails experience, or expect you to interview well with backend OOP type code.

I guess that's okay for someone wanting to get away from frontend and be "full stack", but it's not for a lot of people.

Re: Rails 7.1 Released

#173

Earlier quoted context omitted.

As someone who's spent the bulk of his career in Rails and then Phoenix, to me it's the other way around: everything else is just so goddamn slow and unproductive. Don't people realise that it doesn't have to be like this?

Wait, are you saying that you are more productive in Rails than in Phoenix? That seems to be the opposite of what the consensus view in this thread is.

No, I'm saying that I'm more productive in either Rails or Phoenix than I am in anything else.

(And of the two, I'm more productive in Phoenix, but I didn't mention that in the comment you're replying to.)

Re: Rails 7.1 Released

#174

Earlier quoted context omitted.

Wait, are you saying that you are more productive in Rails than in Phoenix? That seems to be the opposite of what the consensus view in this thread is.

I'm reading it as "Rails and Phoenix is more productive than other technologies".

Yes.

Re: Rails 7.1 Released

#176
I am hoping for a renaissance of Rails + HTMX with some sprinkles of JS on very interactive pages.

Using Rails with Slim/HAML is an absolute bliss. If you prefer there are also libraries like `ViewComponents` that can facilitate partial rendering even further. Add in some web components and you can build very interactive pages with it. Even use React if you really need it in specific pages.

HATEOAS cuts the complexity of applications drastically. And if you still need APIs, it's extremely easy to respond to different mime types and even have the same endpoints if you desire.

IME the majority of applications that use React don't need it at all. They use React for a couple of menus that have to pop ups. So hopefully once some larger apps start popping up with no React (or only sprinkles of it), it finally clicks for some people how unnecessarily complex our applications are today.

But I already read comments saying they need to switch to React because everyone else uses it. SMH.

One can dream!

Re: Rails 7.1 Released

#177
post #5

Earlier quoted context omitted.

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're looking to hire frontend engineers, the candidate pool for React is a few orders or magnitude bigger Can't these candidates quickly learn Hotwire? Seems like its much simpler than React (less moving parts)

Stimulus is considerably simpler than React, imo. Turbo, with frames and streams, might take a little time to get the hang of, but it's not overly complex either.

Re: Rails 7.1 Released

#178
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…

Did you ever try Jump Start Rails or Bullet Train? I’m thinking of building a side project with Rails and I’m wondering if they are worth it?

I am on JumpStartPro and quite happy about it. It has all the common gems already included and ready to configure. It also has a lot of excellent code that shows me how to do things.

Re: Rails 7.1 Released

#179

Earlier quoted context omitted.

I love rails. Hardly anyone is using it in my country, and the companies that do are looking for absolute wizards. Because I can’t find jobs using it, I do t get enough experience and lose out to said wizards (after the jobs stay open for 12+ months). Instead, I’m spewing yet more JS into the world because that’s where the demand is :/

What’s limiting you to taking jobs in just your country? I’ve got a gal working for me in Nepal out of all places. Previously had a guy in Jamaica.

I live in a very HCOL country, companies abroad can’t match local market pay.

Re: Rails 7.1 Released

#180
post #119

Earlier quoted context omitted.

DHH removed TS from Turbo, posted a pretty inflammatory blog post about it and then got surprised when people reacted badly to it. Classic DHH stuff really.

A significant part of that ""reacted badly"" was a bunch of kids and YouTuber idiots spamming GitHub with meaningless comments, issues and PRs. Those people don't come out of it looking respectable, regardless of DHH's approach.

I mean yeah sure but DHH does seem to enjoy the controversy a bit. Either that or he’s really good at unintentionally courting it.
Post reply on HN