4 ms·
I’ve been writing TS for a year now and I find TS annoying. Especially for react components with state management of some kind, the types get so complex you alm
by fiddlerwoaroof 5y ago
I’ve been writing TS for a year now and I find TS annoying. Especially for react components with state management of some kind, the types get so complex you almost need unit tests to assert they are what you think they are. Additionally, TS being a structural type system with no access to nominal types at all eliminates a whole class of “ghosts of departed proofs” modeling techniques. (And, I know you can work around this, but those workarounds are ugly.)
My view is that I’d use TS if I have to but I’d pick either plain JS / CLJS or something like purescript if I really wanted types.
- jamil7 5y agoI haven’t touched the ecosystem really for a number of years but my last JS project was in TS and I hated it for the same reason. The overhead of bringing in yet more npm modules and types and build steps for questionable levels type safety. Languages with much better type systems exist.
- canaus 5y agoSuch as?
- arcanon 5y agoThe year is 2021. People argue for a toolchain that takes a static language, compiles it to a dynamic one, then runs it with an interpreter on the server side. Humanity ended shortly thereafter.