The author might consider using Microsoft products because they are obsessive about providing backwards compatibility. That's one of the positive things about Microsoft products. The downside is that they have to deal with a lot of old baggage as a result. Apple, on the other hand is almost the opposite. They're obsessive about upgrading everyone and leaving the past behind. That's great because they're free to make…
“This presentation can’t be opened because it’s too old”
111–120 of 217 posts
Re: “This presentation can’t be opened because it’s too old”
#112Re: “This presentation can’t be opened because it’s too old”
#113A lot of people have absolutely no problem with proprietary software until it breaks. The problem is you never know when it will break, and what it'll take down with it. I'm not saying 'go full Stallman'. I'm just saying think that when ever you hand over your data to a private company if they consider it as important as you consider it.
Re: “This presentation can’t be opened because it’s too old”
#114A lot of people have absolutely no problem with proprietary software until it breaks. The problem is you never know when it will break, and what it'll take down with it. I'm not saying 'go full Stallman'. I'm just saying think that when ever you hand over your data to a private company if they consider it as important as you consider it.
Re: “This presentation can’t be opened because it’s too old”
#115The author might consider using Microsoft products because they are obsessive about providing backwards compatibility. That's one of the positive things about Microsoft products. The downside is that they have to deal with a lot of old baggage as a result. Apple, on the other hand is almost the opposite. They're obsessive about upgrading everyone and leaving the past behind. That's great because they're free to make…
The most important point here is that if you are aware of the problem and provide an incredibly lame dialog to deal with it, then you should have just provided the solution. Clearly Apple has all the necessary tools in their possession to fix this problem: they own the source to both Keynote '09 and the latest Keynote. Why not either 1) make a small conversion utility and provide a direct link to it in the dialog (st…
They leave the door open to losing customers to companies like Microsoft with these kinds of decisions. But that's the choice they made.
Re: “This presentation can’t be opened because it’s too old”
#116Earlier quoted context omitted.
Wouldn't it have been better to just stick a specialized piece of hardware/fpga to read directly from the crystal, buffer it, and pass it on? In fact that's what the timing equipment usually does for you. There's no reason to give up security when a few minor changes in architecture will give you performance, security and ease of maintenance and interconnectability.
Your acting like the read/write time to the hardware/FPGA is negligible which it isn't. When you access hardware on say a PCI bus (which you would in this scenario). Your call to the PCI bus does not take place WHEN you call for it to take place. You call the Kernel, which calls the scheduler, which calls the hardware manager, which calls the driver, which finally processes your request. Now your request is processed…
Re: “This presentation can’t be opened because it’s too old”
#117I think even MS is better than this at supporting old Office binary formats. Only PowerPoint has completely removed the support for pre-97 formats. With Word/Excel you can generally unblock support for older formats even if by default they will not open.
'even MS' MS is one of the best in supporting old formats. That's part of how and why the managed to keep their monopoly on the desktop. There's not many OSs out there where you can start a 20 year old software and it runs almost always perfectly. (Try that on Linux or OSX.)
On OS X that would certainly fail (even much software that's between 5-10 years old would fail) this test.
But Linux provides a very stable ABI.
20-year backwards compatibility might be stretching it for Linux, since it's only around 20 years old to begin with. But if you have (e.g.) a statically linked Debian binary from the late 1990s, I'd bet almost anything it would still work on your desktop today.
Re: “This presentation can’t be opened because it’s too old”
#118Earlier quoted context omitted.
Files are data. Data should be eternal. You should be able to convert a presentation you make today 30 years from now to a newer format. Making software not-backwards compatible is fine and normal but if files expire in a few years Apple is saying that the things you do on their computers are disposable.
The world isn't so black and white. Document serialization is a rocky landscape that is rife with compromise. You have to balance document open time, document save time, file size, backwards compatibility, forwards compatibility, recovery modes, interoperability, size in memory, parsing time, time to save to disk, proprietary embedded file formats, metadata support, and more. And those are just the development consid…
Is it really so difficult to just not break a feature that was present in the last version of the software?
Re: “This presentation can’t be opened because it’s too old”
#119A lot of people have absolutely no problem with proprietary software until it breaks. The problem is you never know when it will break, and what it'll take down with it. I'm not saying 'go full Stallman'. I'm just saying think that when ever you hand over your data to a private company if they consider it as important as you consider it.
To play devil's advocate, one could say the same for a lot of open source software: it's great until it breaks. Your claim implies that broken proprietary software is bad because you can't access the source code, while mine implies that broken open source software is bad because there might be no company or organization dedicated to providing support.
Re: “This presentation can’t be opened because it’s too old”
#120Earlier quoted context omitted.
s/proprietary// While I like non-proprietary software, there is nothing inherit that makes much of a difference for the lay person. As the complexity of the software goes up, so does the level of what is considered a 'lay person'. For any sufficiently complex software and non-pervasive problem - you're SOL in both cases. Standards help more than proprietary/non-proprietary. Lower complexity also helps more.
For example, if you had your own compiler which generated a.out output, then the Linux 1.2 switch to ELF would have broken the code in a similar backward incompatible way, despite there being no proprietary code involved. (Standards wouldn't have helped either.)
https://plus.google.com/115250422803614415116/posts/hMT5kW8L...
Specifically, Alan Cox's comment that he can still run an a.out rogue binary from 1992 on a 3.6 version of the Linux kernel. Linux 1.2 was released March 1995.