2 ms·
These are all great points, thanks for digging in here. It does sound like you give the TS community a lot of credit with respect to toolchain stability and th
by spmurrayzzz 6y ago
These are all great points, thanks for digging in here.
It does sound like you give the TS community a lot of credit with respect to toolchain stability and thats nice to hear for someone like me who isn't directly involved in that community apart from browsing the issue tracker every month or so.
I'll concede that I do work backwards from the "you don't know what you don't know" bias, and given my previous experience with other type systems, I tend to privilege the status quo (e.g. our software works well, five 9's of uptime, virtually no runtime errors reported via APM, developer productivity is high, business objectives are being met, etc).
I need to work on that bias, because it can become an infinitely recursive argument.
- striking 6y agoDefinitely, and there's nothing wrong with maintaining the status quo if it's working really well as-is. But I think it can be pretty surprising to folks that haven't had an opportunity to play with TS, just how powerful the tooling is. Perhaps one way to break through that bias is to start up a side project and play with it a little.
- spmurrayzzz 6y agoI actually have done a few projects with TS, but none of them were really put to the full professional SDLC test. e.g. managing upstream dependency changes, lots of developers contributing, business constraints, etc. Personally I am very bullish on Deno, which goes beyond just native type system, but we'll see how that project ultimately plays out.