4 ms·
Supporting TypeScript OOTB in any capacity was itself "appealing to the masses". Being able to use TS without the burden of setting it up was a big selling poin
by frou_dh 4y ago
Supporting TypeScript OOTB in any capacity was itself "appealing to the masses". Being able to use TS without the burden of setting it up was a big selling point that resulted in people giving Deno a try, particularly in the early days.
Search this transcript for "any mistakes so far": https://changelog.com/podcast/443 https://changelog.com/podcast/443
- SyrupThinker 4y agoYes, I agree with that. To me the difference between this and the current changes is that TS support seems to have been a decision done quite early. Meanwhile configuration and npm support was something that initially (pre and at 1.0 times) was something considered a bad thing. Now, not so much. I would lie if I said that such a hard stance on these things wasn’t what initially drew me to the project.
- LunaSea 4y agoI don't understand how breaking every dependency in the ecosystem just to not have to setup a package.json or tsconfig.json file is worth it.
- selfmodruntime 4y agoIt's really not. Deno broke most of its promises, so for me personally, it's no longer worth switching over.
- Sysctl232 4y agoSetting up TypeScript with node is maybe 1 minute work? I don't understand this argument.