By Dan Kennedy • The press, politics, technology, culture and other passions

Tag Archives: Safari

The next few weeks should be interesting as the folks at the Boston Globe work out the bugs at BostonGlobe.com.

Starting last night, the site stopped working on my almost-four-year-old MacBook using Chrome and Safari. (Might be just my set-up, though I did reboot.) On the other hand, it still works fine with Firefox, for which I’ve recently been developing a new appreciation, as it seems to be the most stable of the three major Mac browsers. No problems on my iPhone or on Mrs. Media Nation’s iPad, either.

I’m glad to see Dan Wasserman’s editorial cartoon made it to the site today, and I hope syndicated cartoons will be included on days that Wasserman isn’t drawing. The comics are online today, too. Maybe they were yesterday, but I couldn’t find them.

Other observations: clean as the site is, the organizational scheme is a bit bewildering, with many different options. I feel as though I’m missing stuff. The “Today’s Paper” option doesn’t seem to be quite that. It would be nice to have a clearly delineated separate section of everything that’s in that day’s print edition.

Also, how about combining all the little “Names” tidbits into one column? Other “g” shorts could be combined, too. I don’t want to keep clicking to read 90-word items. It’s one of my main peeves about GlobeReader, too, and I’ll bet I’m not alone.

Welcome to the tech blog whose author almost knows what he’s talking about. I know just enough to be dangerous, folks. Here are three tidbits for your Tuesday morning.

1. Beyond Google Reader. Last week Laura McGann of the Nieman Media Lab was rhapsodizing to a group of us about the glories of NetNewsWire, an RSS aggregator that resides on your computer rather than in the cloud, as is the case with Google Reader.

I was not entirely unfamiliar with NetNewsWire. I’d played with it before, but preferred a competitor called NewsFire. Several years ago, though, I made the switch to Google Reader and hadn’t looked back.

But lately, like many people, I’d found myself looking at Google Reader less and following interesting links from Twitter more. In part it’s because I really like Twitter. In part, though, it was because Google Reader just wasn’t all that satisfying — it’s slower than using a good client-based news reader and shows you less content before you click.

So a few days ago I reinstalled NetNewsWire and found, to my delight, that it now syncs with Google Reader, which means you don’t really have to decide. It’s fast and free (if you don’t mind looking at advertising; I don’t). If you’ve been losing interest in Google Reader, give NetNewsWire a try.

2. From Chrome to Safari and back again. When Apple unveiled Safari 5 a few months ago, I made the switch from Google Chrome. Though not quite as fast as Chrome (I’ve seen test results that say otherwise, but that’s not my experience), Safari was aesthetically more pleasing. My favorite feature, Reader, isolates the text in a story or blog post and presents it in as a beautifully rendered, easy-to-read page. On a properly designed website, Reader will even find the jump and display that, too.

Then Xmarks went out of business. Xmarks is a browser extension that lets you sync your bookmarks in the cloud and use them across multiple computers. An e-mail from the company outlined the alternatives — free for Internet Explorer, Firefox and Chrome, but $99 for Safari via Apple’s MobileMe service.

As it turns out, there are at least two free extensions for Chrome — Readability Redux and iReader — that do what Safari’s Reader does, and are more customizable besides. So goodbye Safari.

3. The future of Reader. OK, different Reader — now I’m talking about Times Reader and GlobeReader, the paid electronic editions of the New York Times and the Boston Globe built on Adobe Air.

I’ve been a big fan of Reader since it was unveiled a couple of years ago, but I find that it hasn’t kept up. And with the development folks furiously working on iPad and mobile editions, it doesn’t seem likely that much brain power is going to be devoted to improving them, my wish list aside.

Here’s what I like about Reader: it’s fast, it’s highly readable and you don’t need an Internet connection once that day’s edition has been downloaded. What I miss, though, is the richness of the Web — the slideshows, the videos, even the advertising. Lately, more often than not, I find myself using the “Today’s Paper” feature of NYTimes.com, supplemented with Chrome’s iReader extension. (I still tend to use GlobeReader because the “Today’s Globe” section of Boston.com can be so slow.)

Maybe the Reader editions have a future. But my suspicion is that they are just going to fade away for lack of interest.

Because I had a lot of writing to do yesterday, I indulged myself with some quality screwing-off time and installed Safari 5, the latest version of Apple’s Web browser. I can’t say I expected much. Safari has always been feature-laden but sluggish. The new version, though, is speedy enough that I may make it my primary browser.

