Maybe Im reading the vibe wrong but to me, it seems like when it comes to the programmer/sysadmin/poweruser side of Microsoft, they seem pretty good in terms of not being total shit. Their "normie" facing side though seems hella shady though. Things like ads in windows, the speculated subscription model for windows, office 365, one drive spam.

For example, things like vscode, WSL, winget, power tools, the new console app, powershell, typescript, opening up .net to native cross platform. All these things are pretty sweet and seem like something they wouldn't be interested in doing.

It almost feels like there are two Microsofts right now and they are at odds with each other. So yeah, I guess enjoy it while it lasts, but always be ready to drop them like a sack of potatoes.

do you worry that Microsoft is going to eventually do the Microsoft thing and horribly fuck it up for everyone?

I'm not really sure what you have against Microsoft, or what "Microsoft classic" you'd be referring to...

In the last 10 years or so they pretty much moved everything C# related to Core, cross platform and open source. Even the decision making for the language is "Open source" - Microsoft is not really behaving the same as the Microsoft from 2000...

Soo, I don't really know how they could possibly fuck it up. They might add more and more features you might not like, but you could just choose to stick to an older version of the language

It’s open source. Anything is better than JS.

Everything is temporary. If we were talking about a niche language, I might worry a little bit that it could just lose momentum and die. But TS is a juggernaut. The only way typescript “dies” is if JS integrates enough of its features to make it redundant.

Besides that, if Oracle managed to allow Java to continue to grow and flourish, I have confidence that MS can do at least that well. I also think lumping all of MS’s products into the same boat is a mistake. They have been pretty good stewards of their languages for decades.

The rug pull is google's forte

I'd like to point out that TypeScript is a superset of JavaScript, so if anything goes wrong with it, you can just remove the type information and you'll have regular JavaScript.

FYI, there's a TypeScript community in Lemmy.

!typescript@programming.dev

I'm sure that any non-trolling/flamebait discussion over TypeScript is welcomed in there.

It's nice, but it would be great if JS were replaced by WASM.

Regarding "doing the Microsoft classic" whatever that means... I don't believe in judging a company by what they did in the past. They should be judged by what they actually do now and in the future. So far, they haven't done anything bad. And anyway they've been good stewards of recent products that they've taken over (GitHub for example).

As for TypeScript itself... well my opinion is language choices should always be done on a case by case basis. So far I have never personally encountered an individual case where TypeScript is the best choice. They do exist though, so I won't hold it against anyone if they choose to use it.

TS is open-source, so if they do I'm certain that there will be a fork available within moments.

Its an improvement over plain js, but we say "you cant build a castle with bricks made of shit" the shit is javascript. Undefined errors are there using TS...