I haven't seen any new Rails deployments recently but I've also never seen an existing one rewritten to use something else, although I've heard tell of it. It definitely has way less baggage than what you'd call the modern equivalents, I doubt you would regret using it for something personal. But it's probably worthless on resumes these days.

>>107749091
No.

One of the senior engineers at my work is obsessed with it. It seems like a fine notpython from my limited experience but it's annoying that I always have to look everything up on the odd occasion I need to modify his scripts. Personally I write all my tools as C++ native executables. Please be patient I have autism.

>>107749173
>Personally I write all my tools as C++ native executables
Good god

>>107749173
>It seems like a fine notpython
That's a bit of an anachronism, Python 3 took a lot from Ruby.

>>107749275
Yeh well, normal people use python

>>107749091
If you don't already know an equivalent in another language, then go for it.

If you don't already know Ruby, and are learning Ruby concurrently with Rails, my biggest pieces of advice is that, if you are following tutorials or examples, learn which classes and methods of the examples are code that comes from stock Ruby, and which come from Rails' constituent libraries.
My second piece of advice is to keep in mind that Rails is organized into individual libraries, for each of the major affordances it provides:

ActionPack: Web connectivity bits: routes, controllers, request/response, param parsing.
ActionView: HTML templating and JSON rendering helpers.
ActiveModel + ActiveRecord : Models, database query builder, database migrations.
ActionMailer: Email sending.
ActiveJob: Background job abstraction.
ActionCable: Websockets
ActiveStorage: asset storage, e.g. AWS S3.
ActiveSupport: A cross-cutting utility library that also augments core Ruby classes with some useful helpers.

All of these can be included or excluded on any given project. For example if you only want an API server, and don't like Rails' JSON helpers, you can exclude ActionView. If you don't care about Websockets, you can exclude ActionCable. If you don't need to send email over SMTP,, you can exclude ActionMailer. And so on.

>>107749091
No. Learn Java. >>107738273

>>107749091
I remember when this was everywhere like 10 years ago and now it's rarely mentioned lol. So glad I didn't waste time on this lang

>>107749864
It died alongside the classic MVC webapp. Now everything is a separate frontend and backend, and the frontend is usually an SPA or some other NextJS concoction.

>>107750271
MVC is making a comeback though, everybody hates client side complexity nowadays unless it’s for a map app or similar. HTMX, LiveView, Hotwire etc.

>>107749091
use anything popular in the industry

>>107749091
Last time I heart of Ruby on Rails was literally 20 years ago. Boom time may have been RIGGGGGGHT before O'bummer took office in Amerikkka, but the time is over.

I literally do not know of any project that is written on RoR now a days.

Throw in creator shenanigans and why would you write anything in it?

>>107749173
>script
>compiled
that's the opposite of autism
because the two are unrelated

>>107753008
>Throw in creator shenanigans
What shenanigans? Is he a white nationalist or something?

Rails legacy jobs are pretty comfy. A disproportionate amount of 4 day workweek jobs are at rails shops.

>>107749091
just use php. why are people still falling for fads that will cause their code to be unmaintainable. don't be stupid.

>>107750271
and everyone saw that it sucks, the js hate is as high as ever

>>107753190
>just use PHP
>why unmaintainable code

>>107749522 has good points. Rails is great but has frustrated me often with odd behavior. I don't think it's a good financial decision since you won't find many jobs, but I prefer Ruby & Rails over every other stack I've used for my personal projects.

Stay away from Turbo at first. One of the dumbfuck things it does is preload other pages when the user hovers over a link. Then it also caches previous pages and renders those cached versions first. All to make the experience feel "snappy".