I miss the days when only seasoned, professional programmers working for actual companies and releasing under that company released software.
So how should people go about becoming "seasoned, professional programmers" in the first place?
The difference is that every platform I can think of that uses APT allows root to add signers.
Debian-based PC operating systems allow the administrator to add third-party repositories with their own certificates. They also don't require that code be signed just to execute; one can install applications from outside the repositories or use applications compiled from source code without having to pay a recurring fee for a "developer license". This is in contrast to platforms designed to work with only one repository maintained by the operating system publisher, such as game consoles, iOS, Windows Phone, Windows RT, and the Windows Runtime environment of Windows 8 and 8.1.
but many open-source apps can be found at the store from unofficial sources that have a cost
FSF says it's perfectly fine to distribute free software for a fee, so long as the license is followed.
But platforms relying on a single app store have in the past made copyleft license compliance difficult or impossible. The GNU General Public License, for example, defines "source code" to include what GPLv3 calls "Installation Information" and GPLv2 calls "scripts used to control compilation and installation". When a platform requires all code to be digitally signed, a signing key is part of this "Information" or these "scripts". And the terms for obtaining a code signing certificate tend to forbid developers from sharing the private key with the public. This is why GPL software like VLC can't be on Apple's App Store, nor can ScummVM be on the Wii console.
If you're really hardcore and only have Dell equipment, you can use the service tag ID for the machine name!
But how would that be limited to Dell shops? My employer runs mostly HP computers, each with a conspicuous serial number.
With your bare hands?!?