41–50 of 73 posts
the installation story for devs writing windows apps has been dreadful for 3 decades. vs used to help you build setup.exe, which was always a huge chore to use. clickonce was launched to replace all this with hosted manifests and auto-updates and modern features like that, and immediately forgotten about because it was so broken. nobody ever used it. then they brought out WinUI and the windows store, which was so ove…
Earlier quoted context omitted.
> No consensus on how to package. Bob wants a .deb, Bob wants a deb. I give him a deb. Bob is not happy because I compiled the software with an incompatible glibc. I deploy a webapp for Bob. Alice gets to use it too.
And then there's Gentoo just smuggly accepting fate and always rebuilding everything rather than trying to force compatibility with libraries.
I even use flatpaks for the stuff I don't want to build, everything just works most of the time.
there are only two versions of libc mine and the one you brought with you.
Earlier quoted context omitted.
Well, the rest of the world (outside of MacOS and Windows) settled on repositories and package managers, with hash verification, versioning, updating/installing/uninstalling with composable commands (that can also be used via GUIs), etc. Use Fedora for half a year and tell me what you prefer.
And yet none of those "outsiders" have figured out a way to economically renumerate developers for their work. Flathub had a initiative a few years ago to add payments to help developers fund their projects, but I haven't seen anything come out of it.
On the other hand, Steam et al are app stores where developers can get paid.
the installation story for devs writing windows apps has been dreadful for 3 decades. vs used to help you build setup.exe, which was always a huge chore to use. clickonce was launched to replace all this with hosted manifests and auto-updates and modern features like that, and immediately forgotten about because it was so broken. nobody ever used it. then they brought out WinUI and the windows store, which was so ove…
> vs used to help you build setup.exe, which was always a huge chore to use. Was it... REALLY though? Everyone knew how to use the setup wizards.
the installation story for devs writing windows apps has been dreadful for 3 decades. vs used to help you build setup.exe, which was always a huge chore to use. clickonce was launched to replace all this with hosted manifests and auto-updates and modern features like that, and immediately forgotten about because it was so broken. nobody ever used it. then they brought out WinUI and the windows store, which was so ove…
I did run into a lot of issues with the store/winrt APIs where there were backdoors that the NTDev team used to work around all the limitations, but they would never publish them.
I’ve read the article and still don’t know why.
They have their own distribution system, so they don't need this anymore.
Seriously who needs a Store App on a desktop OS? The process should be as simple as visiting app’s website, optionally paying, and installing. No middle man, hence less point of breakage.
I'm not sure getting software directly from developers is less likely to break than getting it through a store. The store may do QA to ensure that broken apps cannot be uploaded, developers may vanish and hence absent someone else being able to maintain it the app will eventually break, and how are security issues handled?
the installation story for devs writing windows apps has been dreadful for 3 decades. vs used to help you build setup.exe, which was always a huge chore to use. clickonce was launched to replace all this with hosted manifests and auto-updates and modern features like that, and immediately forgotten about because it was so broken. nobody ever used it. then they brought out WinUI and the windows store, which was so ove…
When I was developing C# winforms applications 15 years ago, I just created a fat signed .exe that was then distributed. Installers and click once stuff was a big turn off for users. On startup, if not already there, it automagically copied itself to the installation directory, created an autostart directory link and started it from the new location and got killed with a named pipe command. It contained and extracted…
Seriously who needs a Store App on a desktop OS? The process should be as simple as visiting app’s website, optionally paying, and installing. No middle man, hence less point of breakage.