Language Selection

English French German Italian Portuguese Spanish

Microsoft and Proprietary Software

Filed under
Microsoft
  • Red Cross urges halt to cyberattacks on healthcare sector amid COVID-19 [iophk: Windows TCO]

    The Red Cross called for an end to cyberattacks on healthcare and medical research facilities during the coronavirus pandemic, in a letter published Tuesday and signed by a group of political and business figures.

    Such attacks endanger human lives and governments must take “immediate and decisive action” to stop them, the letter stated.

  • FBI offers US companies more details from investigations of health care [cr]acking

    Criminal and state actors continue to target U.S. clinical trial data, trade secrets, and the “sensitive data and proprietary research of U.S. universities and research facilities,” the FBI told industry in an advisory this week. “Likely due to the current global public health crisis, the FBI has observed some nation-states shifting cyber resources to collect against the [health care and public health] sector, while criminals are targeting similar entities for financial gain.”

    The advisory, which CyberScoop obtained, includes multiple examples since February of state-linked [attackers] trying to compromise and retain access to the networks of organizations in the U.S. health care and public health sector. It is the latest in a series of warnings from U.S. officials about similar cybersecurity incidents as the race for a coronavirus vaccine intensifies.

  • Microsoft copied its new Windows Package Manager from rival AppGet, claims developer

    Beigi interviewed in December, and then never heard anything back from the company for nearly six months until he received a 24-hour heads up that Microsoft was launching winget last week. “When I finally saw the announcement and the GitHub repositories, I was shocked? Upset? I wasn’t even sure what I was looking at,” says Beigi.

    Beigi claims the “core mechanics, terminology, the manifest format and structure, even the package repository’s folder structure” of Microsoft’s winget are all heavily inspired by AppGet. Microsoft only briefly mentions AppGet once in its announcement, in a throwaway line that lists other Windows package managers.

    “What was copied with no credit is the foundation of the project. How it actually works,” explains Beigi in a separate Reddit post. “And I don’t mean the general concept of package / app managers... WinGet works pretty much identical to the way AppGet works.”

  • The Day AppGet Died.

    TLDR; I’m no longer going to be developing AppGet. The client and backend services will go into maintenance mode immediately until August 1st, 2020, at which point they’ll be shut down permanently.

  • Apache Pulsar joins Kafka in Splunk Data Stream Processor

    Splunk built out its event streaming capabilities with a new update, released Wednesday, to its Data Stream Processor to bring in more data for analysis on the Splunk platform.

    The DSP technology is a foundational component of the information security and event management vendor's Data-to-Everything approach.

More on AppGet

  • Microsoft Windows Package Manager Accused of Copying Open Source AppGet Tool

    A week ago, Microsoft announced a new Windows Package Manager (winget) at Build 2020. It was one of the few unexpected reveals during the virtual developer conference. However, one developer now says Microsoft copied his technology and integrated it into Windows.

    Keivan Beigi, who created a package manager called AppGet, says Microsoft showed a lot of interest in the tool last year. He says the company spoke to him and was interested in AppGet. Later, the company ghosted Beigi and he did not hear from Microsoft again.

    Fast forward to Build, and Windows Package Manager arrives (winget) looking suspiciously like AppGet. Beigi says he was shocked to see winget copied so much from his solution.

Embrace and kill?

  • Embrace and kill? AppGet dev claims Microsoft reeled him in with talk of help and a job – then released remarkably similar package manager

    Keivan Beigi, developer of AppGet, has described how Microsoft nearly hired him to work on the open-source Windows package manager as an official feature, then went quiet for six months before announcing WinGet, which Beigi says is "very inspired by AppGet".

    Microsoft unveiled WinGet at its Build virtual event earlier this month. At the time, Senior program manager Demitrius Nelon said: "What about insert any other package manager here? We think they are great... We have already talked with a few of the well-known package manager teams. Chocolatey has a vibrant community with a massive collection of applications, and a rich history supporting both open-source and enterprise customers. Scoop provides a convenient way to allow software to be installed without the UAC popups. Ninite keeps an eye on updates for all the apps it installed. There are many others like AppGet, Npackd and the PowerShell-based OneGet package manager-manager."

    AppGet got a mention here, but only as a footnote. Beigi's account gives a different perspective. He says he was approached in July 2019 by a "high-level manager at Microsoft" from the Windows app deployment team. The manager thanked him for building AppGet and making "life so much easier" for Windows developers and asked to meet Beigi to "get feedback on how we can make your life easier building AppGet".

AppGet Creator Says Microsoft Stole His Product

  • AppGet Creator Says Microsoft Stole His Product

    Last week, Microsoft released its new Windows Package Manager, called WinGet. But as it turns out, they stole it: Keivan Beigi, the creator of a popular package manager called AppGet, describes how Microsoft wooed him last year and discussed employing him, only to later ghost him and release WinGet, which he says is basically identical to AppGet.

