sorbet-typed VS Grails

The tooling around "installing" types for third party dependencies (the equivalent of doing "npm install @types/something" is non existent. I had to manually copy over files from https://github.com/sorbet/sorbet-typed, which is so far behind pythons and typescript, where you can just "pip install"/"npm install" the types. Not only that, most third party dependencies don't provide types, so the "coverage" is super incomplete. I had to try and create some third party types myself, bit even that was a challenge because it's so hard to be sure of the entirety of what's going on in a ruby codebase because the language is dynamic.

stdlib rbis are shipped with Sorbet. A limited selection of gem RBIs are available at https://github.com/sorbet/sorbet-typed.

And frameworks like Grails build conventions and helpers on top of Spring.

I don't have any direct experience and am only suggesting it because you mentioned RoR...But Grails (https://grails.org/) is basically the JVM version of RoR (Groovy on Rails -> Grails).

Grails - Spring under the hood. Much less boilerplate. Opinionated, which helps keep things consistent. Uses Spring-Security plugin for authentication.

Also, Grails, which a Rails like framework build on Groovy, a JVM scripting language.

Any JVM language to the rescue here? There’s one, but it’s not the one you’re thinking about. In a sign that this index may not accurately reflect our project reality, Groovy saw a meteoric rise of 0.86% to 1.04% last year! That was good for place 17. Yep, Groovy! Are people writing Gradle plugins in Groovy? Or is Grails having a resurgence? I’m as baffled as you are.