Like, ruby built in iteration in the 90s, now most languages have bolted this in for easier looping.
Ruby makes everything an object so I can chain methods, JS then did the same and people love it there and hate it on Ruby because it’s “confusing”.
Ruby uses a different OO paradigm where you worry about messages between objects and this allows for duck typing and fast development. Other languages don’t like this and that’s fine, no one way is right.
The point is the arguments are often from boring or thoughtless people that just wanna argue and it doesn’t matter what you do, they won’t like it and that’s that because “well, it’s just WEIRD” which just means “I don’t know this so I don’t like this”.
Also, look at the work with the JIT and rust right now and tell me that’s a dead language with a straight face.
I actually agree with them lol which is why I’m expanding to other technologies, right now python/Django.
I worked with rails for 7 years and I absolutely love it. But I’m personally seeing the writing on the wall that I have to either expand my breadth of skills to stay relevant for the next 10+ years
I would tell them that this is total nonsense. Yes, RoR is kinda main thing for what Ruby is used for, but it is great scripting language for rapidly prototyping scripts or tools. For example tool like Metasploit which the #1 pentesting framework outhere, written in Ruby and it’s included in Kali Linux distro for cybersecurity specialists.
There is Cucumber framework for behavior-driven development (BDD), which allows to test software for businesses. It is considered to be most popular one.
Jekyll – one of the best static-site generators.
Crystal, functional language designed for building scalable and maintainable applications, has a simplicity of Ruby syntax and high speed of complied languages like C.
There are a lot more tools built on Ruby, and with new version of Ruby and improvements we’re going to see more coming.
Generally, I usually don’t bother answering them. I just go to work, write Ruby, and get paid for it, thus disproving their argument.
But if you need some data, there’s always the fact that I get multiple emails _every day_ from recruiters looking to fill six-figure RoR roles. That’s not something you see for an irrelevant or legacy technology.
I’ve seen recent projects where RoR were key to success. Software made with Rails looks great, feels great, snaps, and has more features with same amount of devs than other frameworks. It’s a framework where you code directly what you want to do instead of having to do irrelevant work.
You still need today a backend. A Rails backend is a solid choice that allows you to build anything on top of it with the latest technology. Want the latest JS wramework? You’ll have it. An API for a native app? Easy. Etc.
Touch grass. You really don’t need to argue w people who think a technology like RoR is legacy.
These are the same people who spend 4 weeks working with a shiny new framework to deliver subpar performance that they would with any framework just to switch to an even newer framework mid product release lol.
Github and Shopify. Done.
Stripe would like a word on the Ruby side of things.
Github (gitlab), Shopify, Twitch, Airbnb, Groupon, Hulu, Kickstarter, Soundcloud, etc.
Also, Hotwire is the most awesome thing that happened to Rails in the past 10 years.
Is it really sufficient as an argument though, that a bunch of well-known companies are continuing to use it?
What are the advantages of RoR against other modern frameworks?
I can build web apps faster than them.
Most anti ruby arguments makes no sense.
Like, ruby built in iteration in the 90s, now most languages have bolted this in for easier looping.
Ruby makes everything an object so I can chain methods, JS then did the same and people love it there and hate it on Ruby because it’s “confusing”.
Ruby uses a different OO paradigm where you worry about messages between objects and this allows for duck typing and fast development. Other languages don’t like this and that’s fine, no one way is right.
The point is the arguments are often from boring or thoughtless people that just wanna argue and it doesn’t matter what you do, they won’t like it and that’s that because “well, it’s just WEIRD” which just means “I don’t know this so I don’t like this”.
Also, look at the work with the JIT and rust right now and tell me that’s a dead language with a straight face.
I actually agree with them lol which is why I’m expanding to other technologies, right now python/Django.
I worked with rails for 7 years and I absolutely love it. But I’m personally seeing the writing on the wall that I have to either expand my breadth of skills to stay relevant for the next 10+ years
I would tell them that this is total nonsense. Yes, RoR is kinda main thing for what Ruby is used for, but it is great scripting language for rapidly prototyping scripts or tools. For example tool like Metasploit which the #1 pentesting framework outhere, written in Ruby and it’s included in Kali Linux distro for cybersecurity specialists.
There is Cucumber framework for behavior-driven development (BDD), which allows to test software for businesses. It is considered to be most popular one.
Jekyll – one of the best static-site generators.
Crystal, functional language designed for building scalable and maintainable applications, has a simplicity of Ruby syntax and high speed of complied languages like C.
There are a lot more tools built on Ruby, and with new version of Ruby and improvements we’re going to see more coming.
Generally, I usually don’t bother answering them. I just go to work, write Ruby, and get paid for it, thus disproving their argument.
But if you need some data, there’s always the fact that I get multiple emails _every day_ from recruiters looking to fill six-figure RoR roles. That’s not something you see for an irrelevant or legacy technology.
I’ve seen recent projects where RoR were key to success. Software made with Rails looks great, feels great, snaps, and has more features with same amount of devs than other frameworks. It’s a framework where you code directly what you want to do instead of having to do irrelevant work.
You still need today a backend. A Rails backend is a solid choice that allows you to build anything on top of it with the latest technology. Want the latest JS wramework? You’ll have it. An API for a native app? Easy. Etc.
I use bank notes to dry my tears…
What are their arguments for why it’s irrelevant/legacy? Really hard to rebuke an argument unless they have some support for why they think it’s true.
Touch grass. You really don’t need to argue w people who think a technology like RoR is legacy.
These are the same people who spend 4 weeks working with a shiny new framework to deliver subpar performance that they would with any framework just to switch to an even newer framework mid product release lol.
One cheeseburger and a diet cola.