Miss Dada  🏳️‍⚧️

I am interested in stories on its ergonomics and how it helps people -- my only info right now is I've run it on a 6,000 line gem I wrote last year, it generated a ton of errors but did not identify any bugs

in contrast to when rust yells at me, it is almost always identifying an actual bug and so it feels like it's helping

to appease sorbet I've moved a bunch of code around, but it's purely refactoring, not changing behaviour, and I have not found any behaviour that needs fixing as a result of running it

that, by itself, is a really interesting ergonomic result to me: rust is extremely restrictive, but when it won't compile, I feel like I understand why ruby is incredibly forgiving, so I'm sure my codebase contains bugs, but everything sorbet is telling me about is noise

saying that, I'm only getting my codebase from `false` to `true` type checking, not `strict` or `strong` but the things it's complaining about at `true` are artificially restrictive already

especially since often it recommends to fix the "module does not have method f" error by including Kernel, which in my case breaks my program

but also it's just not necessary -- you cannot call a method from a module unless it's been included into a class, at which point Kernel is in scope

Unless it's included in a class which extends `BasicObject`