[cageface]

I've been working on Ruby apps again lately after spending a few years in the iOS world. I don't miss iOS at all but moving back to a slow, dynamically typed language like Ruby after getting used to Swift is like trading in a Tesla for a Model T. Ruby was great it its day but I think we can do better now. Maintaining large Ruby codebases is no fun.

[ultrarunner]

No fun for you, maybe. And I can see where you’re coming from. I often find it very fun, though, which has prevented me from porting an API to another language like Go or (gasp) Swift. Ruby gives a lot of flexibility, and in my line of work (especially with covid mitigations) there are lots of immediate change requirements; flexibility is very important. That flexibility provides the ability to shoot yourself in the foot (and I’ve surely done it), but it also allows us to pull off events that have suddenly changed with little warning. I like that.

[theonething]

> pull off events that have suddenly changed with little warning.

Excuse my ignorance. What are the events you reference here?

[ultrarunner]

I work for an event company, and in many cases much of it is orchestrated by Ruby code, including a few rails apps.

[theonething]

aha. I wasn't sure if you were taking about events on the software side.

[ultrarunner]

Imagine the naming conventions on the software side :)

[joelbluminator]

Not really sure what's Ruby's "slowness" has to do with anything? Were you having performance problems with Ruby or did you just throw in it being "slow" to prove a point? I worked on quite a few Rails apps for 6+ years and Ruby's speed was never an issue.