Windows 10: Microsoft now blames the manufacturer for the package manager it “copied” – but offers no apologies



Microsoft has now admitted that it did not give Canadian developer Keivan Beigi credit for his role in the new WinGet Windows 10 package manager.

Last week, Beigi, who created the open-source package manager AppGet for Windows, accused Microsoft of copying its work for WinGet without acknowledging the influence of its product.

Beigi says Microsoft has copied large parts of AppGet to provide WinGet, the Windows package manager announced in Microsoft Build 2020. Last week, he detailed his discussions with a senior Microsoft executive named Andrew who approached him. in July 2019 with an invitation to meet and discuss. “how we can make your life easier by building AppGet”.

SEE: Microsoft 365: A Cheat Sheet (Free PDF)

Andrew Clinick, a group program manager on the team responsible for installing apps on Windows, has now admitted that Microsoft had not given Beigi credit for AppGet’s influence on WinGet.

“Our goal is to provide a great product to our customers and our community where everyone can contribute and be recognized,” Clinick wrote.

“The last thing we want to do is alienate anyone in the process. That’s why we’re building it on GitHub outdoors where anyone can contribute.

“Over the past two days we’ve been listening and learning from our community and it’s clear that we haven’t achieved that goal. Specifically, we haven’t been up to par with Keivan and AppGet. It was. the last thing we wanted. ”

Beigi said he didn’t mind that Microsoft copied its open source Windows Package Manager, but argued that Microsoft should have at least correctly attributed the design of WinGet to AppGet, rather than describing it in Beigi’s words. as only “another package manager that exists”.

AppGet received a passing mention in Microsoft’s WinGet announcement after Microsoft described rival Windows package manager Chocolatey as having a “vibrant community with a massive collection of apps and a rich history supporting both open source clients and enterprises “.

“There are many more like AppGet, Npackd, and the PowerShell-based OneGet Package Manager-Manager,” Microsoft added.

Despite the late credit, Microsoft’s handling of AppGet and WinGet has been clumsy, callous, and marred by “slow and appalling communication speeds,” according to Beigi’s account.

Some would argue that Microsoft should have given the credit to Beigi without the developer raising the issue in the first place – especially given Microsoft’s efforts to shed its evil corporate image that has waged war on the open. source and which once followed the mantra “kiss, extend, and extinguish”.

Sometimes Microsoft buys side projects from developers, like the VisualZip utility, which was acquired from the same Microsoft engineer who also created Windows Task Manager in his den in the 1990s.

The passing mention of AppGet was another sore point for Beigi, who wrote in 2018 how issues with Chocolatey inspired him to relaunch the AppGet project that would eventually be of interest to Microsoft. AppGet currently has over 800 packages that it can install on Windows.

SEE: How to know if your device is eligible for the Windows 10 May 2020 Update

The Canadian developer says Andrew emailed him a week after their first meeting and told Beigi he had “an opportunity to help shape the future of Windows and app distribution in Azure / Microsoft 365 “, potentially as an employee where he would join Microsoft and that would be getting AppGet.

He went for an interview at Microsoft’s headquarters in Redmond in December, which apparently went “well”, but Andrew did not inform him that he would not get the job at Microsoft until six months later – the eve of the unveiling of the preview of WinGet at Build 2020.

“We also call AppGet in our blog post because we believe there will be room for different package managers on Windows,” Andrew told Beigi.

“You will see that our package manager is also based on GitHub, but obviously with our own implementation etc. Our package manager will also be open source, so we would obviously be happy to have any input from you.”

Luckily for Beigi, he wasn’t sure he wanted to work for such a large company, and he wasn’t excited about the prospect of moving from Canada to the United States. However, Beigi has decided that the product and project will now be phased out on August 1 due to the existence of Microsoft’s WinGet.

Clinick’s post, which is no apology, confirms Beigi’s account and details how AppGet helped Microsoft achieve “better product orientation” for WinGet:

  • No scripts during installation – something we fully agree with and do not allow with MSIX.
  • A rich manifesto definition within GitHub – the power of being open combined with rich declarative metadata about the app is so important to achieving Goal # 1.
  • Supports all types of Windows application installers.
  • Transparent updates for apps in the repository.



Comments are closed.