4 ms·
You point is that this is simple, yet Microsoft with Thousands of engineers working over the span of decades never internally developed this idea or framework e
by boublepop 6y ago
You point is that this is simple, yet Microsoft with Thousands of engineers working over the span of decades never internally developed this idea or framework except after picking the brain of this particular person and doing a copy of that particular competing project.
Paintings are just paint on a canvas, and all code is just clicks on a keyboard. That doesn’t make it any less immoral to blatantly copy without recognition.
It’s perfectly fine to carry out a fork, the irony here is that Microsoft likely tried you play this angle of “we’re just competing, not copying you” because they thought carrying out a fork with attribution would blow up in their face, which this now has.
- 908B64B197 6y ago> yet Microsoft with Thousands of engineers working over the span of decades never internally developed this idea Ever heard of NuGet[0]? Been around since 2010. WinGet isn't a fork of AppGet, the codebases share nothing. [0] https://www.nuget.org/ https://www.nuget.org/