3 ms·
Windows legacy problems were very often, very much a case of Windows running on a ton of different hardware. Drivers have quite a bit to do with the pains of ha
by roc 13y ago
Windows legacy problems were very often, very much a case of Windows running on a ton of different hardware. Drivers have quite a bit to do with the pains of hardware fragmentation. And quite a bit of the legacy pain is in having to deal with the old (flawed/bugged/limited) abstraction layers and dlls that people would very much rather not have to support anymore, but cannot abandon due the installed base of the old hardware it supports.
As to quantity of complaints: you asserted these sorts of complaints just didn't exist. If you want to argue about whether they're overblown, or simply proportional with the fragmentation gripes of various historical platforms, that's quite a bit different.
- bluedino 13y ago> And quite a bit of the legacy pain is in having to deal with the old (flawed/bugged/limited) abstraction layers and dlls that people would very much rather not have to support anymore, but cannot abandon due the installed base of the old hardware it supports. It'd be interesting to see if the newer versions of Android would attempt to do what the newer versions of Windows did - detect an older application trying to use an undocumented feature, and then give the app what it wants to hear, instead of crashing or having a bug. Therefore, keeping compatibility with older programs. Microsoft of course had teams of people doing this kind of stuff.
- randallu 13y agoThere are a bunch of conditionals in the Android framework on which SDK version something was compiled against, so they already do this in a way.