Must be significantly harder to develop MS Store apps. Due to sandboxing limitations?
I suffered through this Store pain recently, after buying a $$ game from Microsoft: https://www.thewindowsclub.com/cant-install-forza-horizon-on... (11 things to try!)
Microsoft also had a separate EXE to download to try to repair things, along with wsreset, wscollect, etc. Far too complicated.
Microsoft, the king of backward compatibility?
Tell me it is not true.
/s
They have their own distribution system, so they don't need this anymore.
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 overly sandboxed that it didn't fit most use cases and the permissions system of the store never seemed to line up with the APIs themselves.
then they tried their best to destroy myget by launching winget, which got forgotten about again. now even MS doesnt use their own store.
I'm not sure I would say Microsoft forgot about the store. I think Microsoft is like a Dog that has no head, no legs, only tails. And these tails have their own will and don't care about the dog in the slightest.
Was it... REALLY though? Everyone knew how to use the setup wizards.
I'm glad that after windows 10, you can finally install most software as NOT ADMIN via disabling(!) UAC completely :)
You can spend weeks of effort and hundreds of dollars just to ship an installable hello world app these days. The MS store takes care of signing, but there are other trade-offs.
The entire desktop TTHW (time to installable hello world) story is horrible across the board:
- Win: Decent tech foundation for updates made insufferable by code signing requirements.
- Mac: No update story, cobble together a bunch of tools/scripts, notarize releases with Apple (not very onerous), hope you don't ship an update that crashes at launch because you broke your updater too.
- Linux: No consensus on how to package. Bob wants a .deb, Alice wants a snap. Flatpak seems to be winning overall. The best tool to smooth over Win/Mac installer headaches (Conveyor) doesn't support flatpak. Bummer.
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.
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.
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 another .exe that was continuously checking for new versions, downloading them and starting them.
As malwary as it gets but it worked flawlessly!
The windows store nightmare that came after looks dreadful.
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.
Use Fedora for half a year and tell me what you prefer.
On the other hand, Steam et al are app stores where developers can get paid.
> On the other hand, Steam et al are app stores where developers can get paid.
Yes, this is exactly my point. App stores have a reason to exist. They provide discoverability and a streamlined way to monetise your app, something that is sorely lacking in open source projects. A case in point for example is Krita, which is published as a paid app on the Microsoft Store. The revenue generated by the sales goes to fund the development of the project. Linux needs an equivalent.
Produce the `./configure && make install` for Office and you would have a point.
I like the "one consistent system with one dependency tree" policy of Debian et al, but with flatpack, appimage, snap, etc. the "application" part of software might prefer the Windows/MacOS model.
I prefer good high-dpi support, Wifi and Bluetooth that works, usability, developers getting rewarded for their hard work, etc.
FYI I develop software for Linux in my free time, I don't get paid and I feel pretty rewarded.
Xrandr works just fine and has been for decades.
I'm saying Linux is a mediocre desktop operating system, especially on laptops.
I like the idea. A single place to search for common apps, that also keep them updated. I don't want to download the .exe again and again with ever update. Just do that in the background please.
Though I mostly use WinGet, but it's sadly not as user friendly as apt.
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?
But I agree, sometimes central place to get your software might be more reliable.
>No middle man
There usually is, very few software companies handle card transactions themselves. They usually farm it out to someone like Digital River (who aren't very trustworthy).
This is why no one jumps onboard with new stuff Microsoft wants to push. They don’t stick to anything. A dev can constantly chase after Microsoft’s latest pet projects, or they can simply ignore all of it, knowing it will eventually fall out of fashion and save themselves (and their users) a lot of trouble.
Then came Project Reunion, with the whole reboot, that five years later still hasn't reached feature parity, seems most of the team is gone, and they are even open sourcing it, with hopes that the community fixes the bugs that a $4 trillion valued company doesn't care about.
Of course only people on the Windows team care about this, because their salaries depend on it.
Unfortunately, there's a lot more random apps on Windows than macOS, so that was never going to be a good sell...
m-p-3•5d ago
At least they give the ability to be really specific about what you want to deploy using the Configuration XML file.
I wish they offered something similar on macOS.
cprecioso•1d ago