"no apology to dev for killing open-source package manager"

  • AppGet 'really helped us,' Microsoft says, but offers no apology to dev for killing open-source package manager

    Microsoft's Andrew Clinick, a group program manager in the Windows team who is involved with the development of the WinGet package manager, has tried to make good with the open-source community by publishing an acknowledgement of what was borrowed from the existing AppGet project.

    A preview of WinGet was released by Microsoft during the recent virtual Build event, prompting the developer of AppGet, Keivan Beigi, to post about how he was approached by Microsoft in July 2019, supposedly to offer him help with development. He said he was questioned by the vendor in detail about his package management ideas, invited to apply for a job with Microsoft to work on an official version of AppGet, and then heard nothing until the moment before WinGet was launched.

Microsoft finally gives AppGet developer the credit he deserves

  • Microsoft finally gives AppGet developer the credit he deserves

    Microsoft is crediting a developer after he accused the company of copying the core mechanics of its new Windows Package Manager. AppGet developer Keivan Beigi provided a detailed account of Microsoft reaching out with interest about his package manager, inviting him for interviews, and then ghosting him for months before unveiling its own package manager that he felt was inspired by his work.

    Beigi claimed the “core mechanics, terminology, the manifest format and structure, even the package repository’s folder structure” of Microsoft’s Windows Package Manager (winget) are all heavily inspired by AppGet. Microsoft only briefly mentioned AppGet once in its announcement, in a throwaway line that lists other Windows package managers. A variety of Windows package managers exist, and are used to automate the process of installing and updating apps.

More on AppGet

  • Microsoft Admits Windows Package Manager (WinGet) Was Inspired by AppGet, Credits Developer

    Back at Build 2020 last month, Microsoft introduced a new Windows Package Manager (Winget) for Windows 10. The new tool allows developers to easily download services to help app development. However, the new open source solution found controversy after the creator of a similar tool argued Microsoft has stolen his idea.

    Microsoft has now admitted it should have credited Keivan Beigi for his work in getting WinGet off the ground. However, the company stopped short of apologizing to the Canadian developer.

    Windows Package Manager presents a way for developers to access tools that are not available to them from the Microsoft Store. If you want to know how to use WinGet with PowerShell or GUI, check out our tutorial here.

  • Windows 10: Microsoft now credits maker of package manager it 'copied' – but offers no apology

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

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

  • Microsoft Belatedly Credits AppGet Developer For WinGet

    Microsoft has belatedly credited the Canadian developer of AppGet as the inspiration for its WinGet package manager for Windows 10, after mentioning the original app only in passing during a recent launch event.

    Microsoft launched a preview of WinGet at the Build developer conference in May, and after saying it had talked with the ” well-known package manager teams” behind Chocolatey, Scoop and Ninite, the company mentioned there were also “many other” apps including “AppGet, Npackd and the PowerShell based OneGet package manager-manager”.

    Following the launch, developer Keivan Beigi, of Vancouver, Canada, said he would be discontinuing the development of AppGet, a package manager for Windows he has said he developed in response to frustrations with existing tools such as Chocolatey.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Debian Developers' Blogs on Technical Work

  • Markus Koschany: My Free Software Activities in June 2020

    Welcome to gambaru.de. Here is my monthly report (+ the first week in July) that covers what I have been doing for Debian. If you’re interested in Java, Games and LTS topics, this might be interesting for you.

  • MessagePack vs CBOR (RFC7049)

    I recently wanted to choose a binary encoding. This was for a project using Rust serde, so I looked at the list of formats there. I ended up reading about CBOR and MessagePack. Both of these are binary formats for a JSON-like data model. Both of them are "schemaless", meaning you can decode them without knowing the structure. (This also provides some forwards compatibility.) They are, in fact, quite similar (although they are totally incompatible). This is no accident: CBOR is, effectively, a fork of MessagePack. Both formats continue to exist and both are being used in new programs. I needed to make a choice but lacked enough information. I thought I would try to examine the reasons and nature of the split, and to make some kind of judgement about the situation. So I did a lot of reading [11]. Here are my conclusions.

  • Debian PPC64EL Emulation

    In my post on Debian S390X Emulation [1] I mentioned having problems booting a Debian PPC64EL kernel under QEMU. Giovanni commented that they had PPC64EL working and gave a link to their site with Debian QEMU images for various architectures [2]. I tried their image which worked then tried mine again which also worked – it seemed that a recent update in Debian/Unstable fixed the bug that made QEMU not work with the PPC64EL kernel. Here are the instructions on how to do it.

