• Centibeats
• Microfortnights
• Microweeks
• Nanocenturies
• “The velocity of an unladen swallow”
• Planck times
• Shakes of a lamb’s tail
• Warp (Star Trek, of course)
• Centons (Battlestar Galactica)
• Parsecs (a unit of time in Star Wars Episode IV )
• Jiffies
• Skidoo (23.00 skidoo, to be precise)
• Gigawatts (pretty hard to explain how that’s a unit of time or velocity)
• Epochs (one precise figure was 1.25e-15 epochs)
• Hertz
• Femtogalactic years

I haven’t tried to check or estimate the conversion factors used.

Related links

• 2010 April Fool’s Day highlights
• My recent roundup of past years’ April Fool’s highlights
• A companion roundup of other, even funnier pranks
• My alternative to pranks: April No-Fooling Day
• Google Operating System with more on Google’s 2010 April Fool’s jokes.

• In a charming blog post, Google annoucned the new Android Translate For Animals feature.
• Reddit has apparently made every user an administrator, throwing the whole site –or at least the Reddit hot stories list — into chaos.
• A video depicts icons falling off of an iPhone onto a table.
• Firetoys, Ltd., whoever they are, are promoting a Back To The Future style hoverboard. I want one!

Edit: And more being added as I find them:

• Supernatural Season 6
• A crucial computer gaming accessory

Related links

• My recent roundup of past years’ April Fool’s highlights
• A companion roundup of other, even funnier pranks
• My alternative to pranks: April No-Fooling Day

This idea is not, to put it mildly, new. I first saw the definition

Recursion: See recursion

in the glossary to Intellicorp’s KEE documentation, in 1984 or so. And I’d guess the joke is actually a lot older than that.

For another variation of the same idea, see this link.

Edit: For yet more recursive humor, see this picture of Wil Wheaton.

• Open source
• Targeted to appear in netbooks in the second half of 2010
• Google Chrome browser + new windowing system + Linux kernel
• Minimal user interface
• Data stored or at least backed up in the cloud, and hence available on any computer
• Hardware compatibility hassles allegedly eliminated
• Ditto for software update hassles
• Ditto for security problems
• Apps apparently assumed to run inside the browser. (Not clear if this is required or just recommended.)

Obviously, Google Chrome OS is a direct attack on Microsoft — even more so than Google Wave, which I’ve predicted will “play merry hell with Microsoft Outlook, Microsoft Word, Microsoft Exchange, Microsoft SharePoint, and more,” or for that matter than Google Mail and the rest of Google Apps. Taken together, Google’s initiatives suggest that an all-out Google-Microsoft war is coming, in a conflict that many people have been expecting — and analyzing — for years.

So how will this all shake out? Well, let’s start with some basic points:

• Google Chrome OS Release 1 is expected over a year from now, and then only on a limited subset of PCs, namely netbooks.
• Google Chrome OS Release 1 is supposed to have great performance and be bullet-proof. Hmm …
• Google is evidently assuming that the apps people want to run will either be browser-based, or else be new ones written for Chrome OS. Hmm …
• Google is signaling that Chrome OS will be very limited in features. That makes sense for Release 1 — but what will be missing?
• Consumers have proven their willingness to buy non-Microsoft computers, especially Apple ones, specifically in the Mac and iPhone/iTouch product lines.
• A lot of people would have compatibility issues replacing Microsoft Excel or PowerPoint with partially-compatible alternatives. I’m not so sure about Microsoft Word, however. Other than those three, Outlook, and the Windows family itself, I’m not aware of any Microsoft client products that have much lock-in. (Well, maybe Xbox, but that’s not in the main stack.)
• Open source software often gets most of its community support in a couple of areas, namely compatibilities and language translation. Google probably doesn’t need the help in languages, but letting other people fix Chrome OS compatibility issues whose importance it didn’t recognize is potentially valuable.
• Google probably won’t make any direct revenue from Chrome OS. So how much will it invest in the project?
• Notwithstanding Danny Sullivan’s concern, there isn’t much of an antitrust issue here. Google’s search can’t easily be used to favor Chrome, Chrome OS, or Google Apps. And the other way around — e.g., using Chrome OS to favor search — Google clearly isn’t a monopolist.

So while Google may kill Microsoft’s client business some day, it clearly won’t happen for quite a while, Techcrunch’s excitement notwithstanding. We’re talking a multi-year effort before there’s any realistic chance of Microsoft being toppled. On the other hand, it’s hard to think of major software compatibility issues that won’t quickly be addressed, except Microsoft’s own product and, probably, MMO games — assuming, of course, Chrome OS gets enough initial traction for anybody to care. So intermediate- and long-term, Microsoft’s PC business is very vulnerable indeed.

The bulk of Google’s announcement follows (emphasis added):

Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. Because we’re already talking to partners about the project, and we’ll soon be working with the open source community, we wanted to share our vision now so everyone understands what we are trying to achieve.

Speed, simplicity and security are the key aspects of Google Chrome OS. We’re designing the OS to be fast and lightweight, to start up and get you onto the web in a few seconds. The user interface is minimal to stay out of your way, and most of the user experience takes place on the web. And as we did for the Google Chrome browser, we are going back to the basics and completely redesigning the underlying security architecture of the OS so that users don’t have to deal with viruses, malware and security updates. It should just work.

