Pretty cool! Maybe this could provide research for other projects to have a Linux compatibility feature, I know GrapheneOS and RedoxOS have been talking about that kind of stuff
5 Likes
Great stuff. I feel like within corps like Microsoft and Apple there’s a desire from the engineers to open source more things but it’s probably hard to get that done. Pure speculation though I have no idea.
1 Like
Overall Microsoft has really embraced open source. I think they’ve basically pivoted to trying to own everyone’s hardware (via everything becoming a part of Azure), so tight control over the software no longer matters to them.
Not sure about Apple. I haven’t noticed too many open source initiatives from their end tbh. Their open source work is either simply because they bought/forked a legacy FOSS project (CUPS, WebKit, BSD), or it’s very developer focused (FoundationDB, SDKs for building apps on Apple hardware). They don’t really have open source products like Microsoft does.
I would say your assessment most fits Google actually. They really seem to have no clear plan one way or the other when it comes to open source work. Seems like a very “every team for themselves” company to me.
6 Likes
The cynical take is that they dont want to fund it so they unleash it on the community instead, hoping it gets picked up and developed for free. When the open source(ness) gets too popular like what is going on recently with VSCodium, they remove third party support…
Still feels like Embrace Extend Extinguish to me…
4 Likes
AFAIK this is only for Microsoft-developped extensions, so not that big of a deal
1 Like
To be fair, that is true.
But still it sort of still kind of a d*ck move. If they put it out like that on version 1.0, I wont complain; but so far into the development on the product, I can only speculate that some executive or c-suite people is upset that clones are proliferating (as intended, mind you - this is how open source works).
1 Like