WSL VS sorbet

Off the top of my head was this bug that caused a lot of people using vbox to swap to vmware. Just a bunch of really annoying compatibility bugs that made it a nightmare if you were trying to use it like a native linux instance.

yeah. But, the github complaint says otherwise https://github.com/MicrosoftDocs/WSL/issues/798

https://github.com/MicrosoftDocs/WSL/issues/798 - maybe fixed a couple of months ago. I personally haven't tried.

After that https://github.com/MicrosoftDocs/WSL/issues/590 , fixed things for me.

Sorbet can do this, as long as you have type signatures for your code. Given Ruby's highly dynamic nature that's where tools like Tapioca come in to generate these, for example for Active Record models where instance methods are generated based on the database schema. But the moment when something returns T.untyped you're back where you were before - it helps but isn't perfect.

Sorbet[1] is currently the most robust tooling available. It has a few rough edges and limitations but it otherwise works great for 90% of use cases.

[1]: https://sorbet.org

There are solutions like sorbet[^1] and sorbet-rails[^2]. Have you tried them?

[^1]: https://sorbet.org/

[^2]: https://github.com/chanzuckerberg/sorbet-rails

Since I tried Sorbet, a Ruby type-checker, the idea of building an ahead-of-time compiler for Ruby is a cool side project that has been in my mind for some time now. To my surprise, during Hacktoberfest, I got to know Natalie, this AOT compiler written in C++ by Tim Morgan.

Rails has something similar called https://sorbet.org/ Haven't used it since I personally like the flexibility. But it exists if you're into it :)

Ever heard of Sorbet? https://sorbet.org/

Shopify is listed as using Sorbet, which is static typing for Ruby.

So to find things in a similar space, you need to look for languages with these sorts of constraints - so things like Sorbet for Ruby or pyright/pyre and you'll see similar and new ideas