3 ms·
If you notice from the last tc39 conversation about the types proposal, there's a bit of tension where people are reasonably asking, should we really be stuffin
by 90s_dev 1y ago
If you notice from the last tc39 conversation about the types proposal, there's a bit of tension where people are reasonably asking, should we really be stuffing more and more compilation into the browser? At what point do they push back and say, let the developer compile as much as they can ahead of time? I think wasm really has that advantage, that it forces us to do so, and saves time and resources in the user's browser. I'm not sure what the right balance is, though. I've wanted TypeScript in the browser for ages. But I see their point.
- benoau 1y agoI think the right balance is offering choice. Code compiling might take a moment just like shit code takes a moment, bloated code takes a moment, bad developers take a moment, bad software takes a moment, seems arbitrary to decide TS is one moment too many. But more importantly, seems impossible that anything could join the web stack because every other language is certainly a much more complicated proposal.