Google Chrome OS will run on both x86 as well as ARM chips and we are working with multiple OEMs to bring a number of netbooks to market next year. The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel. For application developers, the web is the platform. All web-based applications will automatically work and new applications can be written using your favorite web technologies. And of course, these apps will run not only on Google Chrome OS, but on any standards-based browser on Windows, Mac and Linux thereby giving developers the largest user base of any platform.

Google Chrome OS is a new project, separate from Android. Android was designed from the beginning to work across a variety of devices from phones to set-top boxes to netbooks. Google Chrome OS is being created for people who spend most of their time on the web, and is being designed to power computers ranging from small netbooks to full-size desktop systems. While there are areas where Google Chrome OS and Android overlap, we believe choice will drive innovation for the benefit of everyone, including Google.

We hear a lot from our users and their message is clear — computers need to get better. People want to get to their email instantly, without wasting time waiting for their computers to boot and browsers to start up. They want their computers to always run as fast as when they first bought them. They want their data to be accessible to them wherever they are and not have to worry about losing their computer or forgetting to back up files. Even more importantly, they don’t want to spend hours configuring their computers to work with every new piece of hardware, or have to worry about constant software updates. And any time our users have a better computing experience, Google benefits as well by having happier users who are more likely to spend time on the Internet.

We have a lot of work to do, and we’re definitely going to need a lot of help from the open source community to accomplish this vision. We’re excited for what’s to come and we hope you are too. Stay tuned for more updates in the fall and have a great summer.

• Offers the possibility to improve upon a broad range of communication, collaboration, and/or text-based product categories, such as:
  • Search
  • Word processing
  • E-mail
  • Instant messaging
  • Microblogging
  • Blogging
  • Mini-portals (Facebook-style)
  • Mini-portals (Sharepoint-style)
• In particular, allows these applications to be both much more integrated and interactive than they now are.
• Will have open developer APIs.
• WIll be open-sourced.

If this all works out, Google Wave could play merry hell with Microsoft Outlook, Microsoft Word, Microsoft Exchange, Microsoft SharePoint, and more.

I suspect it will.

And by the way, there’s a cool “natural language” angle as well.

For starters, here are some basic links:

• Google has naturally set up a home page for the Google Wave project.
• Featured on that page but also separately available is an 80-minute video introducing Google Wave.
• Techcrunch has two highly detailed posts on Google Wave, one summarizing what’s in the main Google Wave video and one reporting on a Google Wave Q&A.

Here are some reasons I think Google Wave could actually live up to its promise:

• The email problem Google Wave purports to solve is real and critical. The email paradigm assumes linear conversations, and what actually happens is that they branch. Google Wave’s message-board-like paradigm is simply better, and more flexible (e.g., not limited to a single enterprise!) than Microsoft Exchange or Lotus Notes.
• The instant messaging problems Google Wave purports to solve are also major. Instant messaging is slow, tedious, disjointed, and ephemeral. Fully integrating IM with email solves most of those problems. And Google Wave’s UI interactivity solves most of the rest.
• Twitter needs to be integrated with other forms of communication. What’s more, Twitter’s functionality needs to be drastically extended. Google Wave is the best hope I know of to meet those needs.  Enterprise Twitter is just a special case of that.
• Workgroups (enterprise or otherwise) need light-weight mini-portals that can be created on the fly by non-technical users, to ease collaboration. Microsoft SharePoint, SAP Rooms, et al. don’t really meet that need.  Google Wave could.
• In particular, collaboration on documents, presentations and so on needs to be more cloud-based and generally easier than is the case in Microsoft Office. Google Wave has the potential to provide that.
• Google + open source is a potentially potent combination, especially versus Microsoft.

One note: Google of course needs to improve the reliability and customer service of its cloud-based offerings to make a huge dent in Microsoft’s market. But even with its flaws Google has already been a good alternative for a while.

As for the “natural language” angle: At the 44:30 mark of the main Google Wave video is a demo of some cool, very grammar-sensitive spell-checking technology. Google’s spell-checking technology is further discussed in a separate, short video.  The basic idea is that Google uses its vast library of web pages — and email and chat? — not just to model intended word usage but also kinds of mis-spelling behavior as well.

Since the early 1980s, I’ve thought that natural language interfaces — spoken or otherwise — would someday win.  While this versatility isn’t natural lanaguage per se, it still in my opinion is evidence in favor of that belief.

• A Google acquisition of Twitter
• Some other kind of relationship built around real-time search

I have three initial thoughts on this:

1. Clearly, in Google’s mission to “organize all the world’s information,” there are several web areas it isn’t yet doing well in, and one of those is microblogs. What’s more, much as in the case of YouTube, it’s hard to see how Google would do that organizing any time soon unless it owned or otherwise was in bed with the leading platform for that kind of content — i.e., Twitter.

2. The YouTube example is apt in another way as well — it’s not clear where the monetization would come from. Google famously doesn’t make much advertising revenue from YouTube. And Twitter is even worse as an advertising platform; sticking ads into the tweetstream would quickly drive users elsewhere, and any other advertising scheme would likely fail because of the broad variety of interfaces — such as various mobile phones — Twitterers use to get at the service.

3. I’ve been suggesting all along that Twitter needs radical user experience enhancements. But when has Google ever made made user experience enhancements to a service? Its core search engine always looks pretty much the same. Ditto GMail. Ditto Blogger. Ditto YouTube.

I suspect CADIE is going to grow up a lot over the course of the day …