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

The Day AppGet Died

keivan.io

Post reply on HN
Print view View original

391–400 of 566 posts

Re: The Day AppGet Died

#391

Post by throw_m239339 »

smcl wrote: post #247

Every time I see the “Microsoft <3 open source” stuff I get really suspicious, and this kinda confirms that I’m right to be. I’m grateful of their more open culture these days (dotnet alone is a big achievement) ... but I feel like there’s been a number of incidents like these which snap me back to reality and remind me they’re really just paying lip service to the idea and don’t truly buy into open source.

So much for the "I love the new Microsoft" people here… same as the whole Microsoft, doesn't even have the decency to credit people where credit is due… Of course, nothing illegal here, but this is borderline plagiarism… at least pay the guy, or donate to his foundation or something…

Seems like Microsoft owning GitHub thinks all the code on GitHub belongs to Microsoft…

Re: The Day AppGet Died

#392

Post by ra »

sillysaurusx wrote: post #380
kayone wrote: post #80

Author here, Because it's sure to come up here is a comment I wrote on Reddit that clarifies somethings, I haven't updated the original article since I'm not sure what the etiquette for updating a highly shared article is. ------ Code being copied isn't an issue. I knew full well what it meant to release something opensource and I don't regret it one bit. What was copied with no credit is the foundation of the projec…

I flew to Seattle on December 5th to have a full day of interviews/meetings at Microsoft HQ. I met with four different people; three of the meetings were more like your typical interviews; the meeting with Andrew was more about what we should do once this is all over and how we would migrate AppGet’s process and infrastructure to be able to handle Microsoft’s scale. We talked about some of our options, but in general…

Under the circumstances, it wasn't just a regular interview and so it was either rude (neglectful) not to get back to him or possibly (unlikely) there were other reasons... i.e. someone in the hierarchy had another plan.

Re: The Day AppGet Died

#394

Post by hoffs »

waon wrote: post #202
alasdair_ wrote: post #131

Earlier quoted context omitted.

It’s mentioned in the article: “ the core mechanics, terminology, the manifest format and structure, even the package repository’s folder structure” The manifest format is particularly egregious.

Not disagreeing with you, but I think it's better to make it a little bit more clear what exactly was copied. Reading the article mentioned in the OP, the main selling point for appget seems to be that the packages are written in yaml: > Do you want to know how Microsoft WinGet works? go read the article ( https://keivan.io/appget-what-chocolatey-wasnt/ ) But that alone doesn't particularly strike me as a completely…

Who says it was fake interview? Not everyone who interviews is hired...

Re: The Day AppGet Died

#395

Post by microtherion »

dmix wrote: post #339
TAForObvReasons wrote: post #279

Earlier quoted context omitted.

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…

> If you're going to copy and kill off an OSS project

Many OSS projects (and pretty much all of mine) were started to scratch a particular itch, so if that itch gets scratched by another project, I'm not terribly concerned.

It's more problematic if the competition is a half assed solution that, by virtue of being backed by a larger company, still sucks the oxygen out of the space you're trying to serve.

Re: The Day AppGet Died

#396

Post by throw_m239339 »

harry8 wrote: post #139

Re-licensee all your appget code as GPL v3. Everything about it. It might put the wind up them a little. They hate GPL. Good example of the strength of the GPL for projects you want to be open and don't want mega-corp to embrace and close. BSD, MIT etc if you're fine with that being done for the project. There are other dimensions for licensing, this is just one consideration of many in your decision.

Yep, this is why GPL exist. "But corporations hate GPL" as I can hear there often, well tough luck… GPL is about the rights of the users, not corporations. Another exemple of why open source projects should adopt GPL or AGPL, nothing less.

Re: The Day AppGet Died

#397

Post by throw_m239339 »

chii wrote: post #166
shp0ngle wrote: post #126

Earlier quoted context omitted.

They didn’t copy the code, just the APIs and ideas. In another words, if ideas were copyrighted, GNU/Linux wouldn’t exist.

Their lawyers will have a hard time justifying that none of the original source was used to create their new win-get project, given that the author of appget has met with the engineering team directly. So if it were GPL, microsoft would likely need to license their new winget project under GPL, which would be a win/win for open source.

> Their lawyers will have a hard time justifying that none of the original source was used to create their new win-get project, given that the author of appget has met with the engineering team directly.

Exactly

Re: The Day AppGet Died

#398

Post by creativecupcak3 »

It amazes me how level-headed the author really is about all this. I feel like I'm a lot more upset about this than the author. And, just like him, I don't care that they "forked" the project. I'm upset of how cunning of Microsoft this whole thing feels.

Re: The Day AppGet Died

#399

Post by throw_m239339 »

Conan_Kudo wrote: post #189
benatkin wrote: post #24

I don't want to support this company. What are good alternatives to GitHub, TypeScript, npm, and Visual Studio Code (besides Atom)?

> GitHub Pagure[1] is a good option here. > TypeScript You could just use JavaScript? > npm There aren't any at this time, as far as I know. > Visual Studio Code (besides Atom) Sublime Text[2] is a favorite of many, though I use Emacs[3]. [1]: https://pagure.io/pagure [2]: https://www.sublimetext.com/ [3]: https://www.gnu.org/software/emacs/

> npm / There aren't any at this time, as far as I know.

yarn?

Re: The Day AppGet Died

#400

Post by marvinblum »

BetaDeltaAlpha wrote: post #57
benatkin wrote: post #24

I don't want to support this company. What are good alternatives to GitHub, TypeScript, npm, and Visual Studio Code (besides Atom)?

Gitlab is a contender for sure. I use it at my dayjob. I don't know if any of the other big editors have caught up to VSCode in terms of ecosystem though.

Depending on the language take a look at the product range from JetBrains. I use GoLand for example and it's the best IDE I've ever used.
Post reply on HN