kayone
why do you think that is?
the manufacturers have no choice, it would be like suggesting they sell cars without seatbelts.
after all this is over, I'll probably do a write up of hall it all worked behind the scene + all the server code.
I'm proud of the work I've done on Sonarr. If someone doesn't want to associate with me because of it, then the feeling is probably mutual.
> I'm sure there was a reason they decided to not hire me. Maybe I had a shitty attitude? I don't know. I'm not questioning that. But I think an email letting me know and some credit would be fair to expect.
I might be wrong, but I don't think to have MS behind a project like that causing it exponentially grow was a betrail of users.
> There was an issue with my travel reimbursement, So I contacted the HR contact and at the same time asked about the Interviews, She told me someone will get back to me about that and they never did. This was on Feb 14th, 2020.
------
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 project. How it actually works. If I were the patenting type, this would be the thing you would patent. ps. I don't regret not patenting anything. And I don't mean the general concept of package/app managers, they have been done a hundred times. If you look at similar projects across OSes, Homebrew, Chocolaty, Scoop, ninite etc; you'll see they all do it in their own way. However, WinGet works pretty much identical to the way AppGet works. Do you want to know how Microsoft WinGet works? go read the article (https://keivan.io/appget-what-chocolatey-wasnt/) I wrote 2 years ago about how AppGet works.
I'm not even upset they copied me. To me, that's a validation of how sound my idea was. What upsets me is how no credit was given.
Even if that was the case, I have no regrets.
Issues like this were one of the main reasons I started working on appget. I died a little bit inside every time I saw a friend google an app and click on the first link (usually an ad) or click through the installation wizard as fast as they possibly could and not unchecking the toolbar, bundle, bonus, whatever else.
AppGet solves these issues from a couple of different angles,
1. we only allow packages hosted on the official vendor, maintainer websites.
2. All package manifests are simple YAML files on GitHub where they go through a PR/Review before getting merged.
3. For your _tech normal_ friends or family, they can search for apps in https://appget.net/packages/ and click the install button, and we do the rest. No command line needed. 4. We disable all bundled app installations by default.
For example here is the page for Keepass https://appget.net/packages/i/keepass
In the meantime, what you can do as a workaround, is to use `-i` param when installing apps to launch the installer in interactive mode. That will let you run through the installer and customize everything including the install location. I know it's not ideal, but if you want to use appget to automatically download, validate the installers and check for outdated apps, it might be a reasonable work-around.
AppGet doesn't use custom scripts on install; everything is defined by data (YAML files). The client uses the data in the manifest and knows how to deal with different installers. This alone makes appget more secure; if you trust the client (it's opensource and managed by the core team) you don't blindly run a PowerShell script as admin on your machine.
Also, adding/updating packages is trivial since all you need to do is update/create a very simple YAML file. Another benefit is we can upgrade the client to better deal with let's say MSI installers, and none of the manifests need to be updated since all the logic is in the client, the manifest only needs to identify itself as MSI.
This also means you can install an app in different interactivity levels, Silent (everything happens in the background), Passive (you see the installer and progress, but you don't have to click next or do anything) or Interactive (appget downloads and validates the installer and just launches it for you, but you can run through the installer and customized it as you see fit)
Our packages are more up-to-date. We have a crawler that checks for updates on regular bases, we use GitHub api, and check vendor sites constantly (over 500K of check events per day). Trivial updates are automatically pushed to the repository, For non-trivial ones the bot automatically creates a pull-request on GitHub to be reviewed by a human. Most cases we pickup updated releases for apps within hours.
AppGet can list, upgrade and uninstall apps that aren't even installed using appget. We check windows installer database as the source of truth. You can download appget right now, run "appget outdated" and I guarantee it'll find outdated apps for you.
I'm sure there are more things, this question comes up a lot, so I'm gonna spend some time and add a page to the documentation just for this.
As far as monetization, we do have plans for a paid offering, internally we are calling it "AppGet for Fleets" it'll be to manage/monitor app installation on a group of computers remotely using a hosted dashboard (SaaS offering).
AppGet as you see today and all of its stand-alone features will remain free and opensource.
take a look at https://appget.net if you use windows.
also, we don't run some random PowerShell script written by god-knows-who on your machine. All installs are driven by pure data, so the only thing you need to trust is the appget client itself.
e.g. https://github.com/appget/appget.packages/blob/master/manife...
What you explained here is one of the main selling points (as in convincing, appget is completely free) for appget.
AppGet pretty much automates what you explained here and more.
We automatically download and validate SHA256 of downloads (We have a strict policy of only allowing releases from the official source)
All package info that is used to install applications are fully public in our GitHub repository [1] (think homebrew)
Also, for less tech-savvy users, they can install applications through our gallery e.g. https://appget.net/packages/i/chrome using appget as long as they have appget installed on the machine.
[1] https://github.com/appget/appget.packages/tree/master/manife...