> Why is taking out the part that actually checks the types at the developer's side a huge blessing? Oh, no, certainly we want to keep type-checking in the pip

> Why is taking out the part that actually checks the types at the developer's side a huge blessing? Oh, no, certainly we want to keep type-checking in the pipeline, somewhere. However, if the browser "understood" typescript, your codebase could have immediate hot-reload, without any transpilation in-between. The type-checking could then be (and already is when using something like esbuild/swc) an entirely separate process that happens independently. Webpack's HMR is pretty good, but not having to modify the code at all to have it work in the browser, that'd be much much better :) ... the browser being able to typecheck (and reject violating code) itself is certainly something I'd love to see eventually, but fully agreed, this is not happening anytime soon.