(no title)
negativegate | 5 years ago
First of all C# doesn't run in the browser without compiling to WASM which has all sorts of caveats.
Second, I don't see how the fact that one could compile TS to C# would suddenly put everyone "on the .NET stack". Does the same risk exist if we can compile JS to C#? Which would work about just as well (i.e. not). And TS is also open source and produces reasonably readable JS, so it's not like there's even any lock-in.
Wouldn't it make more sense to be worried about compiling C# or other languages to WASM? Which I'm also not worried about.
runawaybottle|5 years ago
Did you think Typescript would be the native language in Deno? No, you thought it was something that you might or might not use depending on the situation. Well guess what, that choice is gone for you in Deno’s case. These things compound.
It’s one of the reasons you will see people make a simple blog site with create-react-app, they are so inoculated with the hammer that everything is a nail. Did we think we’d be using React like that and forgo style sheets? Just inline all styles? That’s what we all do now. I had no idea we’d become that nuts, but it happened.
It’s not particularly bad in all cases, but for the web it is because we’ll stop using standard technologies that are supported across all types of scenarios.
negativegate|5 years ago
Yes? I thought that was the whole point. Actually I'm confused about the use of "native" here. It supports running both TS and JS files? And the TS files must be compiled to JS before they can be run anyway. So I'm not seeing any choice that was lost.
That’s what we all do now
I mean, some people do, but I don't. Not everyone uses React / Vue / etc, and afaik it's only React that is forgoing stylesheets. And it's not like stylesheets are dead or that styling elements through JS is non-standard. (I do use Vue, with stylesheets)