Raspberry Pi OS has turned into spyware for M$:
And yes, they add M$'s repository key to APT's trusted database and add their repo to APT's repo list.
Or informing you via a NEWS file.
So now every time you do "apt[itude] update", M$ will know about it.
RPF thought it was good to blog about 'it' after all:
.. by a M$ snake-oil sales representative.
"VS Code is a free, open source developer text editor"
That is "free" as in beer, not freedom. And yes, the code is available, so technically open source, but you can't distribute the binary.
So technically he isn't lying.
But this also proves you (still) can't trust anything that comes from M$.
And shame on #RPF for giving this credence.
But what actually pisses me off the most is this:
Linux isn't hard to learn.
Linux becomes hard to learn, when you first learn something else and then have to unlearn that first in order to learn the new thing.
Then it is different from what you know and that makes it hard.
That is why M$ and Apple give their software (almost) for free to elementary schools, so children get locked in early.
🖕 🖕 🖕
@FreePietje "lock in early" is Adobe's strategy too—it's not so much that (modern) creative open source tools like Krita and Blender are so hard to use compared to Adobe's monsters, but everyone is used to Adobe's so it's always "but this is haard!" because it is different to use
@orionwl @mep1911 @FreePietje Google are in a perfect position to do EEE, and in fact they are already doing so by pulling features out of chromium (and into chrome) that derivative browsers (foolishly) relied on. This strategy isn't new. And this VSCode thing has all the ingredients to take on a similar role in the IDE world.
@kekcoin @orionwl @mep1911
I've used the Debian build of Chromium for a while (as secondary browser) as it disabled various anti-privacy 'features' in chromium. About a year ago I concluded that this was just a losing game. And while open source, (afaict) g👀gle controlled everything. The amount of 'questionable' things G👀gle has done these last couple of years, made me ditch it then. Because of the context.
That G👀gle moved sync from chromium to Chrome was therefor completely expected by me.
@FreePietje @orionwl @mep1911 Yeah when the whole Sync scenario played out my first response was just a jaded "what did you expect? that service uses google servers, it was proprietary all along, it should never have been in chromium in the first place!". But it was pointed out to me later that downstream browsers also used this function and now lost access.
> it should never have been in chromium in the first place!
Excellent point, I had actually overlooked that.
By putting it in chromium all downstream browsers would normally have it, making the sync with android seamless for far more users, thus locking users in.
@FreePietje @orionwl @mep1911 Not just "locking users in", but also "locking browser vendors in". This is pure speculation but it wouldn't surprise me if vendors decided to make the switch to chromium-based partially because this function came included. At the very least they never bothered building their own, which they might have were it not for the inclusion.
And now all those non-chrome users get presented with the choice to create a new vendor-specific sync account or switch to chrome.
Bitcoin Maston Instance