Original author of sorbet-rails here. I tried and it did take some work to integrate with Rails, because how dynamic Rails code can be.

But it's pretty useful once setup. It can know when an attribute is nullable or non-nullable, which is a big deal. We even use Sorbet to limit the usage of some dynamic Rails API so that it's more sane.

Companies that use Rails have also started working on https://github.com/chanzuckerberg/sorbet-rails, worth checking out!

While we're on the topic of static analysis of code that uses Rails... I suggest also using other static analysis tools as they make sense. I lead the Railroader project, an open source security static analysis tool for programs built on Rails. It doesn't guarantee finding all security problems, but it can help. More info here: https://railroader.org/

Yes, join the slack! While Stripe doesn't run rails all other companies in private beta did!

Both Shopify and Kickstarter are on Rails.

I wonder why Github didn't join the private Beta?

Maybe their forked version of Ruby had something to do with it.

IIRC last time I poked at their enterprise image and dumped the code there were bits of custom type annotations. That was around 2-3 years ago.

The parser for Sorbet was actually entirely given to us by GitHub. They were fabulous partners early on in the project and we're grateful for their contributions.

Understated, but awesome! Thanks for the insight!