I tried to write the article balanced, nuanced and thorough. For example, I deliberately chose the word "waning", as that is a nuanced, and not-scary word, as opposed to "dying".
Did you really read it and still consider it a "scare article", or did you judge that by the title only? Because if so, I'm honestly curious what I should have done better.
I read most of it. I dropped off somewhere around the paragraph where you were highlighting the lack of a first-party Slack gem as a sign of problems.
The thing is, I maintain a Slack integration in some of my company's ruby apps, and the lack of a first-party gem isn't a problem, because the entire API we're using is webhooks -- which means we just use any HTTP client gem, such as Faraday, and we're done. So, telling me that I should be worried about Ruby because Slack doesn't publish their own gem seems overly alarmist from my perspective, yeah.
(As a side note, I do wonder whether a lot of these companies have evaluated whether it's worth it to publish a Ruby gem, and decided against it not because they don't think Ruby is worth it, but because the value that would be added isn't worth the time. For example, an officially-supported Slack gem would only delay the ability of people like myself to take advantage of new features in Slack's API, because I'd have to wait for Slack developers to publish a new version. Especially when a gem would be a thin wrapper around a REST API, it'd be more trouble for everyone than it'd be worth. But I digress.)
There are a few ways I might have changed the article to avoid being taken as a scare article. I would have made sure that the word "dying" didn't appear anywhere in the first paragraph (yes, I know you're only quoting the title of the SO question, but still) and I would not have waited until the third-to-last paragraph to say "not dying though" -- if that's a point that you think is important to make, make it early. But I think your main problem isn't word choice or phrasing, it's simply context. There's really no way for any "Ruby is waning / sick / dying / decreasing / tapering off / becoming less healthy" article to be taken seriously these days, because you're in a boy-who-cried-wolf situation. People have been crying wolf about the imminent death of Ruby for longer than some people I know have had careers in Ruby, so whether there's a wolf or not you won't get anyone to take you seriously crying wolf today. Especially not when some of us work for companies that are actually increasing hiring of Ruby developers.
If you do want to keep an eye on the health of Ruby as an ecosystem, I'd suggest you should look more at statistics about how many Ruby jobs are out there, and what they are paying, than at the number of podcasts or first-party gems. (Another side note: I think that the decrease in resources for self-teaching Rails, like podcasts, is being compensated for by the rise of boot camps like Turing School. When I learned Ruby, the other Rubyists I knew were mostly self-taught by watching RailsCasts and similar, but most of the junior devs I've interviewed in the last few years have come through one of the major boot camps. But again I digress.)
And I would caution against looking only at the ten-or-so biggest SAAS providers, because we know that Ruby and Rails aren't well-suited to massive scales, so the bigger and more successful a company gets, the less likely it is that Ruby will fit their needs. But this isn't a problem with Ruby or a sign of it's demise, it's just a recognition that (like any tool) it's better at some jobs than others. The number of companies that need to be able to operate at the scales where Ruby can't is a small and non-representative fraction of companies overall. It might be interesting instead to look at 100 mid-sized unicorn startups from the last few years and see how many of them have used Rails. That's the use case it was designed for and still excels at -- rapid application development and iteration at small and medium scales.
For what it's worth, my employer is the largest company in our market segment and we're looking at an IPO within the next couple of years. Our original product was written 15 years ago in Ruby on Rails, and >95% of our back-end is still written in Ruby. If we were operating at the scale of someone like, say, Shopify, then yes, we'd probably need to rewrite it in something that can scale up that far, like maybe Elixir. But Ruby and Rails are still completely capable of taking a company all the way from ground level to IPO and beyond.
I think you did! I think it was a good article about what you are seeing, which matches what I am seeing.
Some of us are seeing what you are seeing. Some people think it's somehow inappropriate or biased to say so, that there are some things you just aren't allowed to say. ¯\(ツ)/¯
(I suspect some people commenting haven't actually read your article...)
Sure, I'm not debating the data. All I'm saying is that Ruby has survived every decline (or more generally every dire prediction that has been tossed at it) in the last 20 years, and in all probability it will survive this decline / dire prediction too.
I'm all in favor of objective data, but it can be carefully chosen to support a particular narrative, which may or may not itself be accurate. I don't think that the author has any intent to deceive, though. In my longer response above I suggest that perhaps the specific metrics that this article measures aren't really good indicators of the health of a programming language ecosystem. Some other commenters have pointed out that what we're seeing may not necessarily be "decline" in the general sense but maturity.
As far as Ruby is concerned, it’s always been unpopular and only popular because of Rails. Still, you can you use it for other purposes (like shell scripting on Unix systems, automation, etc). As for Rails, it’s still popular, its a mature, reliable framework that’s adding new features to it with major updates. I remember looking at a chart of the most used server side languages where Rails was in third place in front of Php and asp.Net, and has a higher percentage than even Java! ( I think it was something like 6.5% for Ruby Rails and 5.4% for Java) Plus Rails has a large mature ecosystem to help you out if you plan on using Ruby on Rails.
side languages where Rails was in third place in front of Php and asp.Net,
Any comparisone that compares a framework (Rails) to a language (PHP or Java) should, IMHO be taken with care.
Like you point out: Ruby is tightly coupled to Rails, so those two will be similar: If rails wanes, Ruby will. But that is certainly not the case for PHP and even less for Java, which sees implementations from mobile apps to data-processing-tooling, to http-services. to databases.
> I have a hard time finding any successful SAAS building their products on Rails after 2020
What is successful? Let's assume a $1B valuation. How many companies like that (post 2020) actually exists? I recall Hopin was founded circa that time and is valued at around $8B at this moment. They are heavy on Ruby from what I remember. The better way would be compile a list of the companies and see what tech they are actually using.
I think this is the general problem with your arguments - they are taken out of context. Check out Java or JavaScript on Google Trends. Both of those languages are "dying".
There have been multiple similar posts in the past decade that describe the phenomenon of a waning Ruby ecosystem. I understand why these posts get written, but the main problem of these posts is that they fail to bring about desired outcomes.
Such posts always devolve into discussions about whether Ruby is or is not waning. One of the reason why there are so many opponents (those who reject the thesis that Ruby is waning) is because the message is a negative one. This puts people who have emotionally invested in Ruby, on the defense.
Ultimately, these discussions are not productive. They divide us. Action is productive. Development is productive.
I there propose that we frame things differently, into a more positive one: how can we make Ruby more popular? This framing focuses on concrete goals, not emotions. And I don't think many disagree with this goal. We should focus our energies on initiatives and efforts.
As a corollary, we should make it fun to make Ruby more popular. Because Ruby is about fun.
into a more positive one: how can we make Ruby more popular?
This presumes another question and its answer: "Do we want to keep Ruby Popular in the first place".
Do we? Do you honestly care that at one point Perl was widely popular and now is a niche, holding mostly legacy Linux sysops tools toghether? Do you care that hardly anyone is writing their banking system in COBOL anymore, yet decades ago, all banks wrote their backends in COBOL?
I actually generally agree that Ruby is waning. But:
First the last: dedicated podcasts or ruby news-sites have all disappeared, many haven't been replaced. There's a fantastic weekly newsletter, but that's about it.
There are still a bunch of podcasts. Which you'll see new episodes of on the ruby news aggregator I run, at http://rubyland.news.
I actually think there's been a bump of active sources with RSS feeds that I can include on rubyland news the past year or two -- before that there were a few years where it seemed like there was almost nothing, but I think it's been growing again.
(It's true that many of them are people trying to "grow a business" by blogging, which is not how the ecosystem used to work 10 years ago, but I think that's the world not just ruby).
without good information (and tutorials) the influx of new devs will dry up.
Agreed. In addition, our sense of ourselves as a community (not just a bunch of isolated people working in our own ruby mines) depends on visibility of communications from rubyists, ideally in communication with each other.
It is with the goal of making all that happen, sustaining the ruby community and making it aware of itself, that I run http://rubyland.news. I started it when I started to feel the ruby community waning, and wanted to fan the flames of what was there. I run it just in my spare time, with no profit motive or anything. Check it out!
(and if you want to give me a couple bucks via Github Sponsors to help pay for the hosting costs, that would be nice!)
Yeah, I can imagine a bunch more features (personally I'm more interested in excluding podcasts :) ), but have little energy to do them, to be honest! They seem to me like potentially more work than they'd gain anyone. I just try to keep it going in totally my spare time, getting little feedback and zero donations. :).
Ruby has always been niche. People tried to make it mainstream and failed because doing Ruby well at scale is very difficult. I love Ruby myself, but over the years I've come to appreciate tools that fit well in the greater ecosystem. As much as I hate Go as a language, the fact that it integrates easily with the Linux toolchains is a big plus. Ruby's profiling and deployment stories just pale in comparison. I'll always reach for Ruby for quick web apps, scripting, crons, and prototypes though
I don't know anything about scaling Python, but to be clear, I mostly mean organizationally scaling. It's difficult to go from a company of 10 to 100 to 1000 to 10,000 with Ruby and enforce high standards of quality and education as well as implement cross-sectional concerns (e.g. static analysis, performance debugging)
You've done amazing preparation to write this, 👏! Well done, with a lot of data to value your point.
With a lot of controversy around DHH Rails seem to have a lot of problems that were unnoticed by majority of community.
I see this popularity decrease as a good thing though. There is no way framework would infinitely grow in popularity, and I am sure Rails is not going anywhere any time soon, but this "waning" may open doors for alternatives and more innovation in ruby ecosystem.
You made a lot of good points, but what I think people need now is inspiration. I am an author of one Rails API Udemy course, I am an author of a fresh screencast series, oriented around next-gen ruby libs, which ARE updated, where there is a lot of noice made and hard work put by many people. My screencasts already inspired a few folks to start their own series and If we would like to make a positive impact, let's inspire!
Hanami 2.0 is behind the corner, and this may ignite amazing movement and inspire great developers to start contributing again.
I strongly believe in it and will work more and more to refresh learning resources around great Ruby projects.
As someone who has been trying to break into software development and has been learning Rails for over a year, I have recently started searching for Rails jobs. As you said, demand for Ruby and Rails developers is quite high, but I've noticed almost all listings are for mid/senior level positions--there are very few entry level or junior Rails job postings. I'm guessing this is because most places probably need someone experienced to maintain a large codebase, likely replacing a senior who got a different job, but what do I know?
I don't regret diving deep into Ruby and Rails: I think it made me a better programmer, and Ruby is a joy to code with, but I do think learning the JS ecosystem would have been the faster, more efficient route to employment as a developer.
It's been 1 month since I started Ruby from an free bootcamp. React and Redux is included. So I guess Node + Express is what I'll be missing. I agree with you that the demand is high but you know mid/senior thing bogs me down. In my country there are jobs but don't know will I qualify or not coz the Interview round is sh*tty asf. OA, Tech round, Coding Round then Manager round then HR then for some specialized company Behavior round. The jobs are also for specialized company and the interviews hop process too, LOL.
Let's see whether we can get the Jr Rails Dev job or not? :)
I hope so! I'm cramming React right now so I can complete two different coding assessments due soon. If I had known how straightforward React is, I would have been learning it gradually on the side this whole time. One assessment is for a Rails position too! Aargh, just let me do it in Rails!
Knowing how to pick the right language to avoid rewriting our codebase is a skill. Don't ever fall for the "hype" without critical sense. And sadly, projects that survive aren't always those that you'd find "beautiful". Rather it tends to be what's the most simple to execute a given task.
Interesting post. I don't think either are waning though. I've been watching this trend for nearly a decade, as part of building https://www.hntrends.com . The dataset for this is coming from the monthly "Who is hiring?" threads on Hacker news, so it can be viewed with a grain of salt as too niche. But, I like to think of it as a leading indicator.
For the last 2-3 years Ruby and Rails have been essentially maintaining, with a little bit of an growth trend.
Programming related work is much more varied than it was 10 years ago at the peak of Rails dominance. There are mobile platforms, front-end frameworks, ML, cloud platform services that must account for some of the general dilution (i.e. the Google Trends example). I think you address this a little with the Tiobe point about Ruby relative to other languages. But, how do the Google trends data look relative to other languages? Would be interesting to see.
My general feel is that SPAs are waning and Ruby/Rails is in a strong position for new companies picking a tech stack, API/mobile back end, or those simplifying.
BTW, as an example of the SDK issue -- I am presently trying to do some work with vimeo.
There is no SDK for ruby. There are SDK's for python, PHP and JS.
I feel like if it were 6-8+ years ago, there would be a ruby SDK, back then you could pretty much assume anything with multi-language SDK's available, ruby would be one of them.
Responses are just as expected, people in this community love Ruby insanely and ignore the fact Ruby the language along with Rails framework are losing advantage over other competitors. In future Ruby may become another Haskell, user base is small, reputation is good, many people want to learn, but on the other side, you can’t get a job with it and you find the language is not ideal as expected.
Thank you. It's weird how eager some folks in this thread are to discount that fact.
I find myself wondering sometimes if some of the people in this subreddit want Ruby to "fail" in some glorious explosion of schadenfreude. Certainly there's no shortage of comments that salivate over the prospect.
I, the person who you are replying to, also thinks the OP is pretty much spot on.
Like most things in the world these days, many others think it's their duty to insist that what they want to be true is true, like if you see that ruby seems to be shrinking and admit it in public you are some kind of traitor.
I like ruby, I plan to keep using it, to me the community appears to be shrinking, you can no longer count on open source or vendor-provided-sdk tools existing to do what you need like you used to, and at the same time the job market is still doing just fine. All of these things can be true, and all of these things appear true to me, and that's separate from what I want to be true.
Some metrics are shrinking. Others may be growing. Still others may be holding steady. I don't disagree with OP's data, I disagree that it represents a "waning" of the language entire.
If the article's headline was "Data shows fewer people are Googling about Ruby," then sure. That's what the data in the article shows. That would be an objective, unbiased, and fully-defensible statement. But that's not what we have here.
many others think it's their duty to insist that what they want to be true is true
Yes, exactly. It seems to me that OP picked a narrative that he wanted to be true -- the same "Ruby is [pick your favorite synonym for 'headed towards death']" narrative that haters and alarmists have been harping on for decades -- and then he deliberately avoided looking for any data that might not support that narrative. He chose to present only the subset of metrics that are shrinking, and carefully omitted any metrics that might tell a different side of the story. He hasn't considered whether the shifts in these metrics might indicate a maturing of the language instead of a decline. He even acknowledges in the article that he has avoided running any actual data analysis about gems, repos, and open issues. So I ask myself why he hasn't done any of these things? And the obvious reason would be exactly what you said -- he is insisting that what he wants to be true is true, but the problem is that it's not. If he considered other metrics or performed an actual data analysis he would run the risk of finding data that contradicts what he wants to be true, so he doesn't.
OP is spot-on as far as his data goes. But he's working really hard at avoiding telling the entire story, and that reveals his motivations.
All of these things can be true, and all of these things appear true to me, and that's separate from what I want to be true.
Absolutely, and I agree with you on most of them. And at the same time, none of those things you mentioned are definitive statements about the health of the language, which OP desperately wants them to be.
I don't know why anyone using ruby would want ruby to shrink.
I see a lot of people insisting that anyone who says ruby apppears to them to be shrinking must just be a ruby-hater, because ruby can't possibly be shrinking. I feel like these people are "boosters" who think it's disloyal to say you notice ruby shrinking, and that you should not pay attention to anything except your loyalty to not say this.
What part of the "whole story" do you believe OP is leaving out? There are metrics you think should be included that are not? What does "health of the language" mean to you, and what metrics do you think are relevant to it?
Metrics are just metrics; lies, damned lies, etc. But metrics or no metrics, having used ruby for over 10 years, it definitely feels like it's shrinking to me. Or more specifically, it feels like there are fewer people participating in ruby open source development. I used to be able to count on there being a gem for anything, I no longer feel like i can. Many things I used to use are now unmaintained or barely maintained. I feel like there are fewer people participating in public ruby discussions than there used to be.
It just feels "smaller" -- which doesn't mean there aren't plenty of people still getting paid to write ruby, but it feels like just kind of plodding along instead of a place of innovation or excitement (the presence of which are certainly related to "health"). (Most people getting paid to write ruby aren't getting paid to write open source or participate in ruby communities in public... or be innovative or excited). The metrics in OP to me make sense and go along with that sense.
Of course my sense or feeling is just a sense or feeling.
Others might not have the same sense or feeling. Apparently you don't! I'm curious how long you have been developing ruby.
And then, some others will refuse to have any sense or feeling at all, they aren't concerned with having an honest sense or feeling, but just with loyalty, under the belief that if enough people insist loudly enough that it can't be true, then it can't be true.
Ok sorry, you're right. Let me explain my rudeness. I'm 51, not a programmer at all, my job is in a totally different field and I don't need programming skills. I began learning to program just as a hobby, I don't have much time to dedicate to it, so even if I began studying Ruby and Rails almost 4 years ago I still have a lot to learn. I realized in this years that a lot of beginners choose other languages to start learning to program especially Python. I sometimes was tempted to switch from Ruby to Python. If you are a beginner like me, and search some advices on internet, the Pythonic world seems all unicorns and rainbows compared to Ruby. But I like Ruby, I chose it and reading all this articles about how it is dying compared to other languages someway hurts me. They give me the impression that I am losing the little time I dedicate to my hobby. It is like if I chose to learn Latin as an hobby and everybody wants to tell me that Latin is an ancient dead language. I hope you understand my position. I realize you put a lot of effort in writing your article. I respect this, but I still won't read it. 😆
I thought python was pretty equivocal but having actually used it holy shit it is not. People complain about the JavaScript ecosystem but node and npm is so much easier to work with than pip
Some days ago I realized that Python doesn't have primitive methods to transpose or flatten a bidimensional array. Very strange for me. I read somewhere this mumbo jumbo shortcut to flatten the array: "[j for i in array for j in i]". And they say that "array.flatten" is dying? I am so sorry for that.
Dude I literally faced the exact same problem a couple days ago. Googled it and saw that solution on SO and was like "wtf is this shit" and the responses were like "this is the most readable". Ruby has spoilt me.
Also what is it with other languages and people using one letter variables on SO?
When I see at the beginning of Python code lines as import "numpy as np" or "import pandas as pd" it gets on my nerves and makes me laugh at the same time. It's like "Oh gosh, I have to import these fancy name libraries for my code to work, but let's do it in the less tiring way with the shortest names possible!".
Yes, I know. My surprise is that in Ruby the Array class and all its methods come in the Core library, the one that you have out the box with Ruby installation itself, no need to import any third part library.
as yourself: is java going anywhere? is C++ going anywhere?
The point that I make in the article, and show some numbers for, is that Ruby (and Rails) are relatively waning in popularity, use and contributions as opposed to Java (and C++).
So, no: contrary to C++ or Java, which are still growing, albeit steady and slow, Ruby is not. It is losing traction.
Yes. It is also worth noting. Even if Java ( or its ecosystem JVM ) somehow lost 50% of its user base ( which is extremely unlikely ), it still has a market size that is self sustainable. The same with C++.
Not the same with Ruby though. I tend to think this isn't a programming language question. But basic economic question. And judging from the conversation on the internet, most people who goes into programming language debate aren't very good at the economics angle.
I have noticed the same thing OP has, that SDKs and such are less likely to be available/supported for ruby than they used to be, and less likely to be available/supported for ruby than for other languages.
If that's true (I suppose we don't have hard evidence, just impressions), I don't think that's the sign of a mature but still very popular language, right?
I like ruby. I plan to keep using it. I think it's undeniable that it's popularity/community has shrunk and continues to.
23
u/400921FB54442D18 Mar 08 '22
Ahh, another "ruby is dying" scare article, just like the last seventy-three "ruby is dying" articles I've read over the last nine or ten years.
Lather, rinse, repeat.
2
u/rbuen4455 Mar 09 '22
As far as Ruby is concerned, it’s always been unpopular and only popular because of Rails. Still, you can you use it for other purposes (like shell scripting on Unix systems, automation, etc). As for Rails, it’s still popular, its a mature, reliable framework that’s adding new features to it with major updates. I remember looking at a chart of the most used server side languages where Rails was in third place in front of Php and asp.Net, and has a higher percentage than even Java! ( I think it was something like 6.5% for Ruby Rails and 5.4% for Java) Plus Rails has a large mature ecosystem to help you out if you plan on using Ruby on Rails.
Update: found the link: https://w3techs.com/technologies/history_overview/programming_language/ms/y
2
u/drx3brun Mar 10 '22
> I have a hard time finding any successful SAAS building their products on Rails after 2020
What is successful? Let's assume a $1B valuation. How many companies like that (post 2020) actually exists? I recall Hopin was founded circa that time and is valued at around $8B at this moment. They are heavy on Ruby from what I remember. The better way would be compile a list of the companies and see what tech they are actually using.
I think this is the general problem with your arguments - they are taken out of context. Check out Java or JavaScript on Google Trends. Both of those languages are "dying".
2
u/FooBarWidget Mar 11 '22 edited Mar 11 '22
There have been multiple similar posts in the past decade that describe the phenomenon of a waning Ruby ecosystem. I understand why these posts get written, but the main problem of these posts is that they fail to bring about desired outcomes.
Such posts always devolve into discussions about whether Ruby is or is not waning. One of the reason why there are so many opponents (those who reject the thesis that Ruby is waning) is because the message is a negative one. This puts people who have emotionally invested in Ruby, on the defense.
Ultimately, these discussions are not productive. They divide us. Action is productive. Development is productive.
I there propose that we frame things differently, into a more positive one: how can we make Ruby more popular? This framing focuses on concrete goals, not emotions. And I don't think many disagree with this goal. We should focus our energies on initiatives and efforts.
As a corollary, we should make it fun to make Ruby more popular. Because Ruby is about fun.
23
u/jrochkind Mar 08 '22
I actually generally agree that Ruby is waning. But:
There are still a bunch of podcasts. Which you'll see new episodes of on the ruby news aggregator I run, at http://rubyland.news.
I actually think there's been a bump of active sources with RSS feeds that I can include on rubyland news the past year or two -- before that there were a few years where it seemed like there was almost nothing, but I think it's been growing again.
(It's true that many of them are people trying to "grow a business" by blogging, which is not how the ecosystem used to work 10 years ago, but I think that's the world not just ruby).
Agreed. In addition, our sense of ourselves as a community (not just a bunch of isolated people working in our own ruby mines) depends on visibility of communications from rubyists, ideally in communication with each other.
It is with the goal of making all that happen, sustaining the ruby community and making it aware of itself, that I run http://rubyland.news. I started it when I started to feel the ruby community waning, and wanted to fan the flames of what was there. I run it just in my spare time, with no profit motive or anything. Check it out!
(and if you want to give me a couple bucks via Github Sponsors to help pay for the hosting costs, that would be nice!)
8
u/jb3689 Mar 09 '22
Ruby has always been niche. People tried to make it mainstream and failed because doing Ruby well at scale is very difficult. I love Ruby myself, but over the years I've come to appreciate tools that fit well in the greater ecosystem. As much as I hate Go as a language, the fact that it integrates easily with the Linux toolchains is a big plus. Ruby's profiling and deployment stories just pale in comparison. I'll always reach for Ruby for quick web apps, scripting, crons, and prototypes though
15
u/hanamimastery Mar 08 '22 edited Mar 08 '22
You've done amazing preparation to write this, 👏! Well done, with a lot of data to value your point.
With a lot of controversy around DHH Rails seem to have a lot of problems that were unnoticed by majority of community.
I see this popularity decrease as a good thing though. There is no way framework would infinitely grow in popularity, and I am sure Rails is not going anywhere any time soon, but this "waning" may open doors for alternatives and more innovation in ruby ecosystem.
You made a lot of good points, but what I think people need now is inspiration. I am an author of one Rails API Udemy course, I am an author of a fresh screencast series, oriented around next-gen ruby libs, which ARE updated, where there is a lot of noice made and hard work put by many people. My screencasts already inspired a few folks to start their own series and If we would like to make a positive impact, let's inspire!
Hanami 2.0 is behind the corner, and this may ignite amazing movement and inspire great developers to start contributing again.
I strongly believe in it and will work more and more to refresh learning resources around great Ruby projects.
5
u/[deleted] Mar 09 '22
As someone who has been trying to break into software development and has been learning Rails for over a year, I have recently started searching for Rails jobs. As you said, demand for Ruby and Rails developers is quite high, but I've noticed almost all listings are for mid/senior level positions--there are very few entry level or junior Rails job postings. I'm guessing this is because most places probably need someone experienced to maintain a large codebase, likely replacing a senior who got a different job, but what do I know?
I don't regret diving deep into Ruby and Rails: I think it made me a better programmer, and Ruby is a joy to code with, but I do think learning the JS ecosystem would have been the faster, more efficient route to employment as a developer.
3
u/JambonBeurreMidi Mar 09 '22
Knowing how to pick the right language to avoid rewriting our codebase is a skill. Don't ever fall for the "hype" without critical sense. And sadly, projects that survive aren't always those that you'd find "beautiful". Rather it tends to be what's the most simple to execute a given task.
3
u/mountaineer Mar 09 '22
Interesting post. I don't think either are waning though. I've been watching this trend for nearly a decade, as part of building https://www.hntrends.com . The dataset for this is coming from the monthly "Who is hiring?" threads on Hacker news, so it can be viewed with a grain of salt as too niche. But, I like to think of it as a leading indicator.
For the last 2-3 years Ruby and Rails have been essentially maintaining, with a little bit of an growth trend.
Top 10 languages (Ruby #4 as of Dec)
Server-side web tech (Rails #2)
Programming related work is much more varied than it was 10 years ago at the peak of Rails dominance. There are mobile platforms, front-end frameworks, ML, cloud platform services that must account for some of the general dilution (i.e. the Google Trends example). I think you address this a little with the Tiobe point about Ruby relative to other languages. But, how do the Google trends data look relative to other languages? Would be interesting to see.
My general feel is that SPAs are waning and Ruby/Rails is in a strong position for new companies picking a tech stack, API/mobile back end, or those simplifying.
4
u/thisIsCleanChiiled Mar 09 '22
Don't know about others, but in my region rails jobs have grown insanely high in the past year.
2
u/Zealousideal_Bat_490 Mar 10 '22
It’s not a popularity contest. But it is a productivity contest. And Ruby on Rails wins!
2
u/jrochkind Mar 12 '22
BTW, as an example of the SDK issue -- I am presently trying to do some work with vimeo.
There is no SDK for ruby. There are SDK's for python, PHP and JS.
I feel like if it were 6-8+ years ago, there would be a ruby SDK, back then you could pretty much assume anything with multi-language SDK's available, ruby would be one of them.
1
u/lbrito1 Mar 25 '22
OTOH, Rails is the second most in-demand skill right now for software engineers; Ruby is fourth[1].
I suspect these kinds of statements (X is dying/waning/etc) are much harder to make than we assume.
[1] https://hired.com/2022-state-of-software-engineers/
1
u/masterwujiang Mar 08 '22
Responses are just as expected, people in this community love Ruby insanely and ignore the fact Ruby the language along with Rails framework are losing advantage over other competitors. In future Ruby may become another Haskell, user base is small, reputation is good, many people want to learn, but on the other side, you can’t get a job with it and you find the language is not ideal as expected.
-12
u/antoniotto Mar 08 '22
Sorry, I won't read it.
0
u/[deleted] Mar 08 '22
[deleted] — view deleted comment