@michael @lightweight @anildash just remember it will get worse, and they'll try to trap you with the transition cost, and have that "saved up" and set aside.
I've still got stuff in Google drive, but I've also got a NAS, etc.
@michael @lightweight @anildash Yeah, this issue is one of the things @pluralistic has written quite a bit about.
In my country, refusing to work with any Microsoft-derived technology in IT will basically remove >70% of jobs, right from the get-go.
We did get some good things out of M$'s laziness though, like the #LSP & #DAP #OpenStandard #protocols, which work just fine in #Emacs (why VSC when you have Emacs?) and have greatly improved its ability to be used for #Java among other languages.
@lightweight @michael @anildash @pluralistic Most employers being bad employers makes for some bleak prospects, but successful entrepreneurship tends to require skills, dispositions and ideas I don't really have.
A fully FOSS setup producing nothing closed-source means a *lot* of customer-facing consultancy (and lots of effort to even get customers), which has burned me in very unpleasant ways in the past. Having that be my main work instead of dev doesn't sound like much of an improvement.
@lightweight @michael @anildash
I agree.
VSCod(ium) is IMHO quite usable and I won't hesitate to call Typescript excellent, but it doesn't change that:
a) I'll never trust MS,
b) I despise, deplore and reject their anti-competitive business practices;
c) their forcing of their products (and DRM) onto people is deeply reprehensible
d) their office products + OSes suck
e) their business empire (including linkedin) is way more insidious & dangerous than most people are aware.
@michael @anildash I’m not sure there’s anything deeper going on than “we want to sell subscriptions and will make it extra easy for devs to be interested in buying them”
• “I like GitHub at home; let’s convince my employee to buy GitHub Enterprise at work”
• “boy, deploying my code to Azure is so convenient”*
etc.
(ICE is also a big GitHub client, which is a bummer)
* it sometimes feels like Azure is the only *real* driving factor behind .NET Core’s existence
@michael @anildash I would indeed watch out for a classic 1990s’ MS EEE strategy
Embrace: embrace git as a useful tool.
Extend: extend git into GitHub with capabilities like an issue tracker, pull requests, etc. Increasingly entice developers to rely on GitHub specifically, not git.
Extinguish: eventually make GitHub incompatible with regular git.
@volviq @flauschzelle @anildash See, I used to use BitBucket. I switched to GitHub because it was (and still is) the gold standard as both a platform and a community. I don’t want to have to give up those benefits in the name of tech liberation.
(That said, here I am on Mastodon; obviously I have *some* piratical inclinations. :D )
I know (and also use) GitLab, but there are also some criticisms of it (see somewhere else in the original post's replies), so if everyone used gitlab.com instead of github.com it would not be that much better...
Maybe a federated version could be a solution here? Then everyone could have their own instance but still create/comment on issues etc. on others' git servers without having to register a new account everywhere...
@michael @anildash Speaking of VS Code: The peculiar state is that a) the code is under MIT-license but b) the product is proprietary Microsoft with telemetry etc.
A super useful alternative I found:
https://vscodium.com/
"Free/Libre Open Source Software Binaries of VS Code" - easy to install and (for me) practically indistinguishable from the 'real' VS Code
@anildash all of these things except for maybe the npm repo are extremely easy to switch off of. Don't like vscode? Use another program. Don't like GitHub? Git clone+ one of several issue migration tools
I get what you are saying but these platforms have hardly any lock in compared to other spooky scary monopolies
@anildash Eh? You're being sarcastic, right? 😈
Oh, yeah, you left out LinkedIn during a layoff epidemic.