Aaah, good old Microsoft is back!
The Day AppGet Died
331–340 of 566 posts
Re: The Day AppGet Died
#332Earlier quoted context omitted.
Not really. Afterall his AppGet package was open source....
Last time I checked, something being open-source doesn't mean corps like MSFT can shit on them.
The MIT license expressly allows for shitting on software though. In fact it's allowed for anyone, not just megacorps.
Re: The Day AppGet Died
#333Hey Microsoft, whenever you do this, you lose all the goodwill you've built with developers. You have put me back in a buying position where I'm now thinking: how can I cancel my paid GitHub & Azure accounts?
Re: The Day AppGet Died
#334Earlier quoted context omitted.
MacPorts (né DarwinPorts) was created by Apple engineers long before the App Store existed. IMHO it’s superior to Homebrew in just about every way, existed long before Homebrew and targets the same audience (unlike the App Store which is targeting a very different population). If you haven’t looked at MP lately, it’s worth reviewing.
MacPorts still has a number of Apple engineers contributing to it, although it is no longer an Apple-sponsored project and I have no idea if they are doing so in any professional capacity. Homebrew, interestingly, has been moving towards an App Store-esque “binary distribution platform” for a while now.
Binary distribution is not bad, it's heaps better than forcing everyone to recompile the very same software again and again on their own laptops. See also Nix.
Re: The Day AppGet Died
#335Re: The Day AppGet Died
#336Earlier quoted context omitted.
I'm actually having a hard time imagining something like Sonarr making much of a negative pr splash. It doesn't download pirated shows, nor does it play them. It just organizes and renames and creates lists of missing episodes for files that may or may not be pirated content.
Mmmm... There is a certain segment of the tech industry that is morally opposed to piracy, and actively pursue those people. I know because I've seen the negative connotations they've received. Had a candidate with a homelab, peer inferred it was for piracy, didn't want to hire him because of that. I've also seen it in the weebs and also brainwashing Japanese Corp culture. I have a feeling because its m$ their cture…
A candidate had a device unrelated to the job which might be for piracy and you turned him down for that?
What sort of self-absorbed narciccist are you?
Re: The Day AppGet Died
#337Earlier quoted context omitted.
What new cuddly Microsoft? When did they grow fur? Did people honesty believe that some messaging and branding choices would outweigh the influence of institutional inertia, for such a large company?
Yes. People honestly believe this.
(*NULL && MAXINT++) == True
Logic is futile
Re: The Day AppGet Died
#338Earlier quoted context omitted.
You are a small Team in a big company. Your job is to create an App Manager. There is already a code base under a MIT license. You use it. I'm not seeing the issue.
The issue is bringing the author of the MIT code to your HQ for a fake interview and make suggestions that he will work with you. You just milk him for information and let him go without any further communication.
Classic brainrape.
Re: The Day AppGet Died
#339Earlier quoted context omitted.
Calling it "WinGet" was the real punch in the gut. Does Microsoft select for assholes or something? There's a thousand other package manager names [1] in the wild and they chose that one. So much for "developers, developers, developers"... [1] https://en.wikipedia.org/wiki/List_of_software_package_manag...
In all fairness: - "NuGet" is super-popular in .NET circles (included in Visual Studio by default) - "apt-get" is the classic tool for Windows Subsystem for Linux So "WinGet" certainly "makes sense" as a name without being a direct ripoff of AppGet
It still looks really bad. If you're going to copy and kill off [1] an OSS project, when you're a major company who owns the platform, with a long history of this sort of thing, after baiting the developer for information, then copying the name on top of it is just cruel and in poor taste.
Context matters. That's the key point here.
Plus your two examples out of a hundred or so examples doesn't make it common either (or maybe one in a half examples since apt/apt-get/apt-cache are the three Debian programs under APT umbrella).
[1] there was no way this project was going to continue despite their nonsense about "broadening the options in the community", they knew what they were doing
Re: The Day AppGet Died
#340Earlier quoted context omitted.
Hopefully they also weigh in the fact that screwing developers over is terrible publicity. Assume 100k developers see this and are slightly less inclined to trust MS in future, this bad publicity could easily cost them 1mn USD plus. A good will gesture of 100k USD at the start for consulting could have saved everyone a lot of trouble. See https://news.ycombinator.com/item?id=23332123 elsewhere in this thread for an e…
I find MS seems quite immune to terrible publicity in the recent years. "But it's not the same company as before! They are doing open-source now!" yada yada
I mean, isn't that because they haven't been screwing people over (that we know of) recently?
If more stories like this one come out I'm sure the goodwill turns fast.