tonza wrote:
What, so now you want me to write something?
Um...usually that's how an exchange of ideas works. One person posts something...the next reacts and posts something in reply to the ideas advanced...the conversation continues based on an exchange of those ideas.
Your method, unfortunately, is to ignore the majority of ideas others post and just carry on with your own agenda, as if those ideas had never been put forth. That's fine, but it leaves the impression that you're unable to withstand challenges to your own ideas, so you just ignore them and hope no one will notice.
We notice.
OK, look. What I write here has only been met with insults and a poor effort to engage in an understanding...
Apparently your definition of "understanding" is "only my ideas matter...yours are so insignificant I won't even acknowledge them."
IMHO, any "insults" you've received here have been earned.
...obviously, your priorities are to ensure that your system doesn't change so as not to break the workflows that you have been using, and I can understand that very well.
As I've explained many times (as have others), my only priority is to provide for the option to continue using a system that has worked very, very well for Mac users over the last 27+ years. The system can "change" all it wants to, as long as we're given that option.
You have yet to demonstrate that a) this is a bad idea; and b) that it can't be done.
There is simply no reason this has to be an "either/or" paradigm.
For me to explain to you what all this change is about is going to take something like a thick text book in order to explain the concepts behind Auto Save and Resume. You need to understand that the changes that Apple have introduced in Lion is not just a change to the name of one solitary command in the "File" menu... it's a whole new architecture in managing user data. If Core Data means anything to you beyond its name, then you can understand where I'm coming from.
Granted, Save As is not going to work with every existing application on the market today, because to take advantage of Auto Save and Resume, an application has to be designed for it. Existing applications can't just use the new APIs and expect to work.
And there's also a need to change the expectations of how users use the new data management models in OS X Lion, just like Grand Central Dispatch and 64-bit computing changed the expectations of how users could (not) run older applications that needed Rosetta or Java or whatever legacy technologies were available prior. I just had a head-start on you: I own and use a Newton, have used OpenDoc before that, and used a Lisa before that. So I'm well familiar with what Lion and iOS have introduced.
These paragraphs have been answered by Kurt. I refer you to his statements...although it's likely you'll just ignore them too.
So I have decided not to say anything more about it.
Translation: I'm getting out before I embarrass myself any further. This way, I can continue to ignore statements I realize I have no answer for.
You've obviously made up your minds, and no amount of explaining is going to make you think any differently.
It might have helped had your "explaining" had anything whatsoever to do with the issues at hand.
Meanwhile, the irony of the last three words of your sentence above is delicious.