Ruby on Rails has been “dying this year” for 21 years. Will this be the year it finally dies?
>>108240112>Empty ThreadYeah.
>ywnba hipster engineer in 2009 silicon valley
>>108240112Ruby is a very good language and I will never hate on it. It doesn't matter if it dies due to AI or corporate pressure. It will always be a beautiful and playful language designed for humans.The world would be a better place if Ruby had won. Alas...
Post your face when you avoided learning this garbage.
>>108240112it's already dead, jim
>>108240112i remember it being somewhat popular in 2005 - 2008. then it just, died.
>ruby dead>rust nextscreencap it
>>108240112Rails is still actively developed and widely deployedit's not going anywhere
>>108240112It is still, by a landslide, the best, comfiest, easiest framework for a solo dev looking to get something off the ground quickly. It's how all web frameworks should work, everything else feels like such tedious trash by comparison.
Rails’ BDFL is an unabashed nazi. As a non-chud, I use Django and nextJS on principle.
>>108240882Didn't die, it became boring tech.
>>108241439Now THIS is cope
Never used itStumble on a ruby script I wanted to useInstall ruby>you need 1gb of msys tooNOPE.jpg>ask claude to convert it in python>does it in 30 seconds
>>108240839CGF had a baby?
>>108240916When people say that something's dead, they mean that nobody uses it for brand new projects in new teams
>>108240112I don't know any Rails developer who is unemployeed.
did rails finally kill perl CGI?
>>108244450PHP did that years before Ruby was even a thing
We’re almost 70 years into COBOL’s promise to eliminate full time programming jobs my making it so easy non-programmers can make entire programs.
Perl won
>>108245899won what?
>>108245919The game, which you just lost.
>>1082461142007 called, it wants its memes back.
>>108247461I called 2007, please take me back :'-(
Ruby is the most pointless language I can think of. There isn’t a single thing you’d be better off using it for over Python.
>>108244432t. DHH
>>108240112Now that DHH has become a chud, the council of troons that control all software development will cancel the project out of existence.
>>108251474Trannies are impotent and only force out impotent leaders, which DHH is not.
i write all my personal projects using ruby and rails, comfy as fuck, specially the latest with their new JIT
>>108253426>Ruby>JITnice, I bet now it's as fast as interpreted Python.
>>108240112Sorry but I personally prefer Personal Home Page (P.H.P.). with jQuery. Did you know that Facebook uses P.H.P.? By 2015, P.H.P. and jQuery will be used by 90% of the top Internet companies in the world such as Nokia, Blockbuster and Sears, serving customers by the millions.
>>108240112better switch to COBOL quick
>>108240882It died because the performance was atrocious and type systems got less bad so that the advantages of dynamic typing weren't as great, and probably really only accrue in image-based systems like Lisp or Smalltalk.
>>108254817The entire ecosystem had shit performance. Heroku, the preferred hosting option for RoR, used AN ENTIRE "dyno" (a virtualized linux instance) to handle each individual client, at a time when many started to consider the thread-per-client model (popular in Java) to be wasteful.It's easy to see why Node.js killed it:>JIT, and a good one>non-blocking IO + event-driven programming>code reuse front-end and back-end
>>108255125>JIT, and a good oneOnly years after it “won” and Google saw it worth pouring real resources into. Node won because of language reuse, plain and simple.
RUBY ON RAILS NIGGERS TRYING TO SEEK ATTENTION TO THEIR SHITSTAINT OF A LANGUAGE. JESUS GET A FUCKING LIFE. YOU DON'T HAVE ANYTHING BETTER THAN REMINDING THIS THREAD ABOUT YOUR "LANGUAGE"?? THE ONLY THING I FIND MORE AUTIST THAN POL IS A NIGGER TRY TO PROMOTE THEIR SHITTY FRAMEWORK AND DEAD LANGUAGE, RAILS IS FOR NIGGERS AND JEETS, GO TOUCH SOME GRASS, NIGGER.
>>108256373All caps is cruise control for schizophrenia
Why can't the shitty things die, like PHP?
>>108240809Ruby on Rails did win, in a way.The verbose-but-intuitive command-line syntax was normalized during the 2010s.90% of CLI apps use it nowadays, you almost never see blarg -fzcf -v3 -g neckbeard horseshit anymore except as additional abbreviations.That said, ruby dependency management is as bad as python's, I don't think ruby's performance issues were ever truly solved, and I think everyone not doing legacy development switched to node or something else.Also:https://crystal-lang.org/https://learnxinyminutes.com/crystal
>>108253426https://shopify.engineering/ruby-yjit-is-production-readyInteresting.Still not inclined to use Ruby's extremely dynamic code for any real-world use though.Imagine spending 2x as much time writing tests as the actual code just to make sure each line actually runs.Couldn't be me.
>>108256969PHP is surprisingly performant, and the ecosystem evolved in the post-Rails world.It has remained popular for a reason.https://www.toptal.com/developers/back-end/server-side-io-performance-node-php-java-go
>>108257232It's still a horrible unfixable mess of a language that is responsible for most of the SQL injection security holes on the internet
>>108256969>>108257251php is the easiest web ecosystem to get a website up an running, and be able to change code on the fly without restarting the web server.verifying code with LLMs can prevent SQL security holes
>>108257270>Yes, it sucks, but AI will fix my curry codeI hate you
>SAAR SAAR YOU MUST USE ENTERPRISE BEANS OR LATEST JAVASCRIPT FRAMEWORK SAAAAARI’ve never met a rails hater that was White.
>>108240280I was
>>108257582Did it feel like salty coins or bags of sand?
I mean honestly, whats better than rails? I dont really want to want php.I've looked at various python frameworks. I don't love them.I recognize that a problem with rails is the "under the hood magic" that can come back to bite you, but I think if youre experienced you can avoid that. and its not like python doesnt do that. like look at djangos database migrations. I don't like the way they make migrations for you from code
>>108255514>Only years after it “won” and Google saw it worth pouring real resources into.V8 predates Node.js
Multiple thing I use have been "dying" for more than 2 decades. Those words have always been meaningless chaff from detractors or parrots.
>>108259215Oh shit you’re right. I thought chrome used a different engine until later but you’re right, it was there from the start.
>>108248635Ruby solved the problem of Perl being unparseable back when Perl was very popular.But then Perl just died one day and Ruby followed suit not long after.Like another anon said, you won't find any new projects being started in Ruby [or Perl].
>>108257141this exact same issue gave me a nice job as qa automation engineer
>>108257232there are zero chances that node is almost twice as fast as java and go
>>108261793okay I can't read apparently xdBut the same goes for php being faster than java
>>108240112COBOL is still a thing that pays decent bucksRoR can't even.
>>108257064>verbose-but-intuitive command-line syntax wasPowerShell did that first.
>>108256373lol u mad bro?
>>108262735Powershell: 2006Ruby: 1995The command line stuff has nothing to do with Rails
>>108257064>90% of CLI apps use it nowadays, you almost never see blarg -fzcf -v3 -g neckbeard horseshit anymore except as additional abbreviations.honestly i never understood why anyone could think it was a good idea, i think it's ok for debug shit and prototyping but nothing should release with those as the sole available options
>>108243478I've used Ruby for a decade and I've never heard of "msys", never mind had to install it.>>108257064>That said, ruby dependency management is as bad as python'sI disagree. I use both Python and Ruby by and by, but I don't blindly love either. One of the things I have liked about Ruby over Python has been the package and dependency management. The Ruby ecosystem seemed to have settled on a solution from the start, while the Python projects keep adding new tools every 2-3 years instead of just fixing or updating an existing ones. At least uv seems like it has a shot at being a longer-lasting solution.The downside to Ruby's approach is not in the dependency management, but the way the VM's runtime handles constant resolution. Modules aren't truly "namespaces" the way other languages have them, and any file can "require" and cause constants to be available for the entire rest of the application. Pythons imports are much more similar to basically every other language out there.I've always found ways to work around the quirks of both, but Python's ecosystem has caused me far more confusion and friction.
Ruby itself is too much fucking magic. It was actually completely fine in the beginning with "fat models and fat controllers" but then they "clean coded" the fuck out of everything and you have to go through serveral layers of objects to find out how something works to get to the real business logic.
>>108265018You mean Rails. It's entirely possible to write Ruby as straightforward as you would like.The "Rails Magic" is a bunch of string-matching metaprogramming bullshit, and I agree it is barely tolerable at best, wasteful at worse.On the other hand, the "go through several layers of objects" is an architecture choice of the application. Nothing's stopping you from just wrapping a call to this-or-that business logic directly from the model. You get the best of both worlds: isolate complex business logic into classes that do-one-thing-well, and it's all still discoverable from the model.
>>108240112legacy software never dies, same as java 8 that is still alive today and will probably never die
I heard you write Chef recipes in ruby, I might look into that tool for automation
>>108257319Just code properly?
>>108240112no lol.In fact anytime someone proposes alternatives to MVC, people just end up coming back to MVC because the alternatives are far, far, worse.>>108243863I've talked to people in startups working with rails. It's still be deployed even on new projects.
>>108266789Easier to do using a language that was actually designed
>>108266992True but there are plenty of non-rails frameworks doing MVC nowadays. Rails inspired a lot, but Rails itself I’d argue is a lesser version of Django, Laravel, or even Spring Boot at this point.
>>108266992>I've talked to people in startups working with rails. It's still be deployed even on new projects.If you need to go from zero to a non-SPA basic web app as fast as possible, then $LARGE_MVC_FRAMEWORK is the way to go. It's just a question of which language you already know, and the state of the various frameworks in those languages.For example, if you already know PHP and know zero Ruby, you'll ship faster in Laravel.And if you already know Python and know zero Ruby, you'll ship faster in Django.But if you know Ruby as well (or better) than those, Rails will be the fastest route to building something.
>>108240112No technology ever truly dies, it just gets reduced down into isolated pockets of decaying infrastructure in various companies.There's garbage PHP code I wrote back in 2009 that is STILL in production. We still have a few Visual Basic 6 projects at my current job.
