I read with interest a short note in ars about how Intel is hard at work porting Android 3.0, or Honeycomb, to x86. While this immediately made me think of x86 powered smartphones, I started to think, well, what can’t you do on a smartphone (or perhaps more appropriate a tablet) that you can on a Wintel box? There are a few things (like graphic-intensive first person shooters) but not a huge number, I think.
And this led to me thinking about Chromium OS and, of course, the prototype Cr-48 that made the rounds late last year, most famously for its fraction-of-a-minute boot times and its usability, while I wait, patiently, as my sad little PC huffs and puffs along for several minutes before showing any signs of life.
Which in turn made me think of a post I wrote back in 2008, where I questioned the assertion that many had made back then about the release of Chrome (the browser, that is) by Google as a “Windows killer” and very much agreed with The Register’s take on it (hint, the story was called: Chrome-fed Googasm bares tech pundit futility, and subtitled: It’s a f***king web browser). And just to be clear, this was before Chromium OS was a twinkle in Google’s eye.
And in that post, I was so bold as to state that Microsoft probably didn’t have much to worry about.
I imagine it should suffice to say that I don’t quite feel the same way these days….
So as many of you have already heard, it looks like Yahoo will be shuttering delicious. Sad but apparently true. In any event, one would think that it would be a relatively simple matter to export from delicious and import into your browser’s bookmarks. The export part is relatively straightfoward, but (at least for those using Firefox, which I do), if you want to import your tags along with your bookmarks, things get a little trickier, because of some incompabitilies between the format that delicious uses for its export file (html) and the format that Firefox uses (JSON).
Apparently, some folks far cleverer than I came up with some ruby scripts that can do it, but why go to all that trouble. Here’s the easiest solution I’ve been able to find: Go here but before you follow the steps, make note of the following:
instead of typing in the URL identified in Step 2 (http://api.del.icio.us/posts/all) use this one instead: https://api.del.icio.us/v1/posts/all (you need to copy and paste into the location bar).
In Step 6, there is one minor detail omitted – the steps to restore should be [Bookmark] -> [Organize Bookmarks] -> [import and backup] -> [Restore] -> [Choose file] -> <created file at 5>.
Also in Step 6, if you have a lot of bookmarks be forwarned that Firefox may become non-responsive as it processes the import. It may give you the “script is taking a long time to respond” message. If you do get that, select the “don’t ask again” checkbox and then click “continue”, then go grab a coffee or some other beverage. Once its done, you should have all your bookmarks (and tags) from delicious now safely ensconced in your Firefox bookmarks.
If you still need an online bookmarks tool, consider Mozilla Sync or Diigo. Perhaps not surprisingly, there seems to be a bit of a backlog in processing imported bookmarks into Diigo. If you don’t need to import bookmarks into Firefox and plan to use something like Diigo exclusively, then of course no need to go through all of the hassle above, as (from what I understand) Diigo will import tags when you import your delicious bookmarks.
Read an article in eWeek that left me scratching my head a bit. The nub below:
Google may be treading lightly with Chrome now, but the browser, combined with Google’s search and Apps, could end up being a big threat to Microsoft Windows’ market share.
Then later:
When Google accidentally leaked its Chrome comic book Sept. 1, reporters and analysts, including yours truly and my colleague Joe Wilcox, argued that Google could make Chrome the premier Web operating system by combining it with its market-leading search engine and increasingly popular SAAS (software as a service) applications. This would eventually constitute a threat to Windows.
And that would spell doom for Microsoft. It’s one thing to squeeze Microsoft out of the Internet game by dominating search and Web services. It’s another entirely to come after the software giant’s core operating system business, wielding the Web as your platform.
Must admit I have a lot of trouble seeing that, as I would have thought in order to supplant Windows, it would need to be gone, and to go from a browser that sits on an o/s to replacing the o/s seems to be a rather large leap. A huge leap, actually.
What they’re suggesting might happen is already a possibility today. There is definitely something that can supplant Windows altogether, and provide access to all the web-oriented apps, etc. that Google offers. Its cheap (sometimes free), stable and has pretty good UIs – in fact, a selection of UIs and different flavours. Its called Linux. However, for a variety reasons, it hasn’t kicked Microsoft’s ass yet (at least on the desktop – there are a few areas where it definitely does, such as web and other server functions).
To suggest, then, that, because Google has come out with a browser, that that will lead to the supplanting of Windows seems, IMHO, to be a bit far-fetched. I’m not suggesting that Google wouldn’t have the wherewithal to try to go after the desktop. They may do so. Though I’m not sure if they’d want to – they have a pretty good business model already…
Anyway, if and when they do something like that it will be so much larger an undertaking than Chrome that the links between that and Chrome would be tenuous at best, other than possibly bundling Chrome within whatever o/s they create.
Even possibly on the application front, I can see Google putting some pressure on MS, and how this might tie with Chrome. But not the o/s on which the whole thing runs.
So I think for the time being, Bill and Steve probably don’t have much to worry about with Chrome’s introduction, at least when it comes to the o/s business (IE on the other hand, is another matter altogether…).
Most of you probably already have heard that Google has officially announced its new browser, Chrome, which will be released to the public (in beta form) later today. It is an open source project that has a very, very interesting set of features that enhance security, privacy, speed and stability, including multiprocessing architecture.
You can read more about the features in the comic that Google has published to walk you through it. What a great approach. Wikipedia also has a bit of a compressed summary of the new features as well, which is a bit quicker to get through than the comic.
Will be very interesting to see how this browser does. I imagine it likely will be quite good, given most of the stuff that Google has offered. That being said, I was a bit concerned as to what this meant for Mozilla, whose existence (or at least revenue) I understand depends significantly on its relationship with Google, which is now, effectively, a competitor of sorts. Mozilla’s CEO has already posted his reactions to Chrome. Whether or not it turns out to be a good thing or bad thing remains to be seen – there are already a few folks who have alluded to the possibility of a Google “monopoly” and/or anti-competitive behaviour through Chrome. IMHO I think that’s rather unlikely.
At the end of the day, though, I think this will only serve to enhance the choices people have, browser wise, and improve things all around. Though I’m hoping it will not lead to the demise of Mozilla. I like Mozilla. And of course Firefox.
Update: Alas several hours later no Chrome love for yours truly. If you haven’t given it a shot by all means do so and let me know if you get through. I imagine that’s what happen when a billion or so people try to download the same thing, notwithstanding Google’s massive pipes and data centres. (see below) Also, saw a great story in The Register, that poked a bit of fun at Google. A little sample that, coincidentally, fits right in with the law-related theme of this blog:
Further update: Seems I had a bad link. Tried again (googled) and was able to download from a different URL. Very easily, actually. But, alas, apparently need to close the browser I’m using to install…
Further further update: Installed and running. So far, so good. Rather bare bones but impressive memory footprint, and very snappy, both on launch and, well, pretty well everything else. A very simple and straightforward approach that doesn’t have a million options, choices and tweaks, or nifty integrations (a la Flock). Miss my plugins though. And not surprising there don’t appear to be any for Chrome right now, at least AFAIK.
Another update: Works well but does not play well with Facebook – some links/features just don’t work.
