This Day in Apple History offers a
This Day in Apple History offers a daily story about what happened on a given day in Apple’s history.
This site is made possible by member support. β€οΈ
Big thanks to Arcustech for hosting the site and offering amazing tech support.
When you buy through links on kottke.org, I may earn an affiliate commission. Thanks for supporting the site!
kottke.org. home of fine hypertext products since 1998.
This Day in Apple History offers a daily story about what happened on a given day in Apple’s history.
A list of iPhoto 5 annoyances. I wish iPhoto were as finished a product as iTunes is. (via df?)
Me: Yeah, it’s like the plural of attorney general is attorneys general.
J: Attorneys general? I thought there was only one attorney general.
Me: Well, one for each state, and if they all go to a meeting or something…
M: Like, “all the attorneys general get together for the annual attorney general-a-thon.”
Me: Shouldn’t that be attorney-a-thon general?
Related: Engadget checked with Apple PR to see if it’s iPod shuffles or iPods shuffle. They said the former…I think it should be the latter.
Much to my irritation (and that of others), many hotels charge for broadband internet access and the standard practice (at least on this trip) seems to be to charge per computer. So if both you and your traveling companion want to connect to the internet (via ethernet cable one at a time or both via wireless), you’re screwed. Luckily, we brought along an Airport Express; it’s small and fits easily in a suitcase. You hook that up to the ethernet cable and then you can both connect to that wireless network.
(With the Powerbook, you can also hook it up to the ethernet cable and then share your connection via the Airport. But the cables are typically short, so one of you loses that lounging-in-bed web surfing experience.)
Once again, the pornographers are on the cutting edge of technology. Feast your eyes on the Web 2.0ness of mydirtyipod, which offers naughty iPod-ready videos and podcasts. I’m gonna spell this one out for you: NOT SAFE FOR WORK.
“This guide demonstrates using SSH tunnels and VNC screen-sharing software to use your Mac from any PC over the Internet. It’s fast, secure, cross-platform, and can be done entirely with open source software.” (thx tag)
Sony is using DRM on audio CDs (no copying the CD, no iTunes, etc.) to pressure Apple to open up iTunes and the iPod to other formats. This story is so absurd on so many levels that I don’t even know where to begin.
Apple announces Aperture, professional-grade software for managing and manipulating photos. A little bit o’ iPhoto mixed with Photoshop, it looks like. (Also, new Powerbooks…higher res, better battery life.)
An excellent John Gruber piece on the life cycle of the independent Mac developer, using for an example Brent and Sheila Simmons, whose company Ranchero was recently sold to NewsGator.
Jason @ 37signals noticed a great feature of the new iMac with built-in iSight. The screen is the flash for the camera so just before you take a photo, the screen flashes a bright white. Fantastic.
Well, lookie lookie. If you take a peek at the bottom of the Apple movie trailers page, they’ve added a link to an RSS file of the newest movie trailers. O’ happy day. (thx John)
Update: Dave says: “I was hoping to see permalinks to a reviews page for the movie, and an enclosure containing the trailer itself.” Me too, but baby steps, I guess.
John Gruber has a great bullet-point roundup of the Apple announcements today…mostly stuff that you won’t hear about in the tech press. (If you’re living in a shack, Apple announced video iPods, new iTunes, downloadable TV programs, new iMacs, etc. today.)
Profile of Google’s Marissa Mayer, Google’s answer to Apple’s Jonathan Ive. She grew up about 100 miles from me in northern WI.
Interesting rumination on the possibility of flash memory-based computers. “In two years I have a feeling that Jobs will announce an Intel-flash iBook that will be the thinest laptop ever made boasting the best battery life of any current machine”.
In preparation for the AIGA design conference[1], I’m looking over the session descriptions and speaker list. The theme for this year is “Design”, which seems a little broad but somehow appropriate given how much design has been taken up by the press (especially the business and tech press) recently as something Important and the design profession may be in need of a little wagon circling to figure out how to effectively explain design to someone who is all fired up about incorporating it into their business process because they read a blurb in Fast Company about Jonathan Ive and the iPod.
My knowledge of and involvement with the AIGA up to this point has been fairly minimal, which either makes me the ideal person (fresh eyes!) or a horrible choice (head up ass!) to cover their design conference. I’m particularly interested in learning how they’ve incorporated the fast-changing disciplines of Web and digital design into the mix. When I was working in Minneapolis as a Web designer in the late 90s, my company got me an AIGA membership, but I never used it because although they were trying to be more relevant to those of us working on the Web, my perception is that the AIGA was still largely a graphic design organization and I was finding more of what I was looking for on Web design sites like A List Apart. Now that the Web design profession has matured (and Web design practitioners along with it), it seems to fit better with where the AIGA is going (and vice versa). After all, design is design, no matter what word you stick in front of it.
So, back to the speakers list, I’m looking forward to hearing from Michael Bierut, Lella and Massimo Vignelli, Steven Heller, Matthew Carter, John Maeda, Peter Merholz and Jesse James Garrett from Adaptive Path, Ze Frank, Stefan Sagmeister, Steff Geissbuhler, Caterina Fake, and Milton Glaser (but no Malcolm Gladwell or Errol Morris, both of whom I swear were on earlier speaker lists), some of whom you may recognize from past mentions on kottke.org. They’ve also added some sessions in response to Hurricane Katrina on design, safety, risk, and disaster management, which is an excellent use of the opportunity of having a bunch of designers in the same place.
If you want to follow along with the complete conference coverage here on kottke.org, here’s the AIGA 2005 page. As I mentioned previously, I’ll be opening up comments on most posts (incl. this one), but will be active in gardening off-topic and trolling comments.
[1] I just realized all these URLs are going to break when the next conference rolls around in two years or so, which is disappointing. Would be nice to have something like http://designconference.aiga.org/2005 that would permanently point to this year’s festivities. Bloggers like permanent links (well, this one does anyway).
How the iPod nano came to be. Lots of Jobs and Apple haters out there, but you have to admire the shooting from the hip that’s going on here…too many American companies minimize their risk so much that the possible reward dries up almost completely.
Profile of designer/illustrator/photographer Michael Elins and how he uses Macs to get his work done. “It’s hard for someone like me to talk about technology, because the Mac has gotten to the point where it’s a nonissue. Itβs so good and so fluid, so fast and so freaking reliable that it becomes something I really take for granted.”
The iTunes 5 Announcement From the Perspective of an Anthropomorphized Brushed Metal User Interface Theme. If you’re a Mac nerd, you’ll love this because it’s pretty damn funny and if you’re not, you probably won’t get it.
A couple of recent OS X interface ruminations: rethinking the Finder and Spotlight revisited. Some good ideas in both of these, particularly the Spotlight one (I find Spotlight disorienting at times).
Apple introduces the iPod nano, which, wow, it’s like a baby iPod. So cute.
Robert Cringely: Google may have peaked (“What if search and PageRank and AdSense are Google’s corporate apex?”) and Microsoft may have more to worry about from Apple if they start distributing older versions of OSX (the Intel version) for free on iPods.
Justin’s looking for the largest inbox smoothly handled by Mail.app…the current high is 26,700 messages. Mine only has around 100 because I filter most messages into a variety of folders. Update: he’s up to 43,000 283,686! (That’s gotta be on a G5 with a ton of RAM…my Powerbook would melt under that kind of weight.)
Here’s how to connect to Google’s IM network with iChat or Adium. The audio works with iChat as well. Not as good as a Google Talk client for OS X, but I guess it’ll have to do.
Before we get going, here are some alternate titles for this post, just to give you an idea of what I’m trying to get at before I actually, you know, get at it:
Now that your hyperbole meter has pegged a few times, hopefully the rest of this will seem tame in comparison. (And apologies for the length…I got rolling and, oops, 2500 words. But many of them are small so…)
Way back in October 2004, this idea of how the Web as a platform might play out popped into my head, and I’ve been trying to motivate myself into writing it down ever since. Two recent events, Yahoo’s purchase of Konfabulator and Google’s release of a new beta version of Google Desktop have finally spurred me into action. But back to October. At the Web 2.0 conference, Stewart pulled me aside and said something like, “I think I know what Google is doing with Google Browser.” From a subsequent post on his site:
I’ve had this post about Adam Bosworth, Alchemy and the Google browser sitting around for months now and it is driving me crazy, because I want all the credit for guessing this before it happens. So, for the record, if Google is making a browser, and if it is going to be successful, it will be because there is a sophisticated local caching framework included, and Google will provide the reference apps (replying to emails on Gmail or posting messages to Google groups while on the plane).
At the time, Adam Bosworth had been recently hired by Google for purposes unknown. In a blog post several months before he was hired, Bosworth mused about a “new browser”:
In this entry, I’m going to discuss how I imagine a mobilized or web services browser handles changes and service requests when it isn’t connected. This is really where the peddle hits the metal. If you just read data and never ever alter it or invoke related services (such as approving an expense report or booking a restaurant) then perhaps you might not need a new browser. Perhaps just caching pages offline would be sufficient if one added some metadata about what to cache. Jean Paoli has pointed out to me that this would be even more likely if rather than authoring your site using HTML, you authored it as XML “pages” laid out by the included XSLT stylesheets used to render it because then you could even use the browser to sort/filter the information offline. A very long time ago when I was still at Microsoft (1997) we built such a demo using XSLT and tricky use of Javascript to let the user do local client side sorting and filtering. But if you start actually trying to update trip reports, approve requests, reserve rooms, buy stocks, and so on, then you have Forms of some sort, running offline, at least some of the time, and code has to handle the inputs to the “Forms” and you have to think through how they are handled.
A couple weeks later, Google introduced the first iteration of their Desktop Search. To me, the least interesting thing about GDS was the search mechanism. Google finally had an application that installed on the desktop and, even better, it was a little Web server that could insert data from your local machine into pages you were browsing on google.com. That was a new experience: using a plain old Web browser to run applications locally and on the Web at the same time.
So this is my best guess as to how an “operating system” based on the Web (which I will refer to as “WebOS”) will work. There are three main parts to the system:
That’s it. Aside from the browser and the Web server, applications will be written for the WebOS and won’t be specific to Windows, OS X, or Linux. This is also completely feasible, I think, for organizations like Google, Yahoo, Apple, Microsoft, or the Mozilla Foundation to make happen (more on this below).
Compared to “standalone” Web apps and desktop apps, applications developed for this hypothetical platform have some powerful advantages. Because they run in a Web browser, these applications are cross platform (assuming that whoever develops such a system develops the local Web server part of it for Windows, OS X, Linux, your mobile phone, etc.), just like Web apps such as Gmail, Basecamp, and Salesforce.com. You don’t need to be on a specific machine with a specific OS…you just need a browser + local Web server to access your favorite data and apps.
For application developers, the main advantage is that instead of writing two or more programs for multiple platforms (one for the Web, one for Windows, etc.), they can write one app that will run on any machine with the WebOS using the same code base. Bloglines and NetNewsWire both do about the same thing and have radically different codebases (Bloglines uses HTML/JavaScript + some sort of backend programming/scripting language while NNW is a Cocoa app only for OS X), but a version of Bloglines developed for the above platform could utilize a single codebase.
You also get the advantages of locally run applications. You can use them when you’re not connected to the Internet. There could be an icon in the Dock that fires up Gmail in your favorite browser. For applications using larger files like images, video, and audio, those files could be stored and manipulated locally instead of waiting for transfer over the Internet.
There are also disadvantages to WebOS applications, not the least of which[1] is that HTTP+JavaScript+XHTML+CSS+Flash is not as robust in providing functionality and user interaction as true desktop applications written in Cocoa or Visual Basic. But as Paul Graham points out, Web applications may be good enough[2]:
One thing that might deter you from writing Web-based applications is the lameness of Web pages as a UI. That is a problem, I admit. There were a few things we would have really liked to add to HTML and HTTP. What matters, though, is that Web pages are just good enough.
Web pages weren’t designed to be a UI for applications, but they’re just good enough. And for a significant number of users, software that you can use from any browser will be enough of a win in itself to outweigh any awkwardness in the UI. Maybe you can’t write the best-looking spreadsheet using HTML, but you can write a spreadsheet that several people can use simultaneously from different locations without special client software, or that can incorporate live data feeds, or that can page you when certain conditions are triggered. More importantly, you can write new kinds of applications that don’t even have names yet.
And how about these new kinds of applications? Here’s how I would envision a few apps working on the WebOS:
I’m looking at the rest of the most commonly used apps on my Powerbook and there’s not too many of them that absolutely need to be standalone desktop applications. Text editor, IM[3], Word, Excel, FTP, iCal, address book…I could imagine versions of these running in a browser.
So who’s going to build these WebOS applications? Hopefully anyone with XHTML/JavaScript/CSS skills, but that depends on how open the platform is. And that depends on whose platform it is. Right now, there are five organizations who are or could be moving in this direction:
So yeah, that’s the idea of the WebOS (as I see it developing) in a gigantic nutshell. The reality of it will probably be a lot messier and take a lot longer than most would like. If someone ends up doing it, it will probably not be as open as it could be and there will likely be competing Web platforms just as there are now competing search engines, portals, widget applications (Konfabulator, Dashboard, Google Desktop Sidebar), etc., but hopefully not. There’s lots more to discuss, but I’m going to stop here before this post gets even more ridiculously long. My thanks if you even made this far.
[1] Actually, the biggest potential problems with all this are the massive security concerns (a Web browser that has access to data on your local hard drive?!!!??) and managing user expectations (desktop/web app hybrids will likely be very confusing for a lot of users). Significant worries to be sure, but I believe the advantages will motivate the folks developing the platform and the applications to work through these concerns.
[2] For more discussion of Web applications, check out Adam Rifkin’s post on Weblications.
[3] Rumor has it that Google is releasing an IM client soon (more here). I’ll be pretty surprised if it’s not significantly Web-based. As Hotmail proved for email, there’s no reason that IM has to happen in a desktop app (although the alerting is problematic).
[4] Maybe Google thinks they can’t compete with Apple’s current offerings (Spotlight, Dashboard, Safari, iPhoto) on their own platform, but that’s not a good way of thinking about it. Support as many people as you can on as many different architectures as you can, that’s the advantage of a Web-based OS. Microsoft certainly hasn’t thought of Apple as a serious competitor in the OS space for a long time…until Web applications started coming of age recently, Microsoft’s sole competitor has been Microsoft.
Subway maps that you can put on your iPod. Currently available: DC, NYC, Boston, and Hong Kong. Good one for the 50 Fun Things To Do With Your iPod list. (via coolhunting)
Playstation 3 to support OS X?. “The operating system has also yet to be clarified. The integrated Cell processor will be able to support a variety of operating systems (such as Linux or Apple’s Tiger).”
Cory Doctorow to Apple Computer: put Trusted Computing in your kernel and I’m done as your customer. This doesn’t look promising. You’ve got a good thing going here, Apple…don’t fuck it up.
Announcing the world’s smallest mp3 player: the iPod Flea. Love the Flea collar.
Some iPhoto 5 tips and techniques for managing your digital photos.
Stay Connected