For several years I had been a dedicated Firefox user. But after Google released Chrome for Mac earlier this year, Firefox seemed downright slow by comparison. Chrome blazes, but it doesn’t have much else to recommend it. I especially don’t like the way it displays type — it seems like everything is either a smidgen too small or too large.

The new Safari, by contrast, is slick and attractive, and has a lot of nice touches. I’m a big fan of the Top Sites window, a graphical representation of my most-visited stops on the Web. Chrome has something similar, but the customization features are minimal. Safari also handles bookmarks nicely. Most important, it seems as fast as Chrome, and, unlike Firefox and even Chrome, it doesn’t gag on the Boston.com ad server.

The most interesting feature of Safari is something called Safari Reader. Open a page with an article on it, and a clickable label appears in the address bar. Select it and a new window opens with a nicely formatted text page. Unfortunately, Reader makes it easier to avoid advertising. But since photos within the text are displayed, I see no reason why ads couldn’t be embedded as well.

Reader is especially nice for complex sites with tiny type, such as the example I’ve included above from the New Haven Independent.

One problem is that Web designers have to write to Reader’s specifications or it won’t work properly. NYTimes.com, for instance, handles jumps with aplomb, whereas Boston.com, upon encountering a jump, incorrectly displays the first page again. Reader is going to have to prove very popular in order to force Web designers to change. But it could happen. Safari, after all, isn’t just for Macs (and PCs), but for iPads, iPhones and iPods as well.

No sooner did I tweet my enthusiasm about Reader than Alex Johnson responded by telling me that the same feature had been available in other browsers for some time. Sure enough, I found an extension for Chrome called Readability that did exactly the same thing. But it was glitchy compared to Safari Reader, which Johnson concedes is “the better option for Mac-only users.”

Safari also has a built-in RSS reader, but on first glance I see no reason to switch from Google Reader, which I love. (A lot of programs named Reader, eh?) There doesn’t seem to be any way of pulling my Google Reader feeds into Safari, which would be a minimum requirement for me even to test it.

Between Safari and Chrome, I doubt I’ll be using Firefox any time soon. I’ll try Version 4 when it is released later this year. For now, though, Firefox has definitely fallen behind.

Like this:

So I was enjoying my trial with Safari (for reasons that I can’t quite describe, it feels a little more nailed-down than Firefox 3) when I hit a roadblock: Blogger.

I noticed a post I’d written with Safari had some weird spacing in it. When I looked at the underlying HTML, I saw that Safari inserts bracketed “div” and “/div” thingies every time you hit the RETURN key.

Why, after all these years, are Safari and Blogger still not entirely compatible? Anyway, that’s pretty much a show-stopper for me, so I’m back to Firefox, somewhat reluctantly.

Like this:

For the past month or so I’ve been using Firefox 3 almost exclusively. I’m running version 3.0.4. And though it basically works fine, it does a few things that are flaky.

Example: In just the past day or two, the typeface for stories at NYTimes.com changed, and I was not pleased. I even considered writing a post about it. But when I looked at it in Safari, it hadn’t changed. And then, when I went back to Firefox, the change for the worse had magically disappeared.

Example: I happen to like those little icons that appear next to Web-site names in my bookmarks. But the one for the Boston Globe keeps changing. It’s currently a ladybug, of all things.

Firefox works fine; these are just minor aesthetic annoyances. But aesthetics matter. Safari keeps getting better and better, and I’d like to give it an extended workout — but I can’t transfer my Firefox bookmarks to it.

Like this:

The last few days, it seems that certain sites take forever to load in Firefox 2 for the Mac — especially the Boston Globe. Firefox freezes up once a day or so, too. So I played around with Safari 3 and found the Globe and the New York Times to be much zippier. But Safari quits whenever I try to load the Boston Herald. Safari is also incompatible with Blogger.

I see that Safari 3 is still in beta, which used to mean that it wasn’t quite ready for public release. Increasingly, though, beta is Greek for “we take no responsibility for our product.” I mean, Gmail and Google Calendar are still in beta, and I use them dozens of times a day.

I’ll be glad when this Internet fad blows over.

Update: I’m trying Camino 1.5.5 for the first time in a couple of years. It’s a Mac-only, open-source browser from Mozilla, and I’m pretty sure it uses the same underlying technology as Safari. I’m living dangerously by posting this from Blogger, but so far, so good.