So many major tech companies who used to use Ruby On Rails have now moved away from it. What went wrong with Ruby On Rails?
because its stupid easy to prototype something with a a handful of people themselves, when they had the money they could hire profesionals to make it truely theirs
>>108725497the problem is moreso ruby itself than rails being badrails is fine, but ruby's semantics don't scale well as your team scalesreally, it's the reflection that kills it because you end up with a bunch of people doing god-knows-what random shit just to get something out the door and no one can decipher how it works without building some hacky introspection toolyou end up with simple problems taking days or weeks to solve, just doesn't scale when you have 1000s of engineers working on the codebaseand the gem system is ass, imagine if you had to rewrite jquery from scratch everytime you switch companies, that's what working with ruby gems is like
>>108725497because anything abstracted to that level cannot be fast
Scaling issues mostly, and monkey patching becoming unmaintainable. Then a lot of its key people went on to make Elixir because they were tired of Ruby's scaling issues.
>>108725497If you ever tried to self host gitlab you know why
Because tech companies started hiring non whites/non Japanese, and they can't handle the freedom Ruby gives youJava and go were created so brownoids wouldn't break everything
>>108725497Java is dead too. Only Python and Typescript on Node.js matters anymore. Go if you're serious about performance and have an autist as a CTO.Nobody uses anything. Well except COBOL but that's all H1Bs or offshored and it's days are numbered anyway.
>>108726632This
>>108726642>Only Python and Typescript on Node.js matters anymoreNo serious business uses Node for their main backend.
>>108726642>Java is dead tooIDK how many new projects use java but spring boot was big in the 2010s and its still widely used today.LLMs love typescript for some reason, maybe the type system plays well with how the AI works.
>>108726869yes, but in tech terms, the majority of businesses are unserious
Pre-JIT Ruby is a rare example of a language that makes CPU time more expensive than dev time. And it's still pretty fucking slow.
>>108725497the appeal of rails is that it's opinionated so you don't have to micromanage every aspect of your site to get something running. the first time i used it i was surprised how little you actually had to write to get something functional. but yeah, when your product gets fuck-huge you need to tinker with those details and you kind of lose the main selling point. i'm sure the backend of each of those is a mess of microservices now.supposedly the performance of rails has gotten way better in the last 10 years and shopify uses it for like a million transactions per second. i still see plenty of job postings advertised looking for rails experience, but i think once shopify inevitably drops it, then it will be on the same level as php where it's mostly considered a "legacy" framework that nobody should ever build a greenfield project with
>>108727012DHH on suicide watch
>>108726869No idea what you imagine as a "serious business", but all those corpos get scammed by Oracle.And that is not because corpos are so super smart and serious, it's because of the opposite: Large corpos have incompetent detached administration.Did you know that the legal department of Oracle does over 3000 licence audits in corporations per year and the average settlement per audit is multiple million $$$?They make tens of billions by sending lawyers into fellow corpos who were dumb enough to buy an Oracle product.
>>108727119my experience tells me that oracle could threaten to abduct and rape your children for violating their license terms and managers would still worship them
can ruby (not necessarily rails) be revived? i loved writing ruby
>>108725497Because its ass and always has been>explicit is better than implicit>>108725615Nope it really is just rails. ActiveRecord specifically
>>108725497not cute enough to attract developers