Hardware: Wainlux, RasPi, Arduino

  • Wainlux K6 & Alfawise C50 Mini Laser Engravers Offered for $130 and Up

    A few days ago I saw Wainlux K6 “most compact, powerful and simple-to-use” laser engraver on Kickstarter for about $159. I did not think too much of it at the time, but this morning I thought it already showed up for pre-order on GearBest for $129.99 as Alfawise C50. But I was mistaken, as both products are different, albeit sharing some of the same attributes. Nevertheless, this brought back my curiosity about these types of devices, especially with Wainlux K6 having already managed to raise over $200,000 from close to 1,400 backers so far. So let’s look at both.

  • Travel the world with a retro musical phone
  • Deck out your ride with an Arduino-controlled spoiler

    Car spoilers can provide downforce for better performance, or simply give the appearance of speed. To take things to another level, Michael Rechtin designed his own custom wing that doesn’t just sit there, but pitches up and down via a pair of servos. The system utilizes an Arduino Nano along with an MPU-6050 for control, adjusting itself based on his Mazda’s movement, and powered is supplied by a LiPo battery. Suction cups are used to attach the spoiler, so installation appears to require no actual modification of the car whatsoever.

Programming: XML, Perl and Rust

  • 10 Excellent Free Books to Learn XML

    XML is a set of rules for defining semantic tags that describe the structure and meaning of a document. The user of XML chooses the names and placement of the tags to convey the nature of the data stored in a document. XML can be used to markup any data file to make it easier to understand and process. In addition, it has been applied to many special domains of data: mathematics, music, vector graphics, the spoken word, financial data, chemical symbols, and web pages among others. Here’s our recommended free books to master XML.

  • 2020.28 Bridges 7

    Arne Sommer, inspired by a solution of a previous Weekly Challenge, wrote a small series of blog posts about the seven bridges of Königsberg:

  • A tour with Net::FTP

    When we want to have a way to exchange files between machines, we often think about rsync, scp, git or even something slow and complex (looking at you Artifactory and S3), but the answer is often right in front of your eyes: FTP! The “File Transfer Protocol” provides a very simple and convenient way to share files. It’s battle-tested, requires almost no maintenance, and has a simple anonymous access mechanism. It can be integrated with several standard auth methods and even some virtual ones, none of which I show here. [...] I got the idea to backup and centralize automatically the configuration file during the creation of the build pipeline workspace. It was intended to help both developers (configuration “samples”) and support team (see history, versioned then we can check diffs, file to replay). The constraints were to be able to exchange file from various places with variable users. The FTP protocol is a perfect fit for that. I added also a cronjob to autocommit and push to a git repository and we had magically a website listing versioned configurations files. In addition, FTP proved later to also require zero support. I mean really zero maintenance!

  • Perl Mongers, Unite!

    pm.org is great for resources, but there's no obvious way to promote your meeting. Not that there needed to be when the meetings were local events, but now, thanks to Covid-19, these meetings are taking place virtually. Why limit yourself to your local members? I am convinced that there are plenty of pockets of mongers that, if united and connected, would make the world realize that Perl Is Not Dead.

  • Programming languages: Now Rust project looks for a way into the Linux kernel

    The makers of systems programming language Rust are looking at how to adapt the language for use in the Linux kernel. Josh Triplett, an Intel engineer and lead of the Rust language project, says he'd "love to see a path to incorporating Rust into the kernel", as long as it's done cautiously and doesn't upset Linux kernel creator Linus Torvalds.

