Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Can we trust Microsoft with Open Source? (2021)

dusted.codes

Post reply on HN
Print view View original

11–20 of 121 posts

Re: Can we trust Microsoft with Open Source? (2021)

#16

Post by nonrandomstring »

Trust is a complex thing. It's much more than a rational, game-theoretic or economic equation, it's emotional. Nobody "trusts" Microsoft.

People need it. People fear it, or fear losing it. People suffer it. Or they have no choice due to pressure or policy. Or they don't know any better. Or they are tricked into believing something about it. But in the end, the often forced choice to use Microsoft is a strategically created imposition by a company with billions to spend on manipulation and political manoeuvring.

Re: Can we trust Microsoft with Open Source? (2021)

#17

Post by audidude »

> Yes, that is right, Visual Studio for Mac is a closed source version of the formerly open source MonoDevelop IDE after Microsoft acquired Xamarin.

Having all of my GPL code ripped out of MonoDevelop so it could become Visual Studio for Mac was the straw that made me write GNOME Builder, GNOME's flagship IDE.

Re: Can we trust Microsoft with Open Source? (2021)

#18

Post by marcodiego »

audidude wrote: post #17

> Yes, that is right, Visual Studio for Mac is a closed source version of the formerly open source MonoDevelop IDE after Microsoft acquired Xamarin. Having all of my GPL code ripped out of MonoDevelop so it could become Visual Studio for Mac was the straw that made me write GNOME Builder, GNOME's flagship IDE.

Oh! So you are Christian Hergert, right?

I've been completely deaf to GNOME dev tools for a few years. What are the plans (if is there any) for a reasonably good RAD or ui builder tool (besides cambalache)? Is there any hope for blueprint + workbench turning into something to fill this gap? Was there any progress or plan on the "designable" interface for GTK?

For the record, I wrote this comment some time ago: https://news.ycombinator.com/item?id=35632761

Re: Can we trust Microsoft with Open Source? (2021)

#19

Post by ho_schi »

486sx33 wrote: post #5

Nope, and they’ve proven time and time again that we can’t trust them in any way shape or form

https://web.archive.org/web/20230315200925/http://antitrust....

What did changed since Microsoft used ACPI as tool against Linux?

Enforced Auto-Updates, Ads, Cloud Account enforcement, Blocking Firefox partially in Teams [1], Setting Teams as Browser (Edge?), WSL (intent is not compatibility, it is to prevent migrations to Linux), Azure is a giant security problem and finally the deal with Qualcomm (hinder Linux on ARM) like we are in the 90ies?

The crap named Secure Boot with Microsoft as Certificate Authority. After certificates proofed to be miserable on the internet for 25 years. What about signing with a user generated private key (stored in a keyring or similar) of the superuser and storing the public key in the UEFI? Which would be simple and reliable. No. Microsoft opted for the solution which depends on their goodwill and the biggest possible attack surface.

And Pluton looks so awkward that Lenovo and Dell turned it immediately off.

I will not trust them. Their business model is greed, making the users itself hostile actor against all others. Using something intentionally incompatible and borked isn’t “your department”. You harm others with incompatible APIs, ABIs, weird “Word” files and Teams.

I didn’t considered to use DotNet. GNOME removed it a long time ago and it is fine (Tomboy/Mono -> Gnome/C++). The only thing which seems good is LSP. But the hard work is done by CLANG and others. Not Microsoft.

[1] Teams worked six months ago flawlessly with Firefox. Even screen-sharing on Wayland. But they greyed out and blocked the video-call button. Until I figured out that I can initiate calls through the calendar…lol. It is like 2001.

Post reply on HN