I resonated with the post as I'm in a similar position but I'm really sad that typescript chose just to be a thin layer on top of javascript.
The sentiment mostly comes from having the JS ecosystem mostly being untyped and having to interact with it.
That being said I tried io-ts but found it undocumented, missing examples and hard to write. For future libraries/projects I'm looking to try again ReasonML, tried in the past but had to write too many bindings.
I've been rolling io-ts into an app I inherited and have been porting to TypeScript. If you know a little Haskell/Scala type FP, the docs are plenty. I think the lib could definitely have a shallower learning curve for folks coming from Go though (what my back end devs write mostly).
The sentiment mostly comes from having the JS ecosystem mostly being untyped and having to interact with it.
That being said I tried io-ts but found it undocumented, missing examples and hard to write. For future libraries/projects I'm looking to try again ReasonML, tried in the past but had to write too many bindings.