3 ms·
Please be less patronising in the future; it's not a good look. In reality, of course, many people currently "sitting around typing" are doing plenty of useful
by matthewmacleod 7y ago
Please be less patronising in the future; it's not a good look. In reality, of course, many people currently "sitting around typing" are doing plenty of useful work using a variety of different tools.
There are various tradeoffs to be made when considering the benefits and costs of a strategy for long-term backwards compatibility. Microsoft was traditionally on the "it will continue to work until the heat death of the universe" end of the spectrum, and Apple on the "we will be dropping support soon" end. That is, Microsoft invests a bunch of effort into ensuring old software will continue to run on new platforms, whereas Apple prefers to drop support for various platform features (68k, PPC, 32-bit) with a few years of notice.
In some cases and for some users, backwards compatibility has a value that is worth the cost paid in development time, testing, and complexity. For others, it is not. I've been a Mac user since the G4 days, and I don't think I've ever really been in the situation where I thought "oh I need to run this old software but it's no longer supported" – that is, the feature has no value to me. And I'm pretty confident that the things I produce will continue to have value in the future.
TLDR – other people are different to you sometimes.
- deleted 7y ago[deleted]