3 ms·

note: Your questions are in a rhetorical/sarcastic tone; be certain I'm answering only for the benefit of others. > So should Apple have kept the silicon requi

by vaxman 7y ago

note: Your questions are in a rhetorical/sarcastic tone; be certain I'm answering only for the benefit of others. > So should Apple have kept the silicon required to support 32 bit apps in their ARM chips forever? Yeah, I think so. One would think that Apple would have learned from DEC's mistake in this regard, but such history lessons have been lost with the age discrimination. They should not have made the decision to virtually force consumers that are busy paying rent/mortgages, car payments and putting their kids through school to update software and buy upgraded hardware that breaks apps that they, as consumers, rely upon for home appliances, automotive and online services, especially when those users have gone into debt for upwards of a thousand dollars per device. Someday there will be a transition to radically different devices (projector/visor/voice or whatever) and that would be the time to not support 32-bit. Anyway, they made the decision and there will be all kinds of consequences (with a one trillion market cap, I'm sure they can handle it but what a horrible drain on all of creation for everyone to deal with). > How long should they keep backwards compatibility in watchOS - which is very resource constrained? That's an esoteric cosmetic platform with almost no relevant third-party apps (just second screen notifications) yet, so no need to worry about compatibility. > Going back further - should they never have dropped 68K support? PPC support from MacOS? Of course they should never have dropped support for 68K or PPC, even if it just meant shipping a System 7/macOS 9.04 in an emulator in every new Mac sold, forever. If they wanted to release a computer not called Mac, then that's another story but they clearly wanted to kill off the embarrassment Jobs created back when he was still learning what happens when you consider formal-training/experience to be a handicap. > Even Microsoft dropped Windows' success had almost nothing to do with such technical decisions so it's not real relevant though the compatibility between releases of Windows and Office was remarkable because Microsoft did learn from the lessons of DEC (because it actually had hired much of DEC's team heh).

scarface74 7y ago
Yeah, I think so. One would think that Apple would have learned from DEC's mistake in this regard, Because what killed DEC is leaving backwards compatibility not cheap x86 based servers and people moving to Unix instead of DEC VAX/VMS. No I am not a youngin who doesn’t know about mainframes. My first job out of college was programming VAX/VMS and Stratus VOS mainframes in C and FORTRAN. Anyway, they made the decision and there will be all kinds of consequences (with a one trillion market cap, I'm sure they can handle it but what a horrible drain on all of creation for everyone to deal with). You mean the same decision that they made transitioning from 65C02 Apple //s, to 68K Macs, to PPC Macs, to Intel Macs? That's an esoteric cosmetic platform with almost no relevant third-party apps (just second screen notifications) yet, so no need to worry about compatibility. Yes there are native apps for WatchOS. Of course they should never have dropped support for 68K or PPC, even if it just meant shipping a System 7/macOS 9.04 in an emulator in every new Mac sold, forever. If they wanted to release a computer not called Mac, then that's another story but they clearly wanted to kill off the embarrassment Jobs created back when he was still learning what happens when you consider formal-training/experience to be a handicap. Every piece of code has maintenance and security concerns. The last thing you want is an old security vulnerability showing up because of a bug in QuickDraw GX, OpenDoc and the Publish and Subscribe system A modern low end iPad -the 10.2 inch $329 iPad has 3GB of RAM, no swap and a lower end processor than most modern laptops, yet it runs faster than low end Surface laptops with more RAM and faster processors and has longer battery life. Windows and Intel are albatrosses for mobile devices. As far as what MS “learned”, Microsoft completely missed mobile and every other trend in the last 20 years because they were concerned with backwards compatibility. Seeing where Apple was when Jobs came back and where they are now and comparing them to MS in terms of revenue and profit, can you really say that Apple made a bad decision? On the other hand, where are all of the Apple’s former competitors in the PC market now? As far as “formal training”, how did that help MS during the Ballmer era? Or heck how did it help Apple during the Sculley/Amelio era?

by vaxman 7y ago

scarface74 7y ago

Yeah, I think so. One would think that Apple would have learned from DEC's mistake in this regard, Because what killed DEC is leaving backwards compatibility not cheap x86 based servers and people moving to Unix instead of DEC VAX/VMS. No I am not a youngin who doesn’t know about mainframes. My first job out of college was programming VAX/VMS and Stratus VOS mainframes in C and FORTRAN. Anyway, they made the decision and there will be all kinds of consequences (with a one trillion market cap, I'm sure they can handle it but what a horrible drain on all of creation for everyone to deal with). You mean the same decision that they made transitioning from 65C02 Apple //s, to 68K Macs, to PPC Macs, to Intel Macs? That's an esoteric cosmetic platform with almost no relevant third-party apps (just second screen notifications) yet, so no need to worry about compatibility. Yes there are native apps for WatchOS. Of course they should never have dropped support for 68K or PPC, even if it just meant shipping a System 7/macOS 9.04 in an emulator in every new Mac sold, forever. If they wanted to release a computer not called Mac, then that's another story but they clearly wanted to kill off the embarrassment Jobs created back when he was still learning what happens when you consider formal-training/experience to be a handicap. Every piece of code has maintenance and security concerns. The last thing you want is an old security vulnerability showing up because of a bug in QuickDraw GX, OpenDoc and the Publish and Subscribe system A modern low end iPad -the 10.2 inch $329 iPad has 3GB of RAM, no swap and a lower end processor than most modern laptops, yet it runs faster than low end Surface laptops with more RAM and faster processors and has longer battery life. Windows and Intel are albatrosses for mobile devices. As far as what MS “learned”, Microsoft completely missed mobile and every other trend in the last 20 years because they were concerned with backwards compatibility. Seeing where Apple was when Jobs came back and where they are now and comparing them to MS in terms of revenue and profit, can you really say that Apple made a bad decision? On the other hand, where are all of the Apple’s former competitors in the PC market now? As far as “formal training”, how did that help MS during the Ballmer era? Or heck how did it help Apple during the Sculley/Amelio era?