Hacker News Reader

I like TST. We use it in our code (FP'ish Kotlin).

But I also like stack traces, as they show me call-stack to the point the error happened. Something TST does not always show: different call-stacks can result in the same (or very similar) TST-stack.

it's secret superpower it to allow you to give up on trying your code to compile and then just to shim against some C# bindings

C# bindings?? F# and C# build on top of the same type system and can transparently access each other's types.

maybe I misunderstand, but iirc i had to compile C# first into a separate dll.

I must say this take seems a bit... grandiose... to me.

People have been banging on with type systems and similarly "better" capabilities for at least 2 decades [0] and Enterprise continues with a stark preference for language "practicality" and low barrier of entry.

IMO it's because it's best to keep engineers superficially interchangeable rather than having a highly stable system (perhaps stable over spec) and a costly workforce with lots of negotiation leverage. But I digress.

[0] https://en.wikipedia.org/wiki/Worse_is_better