And even in cases where compatibility is broken, there's still the possibility on Windows or GNU/Linux or even OS X to fire up somet...
And even in cases where compatibility is broken, there's still the possibility on Windows or GNU/Linux or even OS X to fire up something along the lines of DOSBox or VirtualBox or somesuch and be able to recreate the necessary environment to play 15, 20, even 30-year-old games. Last I checked (which was admittedly a long time ago, seeing as my ship-jump from iOS to Android was a few years ago), you have to jailbreak an iOS device in order to achieve similar functionality thanks to Apple's rather-draconian restrictions on such things. Apple's attitude toward iOS - move fast and break things - is in stark contrast to even OS X, where a lot of software made for OS X versions as old as 10.5 will still run relatively happily (though apparently Yosemite broke quite a few things). That said, there's a time and a place. On my servers, for example (which are typically running OpenBSD or some GNU/Linux distro), I'm at least somewhat-okay with backwards-compatibility breaking (within reason) if it means having better performance or security. In that context, I'm relying far less on closed-source software (if I'm using closed-source software at all, which is incredibly rare for me when it comes to servers), which means that most of the software I actually rely on will at the very least usually have community-supported patches up the wazoo to support those backwards-compatibility-breaking changes (like OpenBSD's switch to a 64-bit time_t, which basically just amounted to recompiling a bunch of stuff - most of which was already done by the ports tree maintainers when creating binary packages).
Posted by yellowapple on Apr 17, 2015, 1:27 AM
Tags
Related issues
- You obviously did this for fun, I don’t want to throw any shade on it and have no criticism, I also make fun things just because.¹ So ta...
- Many devs love to shit on the guy from the 'I just want the exe.
- Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
- Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
- I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
- Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments
reliability (SaaS)
You obviously did this for fun, I don’t want to throw any shade on it and have no criticism, I also make fun things just because.¹ So ta...
NewMany devs love to shit on the guy from the 'I just want the exe.
Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
App broken with Mosquitto broker 7.0.0
And even in cases where compatibility is broken, there's still the possibility on Windows or GNU/Linux or even OS X to fire up somet...
And even in cases where compatibility is broken, there's still the possibility on Windows or GNU/Linux or even OS X to fire up something along the lines of DOSBox or VirtualBox or somesuch and be able to recreate the necessary environment to play 15, 20, even 30-year-old games. Last I checked (which was admittedly a long time ago, seeing as my ship-jump from iOS to Android was a few years ago), you have to jailbreak an iOS device in order to achieve similar functionality thanks to Apple's rather-draconian restrictions on such things. Apple's attitude toward iOS - move fast and break things - is in stark contrast to even OS X, where a lot of software made for OS X versions as old as 10.5 will still run relatively happily (though apparently Yosemite broke quite a few things). That said, there's a time and a place. On my servers, for example (which are typically running OpenBSD or some GNU/Linux distro), I'm at least somewhat-okay with backwards-compatibility breaking (within reason) if it means having better performance or security. In that context, I'm relying far less on closed-source software (if I'm using closed-source software at all, which is incredibly rare for me when it comes to servers), which means that most of the software I actually rely on will at the very least usually have community-supported patches up the wazoo to support those backwards-compatibility-breaking changes (like OpenBSD's switch to a 64-bit time_t, which basically just amounted to recompiling a bunch of stuff - most of which was already done by the ports tree maintainers when creating binary packages).
Comments (0)
No comments yet. Start the discussion.