Specifically, do you worry that Microsoft is going to eventually do the Microsoft thing and horribly fuck it up for everyone? I’ve really grown to appreciate the language itself, but I’m wary of it getting too ingrained at work only to have the rug pulled out from under us when it’s become hard to back out.
Edit: not really “pulling the rug”, but, you know, doing the Microsoft classic.
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Follow the wormhole through a path of communities !webdev@programming.dev
Everything is temporary except for people’s opinion on Microsoft.
The company is spending a ton on supporting developers, tools, and open source projects but every time they get mentioned people just hark tired lines of past ill deeds.
I mean if they didn’t want a shit reputation, they shouldn’t have done those past ill deeds.
I think people should in general put as little trust as possible in corporations. Ensuring your tools, language and platform are as free as possible is a good idea.
Just look at the problematic situation for VS Code extensions by Microsoft, which are non-free.
I can agree with the goal but sadly the corporations have already got their claws deep in the tech stack.
Facebook control React. Google has its hands around Chromium, Android, Go, Angular and I’m sure dozens of others. Then of course Microsoft now own npm, GitHub etc. You’re making your life very difficult if you entirely avoid corporate entities.
If we don’t give corporations credit when they do run projects well then there’s no incentive for them to not go full on capitalist greed and destroy them.
Corporations aren’t people and don’t behave like people. Giving credit to corporations doesn’t work in the long term, because people who work for them are constantly changing. The ones who did a good job may leave or get replaced, and the ones who take over may not care about maintaining their legacy.
Surely the inverse is also true then? People change, leadership changes, goals change so why assume the Microsoft of today is as bad as its past self?