The deeper reason I think it's a bad argument is because twitter ran into a problem native and new to them - massive fan out (celebrity tweet -> millions of followers). that's not the kind of thing any language typically does while responding to a web request.

Lastly - heavy survivorship bias here. We will never hear about all the startups which were "scalable from day 1" on java or whatever and fizzled out.

Looking at https://www.wired.com/author/sheon-han/, this author's whole strategy seems to be bear poking. The writer is skilled but at least in this ruby one they are definitely hate-farming. I'm a little sad to see content of this quality in Wired.

Anyway, I'm off. Returning to be part of the usually silent majority who is happily using ruby to ship useful software!

I think that should've been the main point to attack.

In the present article, the author went for pathos instead and in some ironic sense confirmed the previous article's notion that Ruby is powered by sentimentality.

Many people that adore Elixir also think Ruby is a no go, despite the latter being a strong influence. Arguments against Elixir tend to revolve around its lack of traction, not its lack of seriousness.

It is not "I like to write code in this language" but "If I am handed down a production ready system, I would prefer it to be written in this language".

A lot of people won't say the same answer to the first and the second question.

I do feel like these sorts of attacks on ruby are quite weird. It's totally ok not to enjoy working in any particular programming language, but I wonder what the angle is to write about it is.

Arguments regarding ruby's successes are always so weird to me. Github, Twitter, Coinbase, and Shopify are all examples of great success. Challenges with scaling are successful problems.

It's a great tool and if you read this, consider and evaluate if ruby is appropriate for your next project. :)

That said - this response and the critique seem to basically agree. The critique can be summed up as "Ruby doesn't work forever" (and so it should never be used) and this is saying "Ruby doesn't work forever" (which is fine). I could almost understand this post as saying: 'Ruby isn't serious and that's not a problem for anyone who uses it.'

