EPISODE 48: The concept of saving documents so if they break you have a “saved version” to return to.
Genius. Got to get one of those new Apples. Pic via the Big E.
EPISODE 48: The concept of saving documents so if they break you have a “saved version” to return to.
Genius. Got to get one of those new Apples. Pic via the Big E.
Unbelievable how well-wtrietn and informative this was.
Integrated versioning and revision control is so old.
Why, every OS just builds that in at the API level and Apple’s the last to the party!
Wait?
You say that nobody else actually has built-in API-level versioning in their OS?
Yeah, funny that.
I don’t think anything can technically be described as funny once you’ve started talking about “API-level-versioning”.
I was lost at Integrated to be honest.
We’ve seen API-level versioning before in VMS, where it was one of the features most often turned off. Much better to handle this at the app / version control level where it can be customised by document type, and many do.
Oops, sorry, forgot where I was for a minute there. Wouldn’t.
*OUT OF MY DEPTH ALARM*
We can all use long words when needed.
Legacy serial integrity variance dereferencing. Multiplexed bidirectional array timeout. Replicated dynamic service inconsistency!
Some with more success than others, admittedly.
“Sphygmomanometer” is one of my favorites. And “clavicles” is always good for a chuckle.
Coccidiostat is my most recently learned long word.
I’m not counting Sphygmomanometer as I can’t be bothered to look it up.
“Load of bollocks” is a collective that springs to mind.
I am disappointed, you forgot to mention Apple invented fullscreen programs too. Whoa!
XHTML: These are some of the tags you can use: <a href=""> <b> <blockquote> <code> <em> <i> <strike> <strong>
Is that what all the cool kids will be wearing this season too?
Wow. Wish I could be as cool as apple.