Skip to main content

Apple iCloud: How vs What

Apple iCloud: How vs What | Technology |

A well written piece by, written by Jean-Louis Gassée.

Bit of background for those of you that don't remember:
Back in 1985 Steve Jobs was in a fight with John Sculley, Apple's then-CEO. (This was shortly after the Macintosh, Steve Jobs's baby, came to market.) At the end of this power struggle Sculley relieved Jobs of his duties as the head of the Macintosh Division, and Jobs sold all stock in Apple (save for 1 share) and left the company, eventually buying Pixar and starting NeXT computer.

Well, after Steve Jobs left, Sculley appointed Jean-Louis Gassée to head the Macintosh division. Just an interesting tidbit there.


There's a couple of tidbits that I thought were very good in this article, but namely the points that I've been struggling with a bit, so I'll outline those.

Google Docs -- Everything is stored in the cloud, accessible via the browser, and you can work on a single document with others, simultaneously. I love this approach, but only for the last part. The simultaneous part. It's the best group-work collaborative product there is. Sharepoint is plain awful, as so is the mailing of documents back and forth trying to get them right. Google Docs, right now, is the answer to that.

iCloud/Documents in the iCloud -- Apple views this differently. Instead of having a browser to access your documents that are "stored" in the cloud, they view the experience as having the documents stored locally, but also pushed up to the "iCloud" and then back down to all devices. That way keeping the documents on all your devices in "sync" all the time. (Apple doesn't use the word sync.) The only thing that this defeats is the collaborative simultaneous work-part.

Apple has had around for awhile, in beta, and I've used it a couple times with my co-workers. Upload a document, and then the people who have access to the document can download it, view it, make comments on it, share it, etc. But they can't EDIT it.

It's the only foothold I think Google has right. Otherwise, I like Apple's approach. I hate editing documents in the browser. But it works.

We'll see.

Please leave comments below.


Popular posts from this blog

Offset, Depth, Distance, and Within

Without going off the deep-end here and discussing every single Snort rule keyword, I just wanted to touch on a few modifiers that people sometimes misunderstand.  They aren't difficult, and hopefully after this explanation and a few examples, I can clear some of the air around these five modifiers.

The five modifiers that I am talking about are
OffsetDepthDistanceWithinnocaseThese five modifiers are not keywords of themselves, but rather they apply as modifiers to another keyword.  That keyword is "content". The content keyword is one of the easiest pieces of the Snort rules language as all it does is look for a particular string.  So for instance if I wanted to look for the word "joel" within a packet.  A simple:
content:"joel";Would allow me to do that.  The interesting part comes into play when you want to specify where inside of a particular packet you want the string "joel" to be looked for.  If you are running just a plain content ma…

Writing Snort Rules Correctly

Let me start off by saying I'm not bashing the writer of this article, and I'm trying not to be super critical.  I don't want to discourage this person from writing articles about Snort rules.  It's great when people in the Snort community step up and explain some simple things out there.  There are mistakes, it comes with the territory.  If you choose to be one of the people that tries to write Snort rules, you also choose to be someone who wants to learn how to do it better.  That's why I write this blog post, not to bash the writer, but to teach.

I noticed this post today over at the "Tao of Signature Writing" blog, and to be honest I glanced over most of it figuring it was a rehash of things I've already read or things that have already been written from countless people about "Here's how you write Snort rules!".  I scrolled down quickly skimming, not reading at all really, and noticed this part:
Now, let us look at the second questio…

Safari 5.1.4 now available

Safari 5.1.4 now available, fixes issues and improves performance | TUAW - The Unofficial Apple Weblog:

Improve JavaScript performanceImprove responsiveness when typing into the search field after changing network configurations or with an intermittent network connectionAddress an issue that could cause webpages to flash white when switching between Safari windowsAddress issues that prevented printing U.S. Postal Service shipping labels and embedded PDFsPreserve links in PDFs saved from webpagesFix an issue that could make Flash content appear incomplete after using gesture zoomingFix an issue that could cause the screen to dim while watching HTML5 videoImprove stability, compatibility and startup time when using extensionsAllow cookies set during regular browsing to be available after using Private BrowsingFix an issue that could cause some data to be left behind after pressing the "Remove All Website Data" button