3 ms·
I think the point this article proves is actually not that apps have a limited lifetime or that breakage should be expected. It proves that mobile APIs are terr
by jeroenhd 5y ago
I think the point this article proves is actually not that apps have a limited lifetime or that breakage should be expected. It proves that mobile APIs are terrible designed and each new version comes with its own terrible design.
Microsoft has gone above and beyond to keep applications working properly but in many instances where the APIs were used properly, user mode applications are nearly impossible to make incompatible. Basic system APIs were standardized almost thirty years ago and to this very day you can take a Windows 3 Hello World program, compile it, and run it.
If I can run twenty year old Windows applications on Windows 11 but I can't run a calculator that hasn't been updated for two years, the problem is clearly not with the concept or with development. iOS APIs, as well as Android APIs, have been atrocious from the beginning and every release deprecates some of that terrible, badly-designed old behavior. The biggest breakage for userland code was that the assumption that all code was running as an admin was challenged way back in 2006 with the release of Vista, and even that was easy to overcome by marking the shortcut as an admin only program.
Someone should look into getting Wine running on mobile (well, Android, iOS probably wouldn't allow such a subsystem to execute) so we can run some Windows CE/Windows Mobile/Windows Phone? applications. The Win32 API has been the most stable API in the history of consumer computers. It's a real shame that old Microsoft, the comic book villain of the tech industry before Jeff Bezos made his first billion dollars, is outperforming modern API designers. This is not a tragedy of lazy app developers littering the app store with their cruft, this is a story of badly management by the surviving mobile tech giants.
UNIX/POSIX has had an even better track record, but Linux is in a constant state of helper application API shift, be it X11 vs Wayland, PulseAudio vs Pipewire, systemd vs initv. The parts that count for the experience, like GUI elements, are all non-standard with their own tastes and preferences, which is Linux's power and weakness. Yes, Windows 8+ and recent macOS have been going more "move fast and break things", but both of those platforms still maintain their old APIs without too much of a sweat. The real challenge is the drive model and other kinds of superprivileged code, and Microsoft deciding it needs a new GUI API every time the CEO sneezes.
- shakna 5y agoWine has official Android builds [0]. They're a little unstable in my experience, but I've run a few Win32 programs with them. [0] https://dl.winehq.org/wine-builds/android/ https://dl.winehq.org/wine-builds/android/
- eternityforest 5y agoPolitics aside, Microsoft does some things light years better than anyone. Linux is my preferred OS, but most of my favorite features are the ones people accuse of being "Too Windows like". I kinda would have liked to see what would happen if Linux Standard Base had really taken off. Move fast and break things sucks. Modern windows mostly sucks because of forced updates, which are in a way kind of the same idea. Tech should work. Every time you turn on the computer you should.be confident it will work, even if you updated yesterday after not updating for three months. Even if there's a hardware issue it should still work if software can work around. Reliability should not be sacrificed for beauty or simplicity or keeping developers from getting bored. Pipewire does it right. It's backwards compatibile with Pulse/JACK/ALSA. Just like systemd is partly backwards compatibile with sysvinit.
- kderbyma 5y agothis is why you seperate out the software makers from the hardware makers....it requires the other side to play niceley....apple is a bully and sadist.