31–40 of 245 posts
Rails on the backend doesn’t get the credit it deserves. On the front-end it’s been a mess for a really long while now though
I love the new hotwire stuff. What don’t you like about thd front-end?
Propshaft should bring sanity back to it, but its going to be a while before that's mainstream.
> 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 concerning to me that one day one person or organization decides that "we will set the direction".
They don't even try to use nicer language. Don't get me wrong, I respect the work and effort. But 37signals are no saints. There was a scandal, and employee exodus not so long ago.
Hotwire is so deeply integrated into Rails, so Rails is even more 37signals' tool than ever before. Before we had webpack, and JavaScript libraries that sometimes were not easy to use. Now things are easier, but instead of JS libraries we've gotten 37signals dependency, which is VERY concerning.
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.
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)
Are they gonna change the governance at the last minute like with Turbo?
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.
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.
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.
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.
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.
Loose typing is a nightmare. The youngins always learn the hard way.