I should point out that, although Lanai was formed millions of years ago by a volcano, there aren't actually any active volcanoes on that island. The only active ones are on the Big Island (also known as Hawaii).
There's always someone coming in with facts that ruins the wonderful ideas. I'm going to pretend it is an active volcano and Larry Ellison is actually Hank Scorpio.
> Even dragging out the USB cord to plug my phone into my MacBook Pro doesn’t yield a simple solution. Open iTunes, iPhoto, etc. – haven’t found the answer.
There's an app called Image Capture, installed on every Mac, that lets you easily download certain photos and videos from your iPhone (or any other camera). It simply presents a list of media on your device, which you can save in any location you want. There's no organizational aspect, unlike iPhoto. Image Capture doesn't help with the uploading/sharing part, of course, but it's much more streamlined way of directly downloading photos versus iPhoto.
> It simply presents a list of media on your device, which you can save in any location you want. There's no organizational aspect, unlike iPhoto. Image Capture doesn't help with the uploading/sharing part, of course, but it's much more streamlined way of directly downloading photos versus iPhoto.
iPhoto's "organizational" aspect, as far as mandatory core goes, does not go any further than an optional "event name" field (it'll just use the import date if no event name is specified). And it does provide sharing options.
Image Capture is useful if you want to download stuff to the filesystem or delete pictures without importing them (iPhoto can't do that), but it definitely isn't simpler than iPhoto to import media: on iPhoto you select your pictures, click "import selected" (or just import all if you don't want to bother) and when done select "keep imported" or "remove imported", on Image Capture you select your filesystem destination, select your pictures, click "import" (or just import all if you don't want to bother) and when done you manually remove the file from the device.
> it's much more streamlined way of directly downloading photos versus iPhoto.
Only if your end goal is to have the pictures in an accessible place on your filesystem in their raw form.
I'm particularly interested – if anyone has experience using Ember – about the concerns raised about Ember's performance with large amounts of data and "hairy custom view situations," as borismus puts it. Is Ember actually going to be slow when dealing with large data sets?
There are some pretty legitimate concerns with Ember and large data sets right now as the treatment of those datasets tends to be fairly naive and linear. There are several people, myself included, who are working on ways to address that problem--but modifying a large collection, at the moment, can trigger the entire collection to re-render which can be extremely expensive.
FWIW, I'm not an expert on Ember.js or Backbone; just someone trying his hand at hacking the Ember.js code to work more effectively with collections (since some of the use cases I have would be impossible using the current methods of bindings and collections).
It really depends on your environment and the complexity of the rendering tied to your collection. For example, on a fast desktop-class system with a collection that renders one element with 1 property, you can probably have hundreds (or maybe even thousands) of items in the collection before you start to notice slowdowns when the collections update. Working on lower-end and mobile platforms, those numbers change. Similarly, if you rendering is complex, it will take more time as well. All that said, there's really no "magic number"
There are definite workarounds such as setting up paging--but the simple approach of using Ember.js bindings to bind a collection to a template will fall to pieces as that collection grows.
Well, I can tell you about SproutCore developer's experiences with Ember's views: they're ripping them out of their apps.
About 10 months ago, Strobe was trumpeting the "Ember" model for views (auto-updating templates, heavy nesting, bindings everywhere) and a lot of SproutCore developers began to use it.
The bloom is definitely off of that rose. At the latest user group meeting three weeks ago, many developers spoke up about having to remove all of their template view code because the performance was absolutely terrible.
At this point, "Ember-style" template views have been relegated to a separate opt-in library, are only being recommend for lightweight read-only data, and the recommendation for developers to use them is being removed from SproutCore's documentation.
This reminds moe of Joe Davis' Telescopic Text: http://www.telescopictext.com/. Assuming you see this on a desktop computer, it's exactly the opposite of Frankie's responsive text: instead of gradually reducing the amount of information, it gradually increases it.
Not only would it be more convenient for you, to focus on bits of the story you're actually interested in, the newspaper could collect analytics on what parts of the story you're interested in, and suggest further articles, and highly-targeted ads, based on that.
Imagine you see an article about Christopher Hitchens accusing Henry Kissinger of war crimes, and Kissinger is wearing a smart suit, and you dive in to find out more about his couturier. The click-through rates on high-end clothing ads would be vastly more.
Though, to take the opposite tack: would this encourage newspapers to turn into something like mesothelioma blogspam? Writing about something, only because the ads associated with it are profitable, instead of because it's a Fact Worth Knowing?
The OP, written by Inkling's CEO, also says: "I also previewed Inkling for Web, which will make all of Inkling’s great interactive content available in any web browser."
I wonder what this could mean for using Google+ in the classroom – perhaps teachers could post links in a circle exclusively for the students in their class, and allow students to comment and discuss those links. Also, on a hangout, students could more easily collaborate on group projects, especially if they use Google Docs.
That would explain why my Google search wasn't bearing fruit :)
Edit: the video has the quote I was thinking of, but what I read was an article. From the video (Jobs talking):
> I asked him if he would come up with a few options. And he said, ‘No, I will solve your problem for you, and you will pay me. And you don’t have to use the solution — if you want options, go talk to other people. But I’ll solve your problem for you the best way I know how, and you use it or not, that’s up to you — you’re the client — but you pay me.’
http://en.wikipedia.org/wiki/Evolution_of_Hawaiian_volcanoes