3 ms·
Thank God, I would really appreciate this. The TypeScript usage was the one thing that I didn't like about Deno. Why add complexity to a new project which star
by cocktailpeanuts 6y ago
Thank God, I would really appreciate this. The TypeScript usage was the one thing that I didn't like about Deno.
Why add complexity to a new project which starts from scratch? JavaScript is good enough and there's no need to make it confusing by adding another layer.
- untog 6y agoThis is talking about the internal Deno code. The user facing side will still support TypeScript, though you’re also free to not use it if you want.
- lowercased 6y ago> JavaScript is good enough and there's no need to make it confusing by adding another layer. To some people, JS itself is relatively confusing, and TypeScript reduces that confusion. EDIT: And... someone's clarification is saying this is internal framework code, not userland support for TS. Seems like a non-issue, really. They don't want to use it, but want to provide support for others to use it in their projects.
- eloff 6y agoYou can use JavaScript with Deno. Nobody is forcing you to use TypeScript. This doesn't change anything, it's for their internals. Why anyone would ditch static typing on a large collaborative project is beyond me though.