I will say that I found it funny that the original article attacked Ruby for being all the way down at "18th place" (This is inaccurate - it's 14th in 2024) on the SO dev survey - while talking up Scala which is 9 places further down on the survey[1].

[1] https://survey.stackoverflow.co/2024/technology#most-popular...

At least a few emerged later. Pattern-matching + guards are godlike and eliminate tons of boilerplate argument-checking logic. Per-process GC, no GIL, etc. etc.

A small learning curve to master functional-language semantics and I haven't looked back.

Elixir simply scales better in every way- long-term maintenance, load, etc.

The Ruby community is/was amazing, though.

The only thing I wish it could do was compile down to a native executable or run in the browser.

But even if it had been written in good faith, this species of article (specifically: harsh critiques of popular programming languages written by people who aren't ongoing practitioners in that language) are a toxin to HN, the resulting language fights they gin up one of our closest equivalents to a cytokine storm. Don't feed into them.

I don’t care about what’s popular or what feels most familiar. What I want is a dispassionate discussion of how different language features impact code quality, and I think you can only find that in more abstract discussions. The kind that turns people off with its talk of monads and applicatives.

But yeah, that was 20 years ago. These days I find Kotlin to be the perfect fit for my projects, because of the static typing and its ergonomic syntax. I just don't feel confident about Ruby projects when they start growing. But, I still love the language, although mostly for small things.

From the cited article [1]:

"Casual website designers can safely completely ignore the concepts of types and memory deallocation because Ruby is dynamically-typed and garbage-collected. These features are simply not available in all other languages. Java's meta-programming features, for example, are just not powerful enough to implement a system like ActiveRecords. Rails is only possible because of Ruby."

But I'd argue that you can still have types and still have a very powerful meta-programming features and abilities of compiled language for example D to implement a system like ActiveRecords [2].

[1] Stop Designing Languages. Write Libraries Instead:

https://lbstanza.org/purpose_of_programming_languages.html

[2] D Language: Features Overview:

https://dlang.org/comparison.html

> Critically, Ruby’s performance profile consistently ranks near the bottom (read: slowest) among major languages.

Without a cite, perhaps because it's not really true. Ruby's performance is similar to python's. Granted, neither one is going to win any competitions, although I'm not sure what the field of "major languages" is.

These days I mostly use more "serious" languages (python, Java, C#, C++), but it's because I want to work on a domain within those languages and I don't have the time to commit to bringing the domain to Ruby. I should call her...

I am entirely indifferent to the topic of Ruby, but this sentence really resonated with me. I'll take momentum over premature optimization for scale any day of the week.

> Arguing about definitions is a garden path; people wouldn’t go down the path if they saw at the outset where it led.

See [1] for some tips on moving past the fruitless arguments:

> Personally I’d say that if the issue arises, both sides should switch to describing the event in unambiguous lower-level constituents ...

> ... Or each side could designate a new word, like ‘alberzle’ and ‘bargulum,’

> ... and then both sides could use the new words consistently. That way neither side has to back down or lose face, but they can still communicate.

> And of course you should try to keep track, at all times, of some testable proposition that the argument is actually about.

> Does that sound right to you?

[1]: https://www.readthesequences.com/Disputing-Definitions

Manual memory versus GC, JIT, AOT, interpreted, begin/end or curly brackets, unsafe or not, whatever.

We will be slowly moving into some kind specifications for autonomous systems (please not YAML based), up to a point, and language wars will become a moot point, only relevant to the selected few implementing the low level parts of how everything comes together.

My only complaints about Ruby, as someone that never really did much with it, would be a more Smalltalk like dev experience (not sure how RubyMine fares), given its influences, and a proper JIT in the box (which is happening).

Right now Ruby is a language used to maintain legacy Rails systems.

Culture maybe, but business rewards what make business going on. Only that and Ruby proved that it can make businesses start and keep them going on. The few ones that exceed the capabilities of the runtime had to pivot to something else, in part or completely, but would we had a Twitter if they started coding in pick-your-favorite-serious-language? Maybe a competitor would have overrun them. We'll never know.

What I know for sure is that Ruby has been paying my bills for nearly 20 years. That's more than any other language I used, serious or not serious. It worked for me.

I like its rich standard library style and encapsulation style (e.g. .map with lambda).

I've moved to Scala purely because Ruby is not typed. In a large codebase, it becomes really difficult to refactor. Even renaming stuff is convoluted.

Except for static typing and ruby's particular style of metaprogramming (one could argue python enables decorator-based "meta" programming, but whatever), ruby and python are basically the same language, with some obvious semantic differences. Of course there is much about ruby and python that is very different -- adoption, library support, community, vibe, whatever. And you could say that python is at it's core functional with OOP layered on top, while ruby is the opposite, it's all sort of irrelevant, they are basically the same, in the fundamental daily experience of using the two languages, in that ruby/python and go (or java, or elixir, whatever) are very much NOT the same. Minus static typing support.

I'm optimistic ruby will figure this out soon, because the sort of static typing support that has propelled javascript and python is the kind that ruby can and should support. By that I mean neither really have static types. Typescript is another language that compiles to javascript, and python's typing support remains and probably always will be optional, and like javascript, is enabled by external tools (mypy, pyright, etc). Neither python nor javascript have a type-centric/aware runtime, or even one in which types are considered at all. They are still both very much dynamic languages that basically have nice developer tooling to help developers write "type-safe" code, but really, in production, we're just pretending that the types we work with in development exist at all in the runtime.

This is not so much a critique of the approach, but the mass pretending we do when we critique a language like ruby for "not having types" and praising javascript or python for "having types" which they clearly do not. But the approach is good, at least if you agree that optional typing is better than java/go style static typing.

I don't know what's holding ruby back from better supporting optional typing, but i hope they fix it soon. My sense is, to over-simplify, sorbet got too popular, but it's fundamentally an approach you would take if you had to build a type system around the language rather than in the language.

For all its problems, the presence of AI feels like it should solve some of these quibbles for the vast majority of people who program. I can't quite put my finger on why just yet, though.

Good structure. Always put the strawman up front.

Stay tuned for my article about soda pop which starts: "I missed the memo that said that just because something tastes great it's 'unhealthy.'"

Ruby is incredibly versatile: NASA has used it for simulation, it's a popular choice for scripting, DevOps automation, and static site generation. It's a simple, dynamic language ideal for quickly prototyping solutions.

Elixir, however, is a separate conversation. Having used it in production for years, I can attest that the ecosystem is fantastic. Its lack of mainstream popularity doesn't matter; its true strength lies in the BEAM, an incredibly well-architected piece of software. Elixir is simply a great way to access that power. Beyond its Ruby-like syntax, it has become its own distinct entity. It used to exist mainly as a alternative to erlang but it's become its own thing in recent years.

I really hate language-based dogma, every virtually every programming language has place as a tool in in a programmer's tool belt. There is even value in learning and using deprecated languages because doing so gives you a perspective beyond whatever ecosystem that you're currently tied to. There is a reason that languages like fortran and lisp have persisted as meaningful choices in certain domains and I suspect that Ruby will stick around for a very long time.

Enshitification is a very rewarding strategy, depending on which side of it you're on, and I think you'd struggle to argue that's, 'The resonant. The clear. The human. The work that connects.'

The fact of that matter is that business and culture reward a vast range of different approaches in different contexts, and this holds over multiple levels of abstraction. From the sort of staff you want in particular jobs, all the way through to your position as a company relative to the market. Do you want your payroll admin to be playful? Really getting down, feeling that vibe - pay them whatever man - it's all in the vibe dude? Or do you want them to do their job to a standard? Do you want your impression as a company producing finance software to be that you're all about the resonant, the clear, the human, the work that connects? Or do you want it to be that you help the organisation meet its audit burden?

And just as business rewards different things in different contexts - so does programming. I'm not going to do low level systems programming in Ruby. I'm not going to go and do graphics programming in Rust. I'm not going to engage in banging out a CRUD app in C. You choose the best tool for the job given what's reasonably accessible to you at the time the problem occurs. Sometimes it's because a particular language gives you good access and support to a set of libraries - sometimes it's because the code you're working with was already written in that language. Sometimes the features of the language are well suited to particular tasks.

It's not a matter of the tool being serious or not. People are serious or not. Languages are just things and what makes the language serious when you pick it up is whether you're approaching your work seriously or not.

however the success of rails was also its biggest albatross. Ruby though fine for system tasks (such as system automation etc, chef existed yeah - but we haven't seen new gen tools built after) - people forgot it could do those.

the other is failure of certain sjws to separate say dhh the programmer vs the person. & not being aware to how money (velocity & gravity) move the world e.g shopify involvement in the ruby ecosystem.

failure to understand that beginners are the lifeblood of an ecosystem - till this date don't know if ruby can be effectively used on windows. most people have windows machines not mac's or linux boxes.

it didn't fail cz it was too slow (its fast enough)

Ruby is indeed a cotton pickin good time. I use C# every day and find it the balance between a fun and serious language. But I've always preferred Ruby over Python and all the others outside of my C# bubble. I do love working in C#, to be clear. It's a shame Ruby hasn't been on the rise.

If this isn't AI slop it's certainly badly written.

That aside, while I'm "old" enough to remember this kind of cultural/vibe-based rivalry between programming language communities, and read enough to know it predates the greyest of living greybeards (TIMTOWTDI vs the Zen of Python, "Real Programmers Don't Write Pascal", "BASIC considered harmful"), I am not sure that this works any more as an argument.

It's a bit tone-deaf to suggest that the difference between Ruby and other communities is that Rubyists are the (only?) ones who care about "how code feels"; that's a pretty core part of the sales pitch for every PL I've ever seen promoted. I am actually nervously awaiting the first big PL that advertises on the basis of "you may not like it, but LLMs love it".

I suspect the real problem is that data science + ML/AI drove (roughly) a bajillion people to Python and LLM training corpus makeup will keep them there. Meanwhile all the Rubyists (ok, I'm being a little inflammatory) that cared about performance or correctness went to Rust (or had already left for Erlang or Haskell or Elm or... whatever). Who's left over there in the dynamic-types-or-bust Ruby world? DHH? (Not an uncontroversial figure these days.)

These were Django, and Ruby on Rails. I already knew Python, and Django was really well-written, and had great documentation, and I could get going with it really quickly. If the docs didn't explain it, I could read the source code. Super.

The place worked at hired a guy who was big into Ruby on Rails, and I really wanted to like it. I liked the stuff the guy was doing, he seemed like a decent sort, and all, and I'm not egotistical enough to go "No we will use my thing" if someone has a perfectly good alternative. Well, okay, I am that egotistical, but not in this case. The point is, I didn't really care which framework we used although I was already able to write Python, because anything was better than the hideous ball of unstructured PHP4 intermingled with HTML that the company's sites were written in at the time.

I really really wanted to like Ruby on Rails, but the documentation kind of assumed you already knew a lot about Ruby and indeed Rails. Okay, let's learn some Ruby.

The IRC channel pointed me at some video tutorials you had to pay for because "that's the future, everyone watches videos to learn stuff now", and why's (Poignant) Guide to Ruby.

I did not like w(P)GtR, at all. I didn't like the "I'm so wackywackywacky" humour on every page. I didn't particularly care about the dog story, which put me off the rest of the whole chapter. I've tried reading it again, maybe about five times since, and I just do not get on with that American Gibberish Poem style of writing.

(I don't much like Alan Ginsberg either, FWIW).

Then the whole Basecamp thing blew up, and DHH was widely known as a total shithead from the motor racing scene so it's not surprising that he turned out to basically be the sort of person my grandfather would have shot if he'd been around in the 1940s.

So, that's kind of why I've never got on with Ruby, much as I'd like to.

The idea that caring about how your programs feel to write or read is somehow “different” seems weird to me. I don’t write Ruby so maybe I just don’t appreciate this difference.

But I mean, I write fun-to-write, silly little experiments in Octave, Fortran, and Python… I don’t know if anyone would enjoy reading them, but I don’t really see how a language could prevent you from finding joy in programming (other than Java of course /s).

Ruby was not designed to be a serious language. It was designed to be fun like PHP but not ugly like PHP. Meanwhile PHP grew up and Ruby grew out.

It's okay to love a thing and realize that it has some unsolvable issues and some people around it destined to keep it that way. Most things are like that these days.

It’s this ridiculous conceit and arrogance that in some way (never quantified mind you), that makes people want to bring the Ruby conceit back to earth.

That’s why Ruby gets attacked - because it’s nothing special but the Ruby lovers club all claim it is.