Live data from Hacker News

What is wrong with Microsoft buying GitHub

jacquesmattheij.com

131–140 of 228 posts

Re: What is wrong with Microsoft buying GitHub

#131
post #68
post #5

TLDR; the 90’s happened. Delete your github account because Microsoft is evil. I’m surprised this article got this far because it really doesn’t add anything unique to discussions that are already happening.

Putting personal sentiment aside (delete github account part) an article like this is needed to sum up and justify developer worries that are scattered through discussions here and other online communities.

That’s my whole point. Without the part about deleting your account and the unnecessarily long introduction to what github is this article is a bullet point list of what Microsoft did in the 90’s. (With the exception of the telemetry and skype acquisition) Anyone can look up this history.

Re: What is wrong with Microsoft buying GitHub

#132
post #24

Earlier quoted context omitted.

Another recent example: lockdown of ARM-based Windows machines, preventing the installation of other operating systems.

I really dislike how you get downvoted (your message is faded out) here. Do people really applaud removal of control of their own devices?

I think it's because Microsoft's reason for doing this is plausible and not as anti-competitive as that comment makes it seem - locking down the boot process has serious security benefits.

Re: What is wrong with Microsoft buying GitHub

#133
post #29
post #21

Earlier quoted context omitted.

How is Apple not developer friendly?

XCode is a clunky horrible mess of an IDE, iTunes Connect is worse, and they charge $100/year for a developer account. Also, they try to lock you in to buying Apple hardware to develop for Apple devices (though you can get around that using, among others, Microsoft's Visual Studio App Center).

Agreed about XCode but Eclipse is also a horrible mess of an IDE, that doesn't make IBM unfriendly to developers.

Re: What is wrong with Microsoft buying GitHub

#134
post #13

Assuming GitHub was actually losing money and couldn't fix that problem quickly enough it's fair to assume they had to sell, and it's reasonable to believe there aren't that many companies who could have bought them if you think an understanding of the domain is important, then you're really limited to Facebook (user surveillance, adverts), Apple (bad at software, not developer friendly), Google (user surveillance, a…

The assumption is missing some context. A couple of years ago GitHub underwent internal re-organization or, as some people put it, got overrun by suits. Predictions at the time were rather grim.

https://news.ycombinator.com/item?id=11049067

Some parallels to the Nokia-Elop affair could be made.

Re: What is wrong with Microsoft buying GitHub

#135
post #132

Earlier quoted context omitted.

I really dislike how you get downvoted (your message is faded out) here. Do people really applaud removal of control of their own devices?

I think it's because Microsoft's reason for doing this is plausible and not as anti-competitive as that comment makes it seem - locking down the boot process has serious security benefits.

I admit I may be ignorant, but could you spell out the security benefits of going from "locked down but user-openable" to "not user-openable"?

(edit: specifically benefits that couldn't be effectively addressed by making it a little difficult and scary to open that lockdown?)

Re: What is wrong with Microsoft buying GitHub

#136
post #122

Earlier quoted context omitted.

That's… completely false. At least for me. You should really stop and think before accusing people to have noob workloads. Even cronjobs work… The performance is sometimes better than on native linux, as a few of the syscalls are better implemented on windows. The file performance is abysmal, but that only hurts if you're using npm (and there you're in a world of pain already anyways). The only thing lacking, is that…

Grep 150,000 source files on Linux and on WSL and come back to me. That's a pretty standard console load. It kills git operations, package managers, compilers, the lot. ALL the tools I use it for. Well USED it for. Real data: linux -> 1.3 seconds, all from buffer cache on a cranky old 10 year old HP desktop with 8 gig of RAM and bottom end SSD. wsl -> over a minute on a 12 core i7 with high end m2 SSD, every time. Th…

Source code files are small... but hardly a lot though. I've usually been doing extensive search on big files, and ripgrep is great for that (and available for windows).

Re: What is wrong with Microsoft buying GitHub

#137
post #106

Microsoft is not a company that ever contributed my life as a Linux user and open source contributor for years. In fact, it always made life harder for me. Here is a recent example; because Microsoft made a deal with Lenovo, now new Thinkpads are designed for just Windows. If you're a Linux user, good luck in your new adventure. People say "isn't it like IOS or Android?"; it's not. We had this freedom of using Linux,…

You know that Microsoft are the largest corporate contributor to open source projects on Github right?

Microsoft is probably one of the largest contributors to Linux itself.

Re: What is wrong with Microsoft buying GitHub

#138

Earlier quoted context omitted.

Considering your point, what has Microsoft done since the 90's to make you believe they had a change of heart/culture/orientation?

They're the largest corporate contributor to open source projects on GitHub :)

Taht means little to me. Is Facebook excused for their scandals because they open-sourced and maintain React?

Re: What is wrong with Microsoft buying GitHub

#139
post #122

Earlier quoted context omitted.

Grep 150,000 source files on Linux and on WSL and come back to me. That's a pretty standard console load. It kills git operations, package managers, compilers, the lot. ALL the tools I use it for. Well USED it for. Real data: linux -> 1.3 seconds, all from buffer cache on a cranky old 10 year old HP desktop with 8 gig of RAM and bottom end SSD. wsl -> over a minute on a 12 core i7 with high end m2 SSD, every time. Th…

Source code files are small... but hardly a lot though. I've usually been doing extensive search on big files, and ripgrep is great for that (and available for windows).

  $ find ~/src | wc -l
  242341
Maybe, maybe not.

Re: What is wrong with Microsoft buying GitHub

#140
What I find sad is that github didn't find a way to be profitable on its own.

I would really like to have some Consumers' co-operatives that would provide hosting/online services around open source. I wouldn't mind to pay something to have private hosting for me and subsidizing the hosting open source projects.

Post reply on HN