Cries in Delphi.
RoR is too much magic for me. Getting started with any new code base is such a pain that I never want to do again. As a manager, I’ll avoid any job post that mentions Ruby. I have maintained projects written in Delphi, Centura, Java, C#, PHP and none of them even come close to the pain of RoR. Java and C# are notorious for ceremonial interfaces but that’s nothing compared to trying to figure out RoR automagics.
There is a lot of magic in Java. Try Spring Boot for example, and things magically connect together with annotations, or somehow methods get injected onto interface on the fly, or an http interface maps onto a function with parameters because the runtime is doing it. This is most evident when you set a break point in some class and there might be 4 or 5 mystery functions it passed through between it and where you thought it was calling from. Sl4j, Lombok, Hibernate are doing the same kind of thing.
Maybe in enterprises settings what you say makes sense, but for the small to medium startups I usually work for, RoR is great. It’s super easy to prototype and switch lanes. If I had to do what I do in Java I’d go insane. As for Delphi…
The RoR “magic” being obtuse is extremely exaggerated most of the time and more meme than reality. If you think PHP is better, by which I guess you mean Laravel, how on earth is that less “magical”? React? Next? I’ll take Ruby any day.
React can go fuck itself with a pineapple, fuck that piece of shit. Every project I’ve had to deal with that used React was an absurdly bloated mess because it imported fuckloads of React plugins and addons.
Oh. I didn’t know react had its own supply-chain sploit risk. T-I-L
Goddammit, I’m feeling for an anthropomorphic programming language that I don’t even know.
Mastodon is written in Ruby. Nowhere near as big as Facebook or the ML field, but hey, it’s important to a couple of us at least :)
Hi there! Your text contains links to other Lemmy communities, here are correct links for Lemmy users: [email protected]
Mastodon is written in Ruby. Nowhere near as big as Facebook or the ML field yet
FTFY ;)
and therefore scales terribly ;;
It probably wasn’t a big deal when it was a niche project until Twitter imploded. Then all the public instances got overloaded with new users and the limits became obvious.
A better design is Lemmy which is written in Rust so it has far more scalability. It’s compiled and because it’s tokio / actix based, it can also do a lot more stuff asynchronously so it’s not spawning thousands of threads to cope with concurrent requests.
@pkill Yeah seems that way, judging by their scaling up documentation: https://docs.joinmastodon.org/admin/scaling/
Although hey, it all depends on a whole bunch of stuff written in super optimised (and kinda scary) C !
Those docs look pretty easy to scale mastodon. What am i missing?
@towerful I mainly program in Go, so when I see all that extra software I notice how much easier it is when I get to just rely on the Go runtime. It does a lot of the heavy lifting done here, but the resulting code is not as clean. Actually just today I read through Mastodon’s code to track down a bug in my in-progress ActivityPub service (in Go) and found the Ruby really easy to navigate!
Ruby -> Rails.
It just hasn’t had a second revival.
But Cinc and its sell-out dad Chef are really great uses of ruby, keeping us from YAML hell and the kludgey socket-machine-gun that is Ansible. That piece of shit has more lithium-lick than I’ve ever seen.
If we can’t have mgmtConfig (ohai go), at least let us keep Cinc, but it needs ruby.
I really wish I knew what all these words meant. Then again that might ruin the childlike delight I get from my ignorance.
deleted by creator
Emacs enters the chat.
Emacs unfortunately uses Emacs lisp, not common lisp or scheme.
There was that one attempt to rewrite Emacs in cl
And that didn’t work? I would have thought it would be quite popular.
I think that Emacs itself was mostly implemented, but they couldn’t get people to rewrite all of their user generated content.
Oh, right. That makes sense.
What are the main differences?
Emacs is a bunch older than common lisp.
One of its more idiosyncratic design decisions was using dynamic scope, rather than lexical scope. They did add in per-file lexical scope, though.
It also just doesn’t implement a lot of common lisp’s standard library.
Not anymore
QUANTUM COMPUTING
Enterprise will keep the withered husk of Java EE crawling for eternity
Medicine too.
An instrument in my lab is running jdk 1_8_131…and this is a recent/newish piece of equipment.
I don’t use Ruby anymore, but I still use
irbeveryday as a command line calculator.I miss Chef
Those hentai games and visual novel games still keeping ruby lang relevant tho, rpgmaker game engine is one of examples
It’s easier to code in python one handed then it is codeing in C
I think the two newest, MV and MZ, have switched to Javascript. Also, Ren’py is the only visual novel engine I can think of, which is based on Python.
Hey Ruby debs, lookup Elixir. It’s supposedly similar syntax but run on the Erlang VM instead. Lots of cool companies use it, and a great community. 🤗
Don’t learn Elixir to replace Ruby. Learn it to enjoy OTP and BEAM.
I would love to join a cool company that’s willing to accept a dev that can transition fast. However, most of Elixir job listings I find are gambling or crypto. And I ain’t gonna touch those.
I’ve written a non-trivial amount of Elixir. It’s nice, but I wouldn’t say it’s like Ruby. It’s more heavily functional, and it wants you to work with data in an immutable way. If you’re coming from a language that doesn’t force immutability, then you’ll be miserable until you get your head around how to work that way.
I really like it, though. Especially now that it’s getting optional typing.
Elixir is an awesome language. It takes some getting used to as it’s meant to be more functional like Haskell, but it plays really nicely with big parallel workloads and is super clean to write
Crystal lang is also pretty cool looking. It seems to be going for what Nim is doing, making Ruby as fast as C.
I really like ruby :(
Even in 2024, I say that Ruby is one of the best common languages available. While there are some weird syntax choices, and a lot of rope to hang yourself with when it comes to subjects like metaprogramming, it is a better Python than Python, in that it has a clean way to approach problems, and a simple structure to make coding clean and easy. The best part of Ruby is that its tooling is great at pushing best practices, like concise methods, good naming conventions, tests with single/aligned assertions, etc. I’ve taken many lessons from Ruby into other languages I use.
Rails, on the other hand, is totally different. Today, Zed Shaw’s essay on Rails is as accurate as ever, in that many Rails shops have just ignored years of best practices on the web, and opt to do things their way because it’s “better”.
Shopify is built on Ruby on Rails
That explains a lot
Yeah but Shopify also runs on GraphQL and Remix which are way more modern.
This is like saying Twitter is RoRedit: no it’s not
I worked at Shopify up until a year ago. github.com/shopify/shopify repo powers almost every inch of Shopify’s infrastructure and is entirely a rails monolith. It is not the same as saying Twitter is still rails.
Thanks for the insight! I’ve seen so many gql queries in the UI and remix is blowing up so I figured it was at least similar.
Edit: Shopify engineering publishes some neat articles, particularly on scaling rails + other systems. E.g https://shopify.engineering/horizontally-scaling-the-rails-backend-of-shop-app-with-vitess
So is square IIRC
I wrote extensively in Ruby but for Rake - using Ruby as a build system. Can’t say I liked the language although it was okay for how we used it. We have 20 sub projects with some very complex build targets and dependency scanning going on and the Rake syntax was okay. Personally I think its biggest shortcoming was the documentation was very poor and stuff like gems felt primitive compared to other package management systems.
I think if I were doing an acyclic dependency build system these days I’d use Gradle probably.
As for Rails I expect failed to catch on because even compared to Python, Ruby is a slow language. And Python isn’t fast by any stretch. Projects that started with Rails hit the performance brick wall and moved to something else.
Why Gradle?
We had tens of thousands of lines in our rake files to build a bunch of targets, none of which were even Ruby. I think if I needed to build another complex build system that was a directed acyclic graph I think I’d use Gradle, for a several reasons - we had some Java targets so we save on an additional developer runtime, it would run faster & Gradle is more mainstream and easy to get various plugins & documentation for.