IBM/Red Hat Leftovers

  • Command Line Heroes: Becoming a Coder
  • Bank of America, Google, and Red Hat Executives Join OASIS Board of Directors

    OASIS, the international standards and open source consortium, today announced that three new members were elected to its Board of Directors: Jeremy Allison of Google, Rich Bowen of Red Hat, and Wende Peters of Bank of America. Their depth of experience in the open source and open standards communities bolsters the Board’s reach and establishes OASIS as the home for worldwide standards in cybersecurity, blockchain, privacy, cryptography, cloud computing, IoT, urban mobility, emergency management, and other content technologies. These three new members join the continuing members of the Board: Martin Chapman of Oracle, Bruce Rich of Cryptsoft, Jason Keirstead of IBM, Beth Pumo of Kaiser Permanente, and Daniel Reidel of New Context. Reelected Board members Frederick Hirsch, Individual member; Gershon Janssen, Individual member; and Richard Struse of Mitre will each serve a two-year term starting in July 2020.

  • OpenStack @ 10: Red Hat’s take on a decade of customer defined clouds and an update on Red Hat OpenStack Platform

    From the early days, Red Hat has supported the OpenStack project and we’ve built a platform of our own with Red Hat OpenStack Platform. This month, we look back at how far OpenStack has come in the last 10 years, how Red Hat has contributed and lastly, we celebrate the general availability of our next version with Red Hat OpenStack Platform 16.1, available later this month. [...] By 2014, Red Hat was already a major contributor to the project. This not only brought enterprise support from a heavily-invested contributor, but also helped drive community input from customers who may not otherwise have participated. The increasing diversity and chorus of voices within the community helped bring forth new projects and features to solve problems. In addition, the introduction of Red Hat OpenStack Certification widened industry support, launching with more than 100 tech industry leaders as members. The Icehouse (I) and Juno (J) releases coincided with Red Hat OpenStack Platform’s three-year support life cycle, launched with Red Hat OpenStack Platform 5. This meant that enterprises could choose a platform and standardize on it for an extended period, providing stability for the workloads that need it. Red Hat OpenStack Platform 6 kept the ball rolling with more than 700 enhancements, updates and changes to the platform as it continued to grow and mature.

  • How Automation can help banks improve security, compliance, and productivity

    FSIs spend a lot of time responding to auditors. Compliance with regulatory mandates often dictates processes. However, variance in processes can increase tension between developers working to improve the organization’s agility; teams responsible for maintaining operations; and security and compliance teams. Without a clear joint process, each of the teams may develop their own. Inconsistent IT configurations, patching and testing can make management and reporting difficult. A lack of shared processes can also allow technical debt to build, which inhibits change and introduces risk. In addition to managing digital transformation, IT systems are upgraded regularly, entailing an intense period where the IT team focuses on configuration and testing every piece of technology. While this work is critically important, and because the risk exposure is significant if each component is not updated and tested, it is also stressful and can be tedious. The challenge is further increased because many financial organizations are operating across a range of different environments, like Windows, Linux, public and private clouds, virtualized and container environments, increasing the complexity of their IT footprint.

  • My Outreachy Internship: The journey so far…

    I’ve gotten stuck with many issues over the coding period, some more facepalm than others. For example, I wasted almost a week trying to get my setup running on docker-compose only to realize that the problem was just mislabelled services. In another one, while writing a script to initialize a MySQL db I put a space after the ‘-p’ so my builds kept failing. Of course, these issues shouldn’t have taken more than a couple of hours to figure out but more often than not it took days. All this reminds me of the struggle I had when I started learning JavaScript. Trusting the environment/ecosystem did not come easy. It was normal for me to think that the bugs that I was getting were because of a bigger force that I did not understand yet. This would force me to blindly go on an expedition to really understand what’s going on.. only to realize that the issue was right in front of me and I never needed to read anything beyond the files that I wrote. However, even after the time I had lost the net result was always positive. The more ‘blind expeditions’ I went on the more knowledge I accumulated and the more confidence I gained to commit. A bigger hurdle for me has been adjusting to the work-from-home lifestyle. Especially with the pandemic my entire routine has been disrupted and finding a balance has been a challenge.

  • Introduction to Red Hat Insights

    Red Hat Insights is a SaaS application that is available free of charge to everyone with a valid Red Hat Enterprise Linux (RHEL) subscription. This article provides a brief introduction to Red Hat Insights, shows how RHEL systems are integrated into the cloud service, and lists key documents and resources related to the service. Author's note: I'm testing the service as part of my job at the Bielefeld IT Service Center (BITS) at Bielefeld University. This article reflects my personal view of Red Hat Insights. Furthermore, I would like to clarify that I am a member of the Red Hat Accelerators community.

  • Developing and testing on production with Kubernetes and Istio Workspace

    Due to container-orchestration platforms like Kubernetes and Red Hat OpenShift, developers have become very efficient about deploying and managing distributed and containerized applications. But can we say the same about application development and testing? In this article, I briefly discuss how cloud-native development is transforming the traditional development cycle of coding, building, and testing. I then introduce the idea of testing on production, not as a meme but as a necessity. Finally, I introduce Istio Workspace, a tool for developers working with distributed systems running on Kubernetes or OpenShift. [...] Testing new functionality before it reaches production has always been hard, but the shift from monoliths to microservices has brought scale, which has increased the challenge of testing locally. We see developers trying to use tools like Red Hat CodeReady Containers or Minikube to spin up whole applications composed of multiple services. While this approach works well when projects are relatively small, it’s not so easy when you introduce more fine-grained services, and the graph starts to grow. It is not feasible to spin up even a medium-sized distributed system on your own machine. Using replicated environments such as staging or quality engineering (QE) gives some confidence, but it’s expensive in terms of both cost and maintenance. Despite the effort of defining infrastructure as code, there are still potential differences in the target machines’ configuration; they just show up on the operating system and hardware level. It is also frequently impossible to get the same load and volume of data on the test system that is in the actual system. Therefore, testing on production is no longer a meme: It’s a reality and a necessity. What’s needed is a way to use your favorite tools to develop, build, and debug your code locally, but have your application behave as if it were running in the production cluster.