this post was submitted on 12 Jul 2023
57 points (98.3% liked)
Asklemmy
43898 readers
1202 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I thought Ruby was still pretty relevant given that Mastodon is essentially coded in Ruby but I am coming to the same conclusion you are based on another person's comment.
Ruby is used in some large, older existing projects (e.g. GitLab, Redmine, Puppet) but my impression is that a lot of them do not have very much active development of the Ruby parts going on any more.
I am seriously curious here: Why has popularity of Ruby declined?
Probably a few reasons for this. I’m not a ruby dev so take this with a grain of salt.
Ruby doesn’t have a lot to offer beyond languages like Python or Go without its companion web development framework Rails. Ruby on Rails was good for its time (~2012 -> 2015 era was peak), but there are more mature, stable, and widely adopted frameworks available in other languages. RoR touted speed to develop as a feature, but you can do things plenty fast with the aforementioned languages too. On the flip side, rails apps are notoriously slow to boot. I think this became a problem with cloud native infrastructure. For example, Kubernetes likes to spin up services very quickly, and can be painful to work with if that’s not an option (experienced this with Java apps too for that matter). As self hosting on bare metal went by the wayside, so too did interest in developing new apps on rails, imho.
Interesting! Thank you for the perspective. I am seeing a trend of smaller businesses that are bringing services back on premises and self-hosting but I have no interest in working for a small business. I've been there, done that, and it was hell.
Yeah, which makes Ruby one of those languages like COBOL, you can make a lot of money if you're in that world, but I wouldn't ever recommend that someone should try and join that world, it's going to be too hard to get in to and it might not stick around for long. I know some people that make a lot of money working in Ruby, but that doesn't mean that anyone can, unlike javascript which will be valuable anywhere