3 ms·

Microsoft Privatized Open Source, Killing JavaScript in the Process

3 points by MaysonL 5y ago

jjgreen 5y ago
without subscription: https://hackernoon.com/a-post-mortem-in-5-acts-how-microsoft-privatized-open-source-and-killed-javascript-in-the-process-5s5i33ma https://hackernoon.com/a-post-mortem-in-5-acts-how-microsoft...
noseratio 5y ago
> "TypeScript does use JavaScript constructs but has a lot more in common with C# ... It’s fairer to say that TypeScript is a C# superset, with some JavaScript limitations, which compiles to JavaScript." Lol. As someone who's reasonable good at C#, when I started learning TypeScript, I made that common mistake of approaching it as something similar to C#. Boy was I wrong, it's a totally different language and philosophy, and the prior knowledge of C# actually serves a bad favor here.
raxxorrax 5y ago
Not a web developer, I don't like Typescript or the usual web frameworks and prefer using Javascript just as is. I use it mainly for visualization and control (embedded dev). To me adding a toolchain just for the benefits of typescript isn't worth it, so I don't really understand the popularity. Just writing stuff I can immediately execute is the main benefit. Yes, I could configure my environment in a way that the effort is small, but as I said, not worth it. Maybe for real webapps, where you go through the effort of cleanly bundling your sources anyway, but that isn't for me. While many may have jumped in joy while reading the headline, I do think Javascript will stay alive longer than anybody would want. What is true however is what the article describes and MS tries to do. They know they lost a lot of developers and try to get/buy them back. It is also true that Typescript isn't a superset. Just nearly a superset. Your work on Github will be monetized. That is already the case you might think, but MS will probably soon introduce business repositories of some form. It will be like an app store for source. Shitty, proprietary and exploitative. Don't host too much on Github, you have been warned.

3 points by MaysonL 5y ago

without subscription: https://hackernoon.com/a-post-mortem-in-5-acts-how-microsoft-privatized-open-source-and-killed-javascript-in-the-process-5s5i33ma https://hackernoon.com/a-post-mortem-in-5-acts-how-microsoft...

noseratio 5y ago

> "TypeScript does use JavaScript constructs but has a lot more in common with C# ... It’s fairer to say that TypeScript is a C# superset, with some JavaScript limitations, which compiles to JavaScript." Lol. As someone who's reasonable good at C#, when I started learning TypeScript, I made that common mistake of approaching it as something similar to C#. Boy was I wrong, it's a totally different language and philosophy, and the prior knowledge of C# actually serves a bad favor here.

raxxorrax 5y ago

Not a web developer, I don't like Typescript or the usual web frameworks and prefer using Javascript just as is. I use it mainly for visualization and control (embedded dev). To me adding a toolchain just for the benefits of typescript isn't worth it, so I don't really understand the popularity. Just writing stuff I can immediately execute is the main benefit. Yes, I could configure my environment in a way that the effort is small, but as I said, not worth it. Maybe for real webapps, where you go through the effort of cleanly bundling your sources anyway, but that isn't for me. While many may have jumped in joy while reading the headline, I do think Javascript will stay alive longer than anybody would want. What is true however is what the article describes and MS tries to do. They know they lost a lot of developers and try to get/buy them back. It is also true that Typescript isn't a superset. Just nearly a superset. Your work on Github will be monetized. That is already the case you might think, but MS will probably soon introduce business repositories of some form. It will be like an app store for source. Shitty, proprietary and exploitative. Don't host too much on Github, you have been warned.