Why do you think that follows?

I was on team dynamic typing for about 12 years, and Ruby was a big part of that. I still think dynamic languages can be wonderful to read and write.

But after using modern statically typed languages with good inference, I changed my mind. Many of my old objections were really objections to verbose type systems, not static typing itself. With inference, you can keep a lot of the readability while gaining safer refactoring, better tooling, and earlier feedback.

That doesn’t mean dynamic languages can’t produce high-quality software. They obviously can. But I don’t think appreciating modern static typing is just evangelism.

And yes, I understand what this library is about, it's for "beautiful" easy to use interface to AI providers for Ruby apps. It's the popular play nowadays with litellm, bifrost, gomodel and vercel gateway. We have at least couple AI gateways, libraries like that every week on HN.

Because it is simply incorrect. I have been using ruby since 2005 or so. Static types were never relevant or needed in the slightest here. The various claims by the type afficionados camps could easily be disproven and rejected, but that never stopped them from trying to ruin other languages.

> But I don’t think appreciating modern static typing is just evangelism.

But it is evangelism, because the type-addicted devs want to slap on types on ruby. That is evangelism. They try to change an existing language to their world view and narrative. And you can not talk to them because their brain is deadlocked here. This is why the person you replied to, is correct here.

Languages are always evolving, because the needs they serve are always evolving. Stasis is death.

> I have been using ruby since 2005 or so. Static types were never relevant or needed in the slightest here.

We are like Liebniz monads, with disjoint views of the same universe due to our different experiences. I worked for several years at Shopify and there were droves of developers begging for types. Shopify itself recognized this need. We contributed early to Sorbet and began implementing it in the main monolith prior to it being publicly announced. I personally was the incident response on-call for a million-dollar bug that static typing would have prevented from ever being merged. And so on.

Static typed languages had been around a long time before Python, JS and Ruby gained popularity. All three of the latter now support some form of type hints.

Why did people switch to these languages in the first place and what's driving the current back-to-typed-languages trend?

I didn't misunderstand what this library is about. I assume the authors are using LLM's to help author their code in general, even meta-frameworks like this.