\ Software | TechnoTaste

Software


Everyone is a-flutter this morning about Google's announcement: the rumors are true, and they are developing a new operating system after all. It's called the Google Chrome OS, and it's going to be targeted at netbooks. Netbooks are those cheap, light laptops that are designed to connect to the internet and that's about all.

When Google makes any kind of big announcement the tech. world sits at attention and listens carefully. TechCrunch says Google just dropped a nuclear bomb on Microsoft. This one, however, is a big fat yawn. Google will release an OS, a small group of dedicated Google-fanatics will use it, and then it will die a slow and steady death. Here's why:

  1. Google is good at search. Easy, one-step search. Fast and easy search has become so important to everyone, across every demographic and level of expertise that Google has become the verb to describe that action. But operating systems are not like search. Operating systems for netbooks are even less like search. More importantly, all those people who understand fast and easy search are not interested in OSs, and they've never heard of netbooks.
  2. "Hey, wait!" you say. "Google isn't stupid. They know a netbook OS isn't for the masses. This is about Google promoting its brand and its products. It's the same strategy as Android." Well, I say, it may be the same strategy, but mobile OS and netbook OS are very different. There are only a handful of mobile OSs. There are dozens of OS distributions (flavors of Linux), many of which are targeted to netbooks. Google can't compete with that. No matter how much $$ and development time they throw at their OS, they'll need a dedicated community of developers and testers. And they'll need to steal them from another open source project. The Google carries a lot of weight, but it can't carry that load.
  3. An operating system doesn't take advantage of Google's core competencies. They have two. First, search. Second, efficient use of massive (and massively distributed) servers. GMail, Docs, etc. make sense because they integrate with search and capitalize on Google's massive server load. A netbook OS does neither.

From my POV, this is just another bit of Google casting around in search of more footholds. Eventually they'll find one, but it won't be operating systems, and it won't be browsers. (Depending on who you ask, Google Chrome is languishing at between 1 and 3% market share.) It may be that these efforts, even if they're incrementally beneficial, are useful enough for Google to push them. Convert a few developers, get some buzz, develop technology with multiple uses. That's fine. But let's not call it a nuclear bomb. A world with Google Chrome OS will look almost exactly like a world without it.

As part of my foray into LaTeX, I started to check out Zotero. I've been a happy EndNote user for years now. Love the Word integration. But it really doesn't play well with LaTeX. The RIS and Bibtex export filters are crap. And, obviously, it doesn't integrate with a LaTeX GUI editor the way it does with Word.

I know many people who sing the praises of Zotero, and I know it does a better job of exporting to Bibtex. But after a few days of using it, I'm done. Granted, I haven't put it through as rigorous a test as I might have, but here are my first impressions:

  1. Wow does it slow down Firefox. At least for me, there was a noticeable snappiness hit and a big increase in memory footprint with Zotero running.
  2. It does not seem to do the magic I want it to. I tried to get it to import cites using the "Create New Item from the Current Page" feature, expecting great things. No dice on ACM Portal, IEEE Explore, or ScienceDirect. Maybe I'm not doing it right. The only way I could get it to import a cite was to export a citation for EndNote. Zotero intercepts it and imports. But that's no better than EndNote.
  3. Zotero still doesn't solve the problem of integration with my LaTeX editor. I have to gather cites in Zotero, export a Bibtex file, then go back to my editor.

So, Zotero is out. I think I'll try JabRef next, which integrates with LatexEDitor.