4 ms·
Newman is saying it’d be nice to have it both ways. I’m saying you can’t have it both ways. He’s definitely right — it would be nice. But I’m pretty sure I’m ri
by pavlov 15y ago
Newman is saying it’d be nice to have it both ways. I’m saying you can’t have it both ways. He’s definitely right — it would be nice. But I’m pretty sure I’m right, too — that it can’t be done.
Strange how this whole argument seems like a step-by-step repetition of "GUI vs. command-line", a quarter of a century ago.
On one side, we have the beautiful new Apple system with no backwards compatibility. On the other side, there's the "industry standard" provider who has announced plans to extend their existing system with a cool new interaction layer while retaining full compatibility. (In 1986, this role was played by IBM with OS/2, but the GUI software was Microsoft's.)
Gruber even mentions DOS drive letters as an ugly wart of compatibility. This same argument could have been made in support of the Mac back then...
These fundamentally aesthetic points seem pretty weak in face of the appeal of backwards compatibility. If Windows 8 can make the "convertible tablet" finally work, it will sell.
- lurch_mojoff 15y agoOne difference is that the command-line and DOS applications didn't require more CPU and memory resources. Another difference is that the mouse didn't remove the main input device for the command line - the keyboard. Yet another difference is that extending the command-line into GUI didn't coincide with a switch to an entirely different system architecture. The argument is not that personal computer OSes and mobile device OSes won't be converging down the road. Actually that's the big thing with Lion, isn't it. And I'm sure it will be a similar thing with iOS 5. The argument, though, is that they will never meld completely because it is impossible (or at the very least very, very unlikely) to have both full backwards compatibility and full and proper casual computer, or tablet if you will, experience.