A Browser is More than Script

Shelley Sat, 03/21/2009 - 07:48

Chrome released on Linux, and IE8 released from beta. Now people are beginning to question Firefox's increasingly bigger piece of the blogger pie. Case in point, PC World.

Mozilla have several grand aims, and there's much to be admired, but they've forgotten how to make a decent browser. I feel plenty of loyalty for them, because they've done more than anybody else to further the cause of open source software in the real world. But when I tried Chrome, as incomplete as it was, I realized I'd found a replacement for Firefox. As soon as it gets to beta under Linux, I will switch to Chrome. No question. It's just infinitely better. It's like when we all switched from Alta Vista (or Yahoo!) to Google back in the early noughties. The king is dead! Long live the king!

I was asked my opinion about the future of JavaScript applications this week, especially in light of the blazingly fast Chrome. I was rather surprised at the emphasis on JavaScript, because a browser is more than just a machine to consume script. A browser must also render a web page, as the designers built her; must display photographs accurately, hopefully using any photographer supplied profiles; to render the more complex SVG, in addition to the simpler Canvas; to handle complex file types, including video files, not to mention supporting different markups, such as XHTML in addition to HTML; to provide the utility to enhance the user's experience, up to and including any extensions, such as the one I use to collect a page's RDFa. Why, then, are we reducing the browser to nothing more than a device to to render HTML and JavaScript?

Firefox is working on its scripting engine, but it's also been improving its graphical rendering engine, including adding in built-in support for color profiles, as well as improvements in support for CSS3 and SVG. Chrome has no support for color profiles, it's graphical rendering engine sucks, as can be seen if you look at CSS3 curved corners in the browser, and it regularly fails my SVG tests. Try this SVG file in Chrome, but don't blame me if your CPU spikes. Luckily, it seems that Chrome just aborts SVG files it can't handle now, rather than fry the CPU. Then try the same page in Safari or Firefox; though both render the page slowly, they do render it—Chrome only rendered the file the third time through. It aborted the page the first two times. And the quality of the rendering? Well, see for yourself.

Look at my photos at MissouriGreen. Most use a color profile. Now, the photos look relatively good in Chrome on Windows, because I'm favoring a sRGB color profile to ensure maximum coverage, but if Chrome is ever implemented in the Mac, the photos will look plain, and washed out, as they do now with Opera. Not so the latest Firefox, and Safari.

Lastly, look at this site, or Just Shelley in Chrome, as compared to Safari, or Firefox, even the latest beta of Opera. I make extensive use of box and text shadows, as well as CSS3-based curved corners. No browser is perfect in its implementation of CSS3 curved corners yet, but the anti-aliasing in Firefox and Safari is vastly superior than what you'll find in Chrome. I have noticed, though, that Chrome has improved its text and box shadows: it doesn't plaster them half way down the page, now.

Why, then, do we talk about how "superior" Chrome is? And how Firefox is dying? When one looks at all of the browsers from an overall web experience, only IE8 is worse than Chrome.

I apportion blame for an over-emphasis on fast script over everything else equally between Google and the current HTML5 effort. I found it telling that, at the same time people are lambasting Firefox for "slowing" down, and praising Chrome for "speeding" up, Douglas Bowman is leaving Google primarily because the company relies on engineering practices, at the expense of fundamentals of design. One doesn't have to stretch one's intuition in order to see that the "machine" is also the emphasis in Chrome. But the same could also be said about the HTML5 effort: an emphasis on mechanistic aspects, such as client-side storage and drag-and-drop, at the expense of a more holistic environment, such as including support for SVG and ensuring continued support for accessibility—though I think this week, at least, client side storage has been pulled for inclusion...elsewhere.

Speed is important in a web browser, speed and efficiency, and Firefox isn't perfect. Newer versions have been locking up on my Leopard machine, to the point where I now prefer Safari on the Mac. If I had to take a guess, Firefox has threading issues. It also needs to work on isolating extensions to the point where they can't harm the overall browsing experience—or at least put something in place so that one knows certain extensions can adversely impact on browser performance.

At the same time, Chrome desperately needs to improve its graphics rendering capability. As this occurs, and as Chrome gets loaded down with extensions, I don't think we'll see the same fast speeds when rendering pages we see now.

It's all a question of balance—the best browsers are the most balanced browsers, and sometimes this means slower page loading in support of better page rendering. As it is, Chrome, Firefox, Safari, and Opera are all giants towering over the anemic and disappointing IE8. If we want to talk about a browser "dying", I have a better candidate in mind than Firefox.

Twitter: An interesting experiment

Shelley Thu, 03/19/2009 - 08:00

I've now used Twitter seriously for a month or two. I've enjoyed chatting with friends, and experiencing an application that brings genuine enjoyment to people I like, and admire. I can also now see the utility of the tool, especially for those who don't communicate frequently online, as it gives us a way to keep in touch and stay informed. But in the last week, I've grown less interested in using the application.

One reason for my growing lack of enthusiasm for Twitter is posts disappearing—a relatively frequent event that has happened to a lot of people this week. Given how taxed the application is, problems of this nature are not surprising. What is surprising, though, is how indifferent most people seemed to be about the whole thing. Perhaps I'm old fashioned but one fact I've learned over the years in developing applications is that the data is sacrosanct. That the loss of "tweets" is no big thing to folks tells me that a) the underlying application has problems more profound then just being able to access the service, and b) that people don't really seem to value what they post on the service. That last one is particularly confusing: if the people don't value what they post, then why spend so much time using the tool?

Another reason I'm thinking of using it less is that I can't keep up with the posts. By Twitter standards, I'm practically a loner, but I find the amount of news and information to be overwhelming. Before this week, if I wanted to catch up with specific people, I would just go to their Twitter page. However, with Twitter dropping posts, I'm most likely going to miss half of what they said, anyway.

Then there's the whole "mean" thing. I guess I'm "mean" or sarcastic with too many of my postings. The problem is, you can easily write upbeat, positive, and wonderful things within 140 characters, but the same can not be said about criticism. Not all of us have mastered the art of Twitter snark.

None of this would matter, though, if it weren't for my lack of comfort with Twitter. I cannot get over that feeling of being the person at the party who drinks too much and says the wrong thing at the wrong time; or puts on the lamp shade and dances around wearing nothing but socks and strategically placed jello shots. Frankly, I don't think everyone is cut out for Twitter.

Remember the scene in the movie Pretty Woman, when Edward Lewis (played by Richard Gere) takes Vivian (played by Julia Robertson) to the Opera? Just before the curtain goes up, Edward tells Vivian, People's reactions to opera the first time they see it is very dramatic; they either love it or they hate it. If they love it, they will always love it. If they don't, they may learn to appreciate it, but it will never become part of their soul. Well, I hated Twitter when I first saw it.

Best of luck in finding a suitable employer

Shelley Tue, 03/17/2009 - 23:03

Roger Johansson

I believe having more content creators and ”authors”, i.e. web designers and web developers, in the HTML Working Group would be good. Unfortunately I think it’s hard to find web professionals who can spare the time unless they get paid to participate. I know I can’t.

When I mentioned something virtually identical to Ian Hickson, he told me

I am sorry you feel that you need to be compensated for your participation in the standards community, and wish you the best of luck in finding a suitable employer.

Can't wait to read Ian Hickson telling Roger Johansson, "...best of luck in finding a suitable employer."

EOL Monetized

Shelley Sun, 03/15/2009 - 08:47

I wrote about planning for death, including how to handle our online lives last August in a writing titled, Planning your own EOL. Evidently, others had the same idea, and now businesses with names like Deathswitch and Slightly Morbid are springing up, providing services such as that one last email to be sent.

The Death of gamers leave their lives in limbo

With all of the foo-flah about Twitter this weekend, perhaps I should start a company called LastTweet. It could feature its own cute graphic—a gracefully dead bird, or perhaps an artistic rendition of roadkill. What would the hash mark be for messages from the company? Something like #RIP? #deadmantweeting?

Kindlegate

Shelley Sat, 03/14/2009 - 19:20

Being a Kindle owner, I've been following, and involved in, many discussions related to the recent DMCA take down notice that Amazon served on the eBook friendly site MobileRead. I'm too tuckered from arguing in other forums to say much now. At this time, all I'm going to do is list out pertinent articles and forum threads, and write my first impressions of the events.

The take down notice was first detailed in MobileThread

As some of you may already know, this week we received a DMCA take-down notice from Amazon requesting the removal of the tool kindlepid.py and instructions associated with it. Although we never hosted this tool (contrary to their claim), nor believe that this tool is used to remove technological measures (contrary to their claim), we decided, due to the vagueness of the DMCA law and our intention to remain in good relation with Amazon, to voluntarily follow their request and remove links and detailed instructions related to it.

A quick backgrounder: kindlepid.py is a small Python script allowing you to derive a Mobipocket-compatible personal identifier (PID) for your Kindle reader. This PID in itself has nothing at all to do with reading any copyrighted content. It is only used to make legitimate e-book purchases at stores other than Amazon's.

We believe in the freedom of speech and we encourage you to continue expressing your views and thoughts on tools like kindlepid.py. We only ask you not to provide any how-to instructions, source codes and/or links for obtaining kindlepid.py.

Several people and organizations have weighed in on the issue, including Slashdot, BoingBoing, CNet and so on. You can find links to the articles in TechMeme, but I also linked stories as I found them in a thread I started in the Kindle owner's forum at Amazon. Current entries to that thread: 127 and counting. Some interesting, and differing, opinions are shared.

What puzzled a lot of people is, why now? The application that Amazon is unhappy about, kindlepid.py, has been out and in use, and discussion item in Amazon forums since December of 2007. So, why now, and why serve a DMCA on MobileRead, rather than Google Apps, or other sites were the software is actually hosted?

A little hunting around found the most likely cause of this current foo-flah: another thread at MobileRead. The timing of the thread and the DMCA seem too close not to be related.

I'm not rigidly against DRM, though I would be happy to have my own books DRM free. (Painting the Web is available without DRM at O'Reilly.) As we all know, DRM typically harms legitimate owners, and does little to prevent piracy. Regardless, I can understand the use of DRM...but it should be based on a consistent standard the industry shares, so that if I buy a book at one eBook store, it will work with my Kindle; and an Amazon eBook will work on devices other than Kindle. Anything else is death to the industry. The industry is just too new, and too small, to be fragmented by such walls.

The Kindle is based on the MobiPocket Mobi digital format. Because of this shared format, Mobi books will work on a Kindle. However, Mobi books also have a PID-based DRM system that requires you provide your device's PID if you want to buy a book. What kindlepid.py does is provide Kindle owners that PID. It does not bypass the DRM; it doesn't circumvent copyright—it just gives us the ability to buy books in other stores.

More importantly, libraries are now incorporating digital book loans, but they're based on DRM-enabled PDF files, or DRM-based Mobi books. If we want to "check" a book out at our libraries for use on our Kindle, we have to use both kindlepid, to get the PID, and kindlefix, to set a flag so we can read the book on our Kindles.

The book loan still expires at the end of the loan program. We can still only read the book on the given device. We've not broken either law or copyright or DRM. And since Amazon refuses to work with libraries, about the only way Kindle owners will have access to library loans is the use of this software.

The DMCA move by Amazon was especially disappointing to me, personally, because one reason I felt comfortable with buying a Kindle is that I trusted Amazon, I trusted Jeff Bezos, not to keep the Kindle jailed forever. I assumed that over time, the company would open both the Kindle, and the book store. I believed that what Amazon did for MP3s, it would eventually do with eBooks. Well, I can see with the DMCA, my trust was misplaced. I guess one can never get too old to still be naive.

I still like my Kindle, but I'm no longer comfortable buying books for it from Amazon. Luckily there are free ones that Amazon "allows" me to load on to the Kindle. As for new books, I've returned to paper books, via library loans. Too bad, too, because my library just doesn't carry all the books I want.

I've also taken copious notes from the books I do have on the Kindle, for that day when the device breaks. I strongly doubt I'll ever buy another eBook reader, much less another Kindle. Not until the industry gets its act together.

Like I said, more some other time.

Wolfram Alpha

Shelley Tue, 03/10/2009 - 10:59

Sheila Lennon asked my opinion on the Nova Spivack's recent writing about Wolfram Alpha, and posted my response, as well as other notes. Wolfram Alpha is the latest brain child of Mathematica creator, Stephan Wolfram, and is a stealth project to create a computational knowledge engine. To repeat my response:

First of all, it's not a new form of Google. Google doesn't answer questions. Google collects information on the web and uses search algorithms to provide the best resources given a specific search criteria.

Secondly, I used Mathematica years ago. It's a great tool. And I imagine that WolframAlpha will provide interesting answers for specific, directed questions, such as "what is the nearest star" and the like. But these are the simplest of all queries, so I'm not altogether impressed.

Think of a question: who originated the concept of "a room of one's own". Chances are the Alpha system will return the writing where the term originated, Virginia Woolf's "A Room of One's Own", and the author, Virginia Woolf. At least, it will if the data has been input.

But one can search on the phrase "A room of one's own" and get the Wikipedia entry on the same. So in a way, WolframAlpha is more of a Wikipedia killer than a Google killer.

Regardless, when you look via Google, then you get link to Wikipedia, but you also get links to places where you can purchase the book, links to essays about the original writing, and so on. You don't get just a specific answer, you also get context for the answer.

To me, that's power. If I wanted answers to directed questions, I could have stayed with the Britannica years ago.

Nova Spivack's writing on the Alpha is way too fannish. And too dismissive of Google, not to mention the human capacity for finding the exact right answer on our own given the necessary resources.

Again, though, all we have is hearsay. We need to try the tool out for ourselves. But other than helping lazy school kids, I'm not sure how overly useful it will be. If it's free, yeah. If it's not, it will be nothing more than a novelty.

I also beg to differ with Nova, when he states that Wolfram Alpha is like plugging into a vast electronic brain. Wolfram Alpha isn't brain-like at al.

The human brain is amazing in its ability to take bits and pieces of data and derive new knowledge. We are capable of learning, and extending, but we're really shite, to use the more delicate English variation of the term, when it comes to storing large amounts of data in an easily accessible form.

Large, persistent data storage with easy access is where computers excel. You can store vast amounts of data in a computer, and access it relatively easily using any number of techniques. You can even using natural language processing to query for the data.

Google uses bulk to store information, with farms of data servers. When you search on a term, you typically get hundreds of responses, sorted by algorithms that determine the timeliness of the data, as well as its relevancy. Sometimes the searches work; sometimes, as Sheila found when querying Google for directions to cooking brown rice in a crockpot, the search results are less than optimum.

Wolfram Alpha seems to take another approach, using experts to input information, which is then computationally queried to find the best possible answer. Supposedly if Sheila asked the same question of Wolfram Alpha, it would return one answer, a definitive answer about how to cook brown rice in a crockpot.

Regardless, neither approach is equivalent to how a human mind works. One can see this simply and easily by asking those around us, "How do I cook brown rice in a crockpot?" Most people won't have a clue. Even those who have cooked rice in a crockpot won't be able to give a definitive answer, as they won't remember all the details—all the ingredients, the exact measurements, and the time. We are not made for perfect recall. Nor are we equipped to be knowledge banks.

What we are good at is trying out variations of ingredients and techniques in order to derive the proper approach to cooking rice in a crockpot. In addition, we're also good at spotting potential problems in recipes we do find, and able to improve on them.

So, no, Wolfram Alpha will not be like plugging into some vast electronic brain. And we won't know how well it will do against other data systems until we all have a chance to try the application, ourselves. It most likely will excel at providing definitive answers to directed questions. I'm not sure, though, that such precision is in our best interests.

I also Googled for a brown rice crockpot recipe, using the search term, "brown rice crockpot". The first result was for RecipeZaar, which lists out several recipes related to crockpots and brown rice. There was no recipe for cooking just plain brown rice in a crockpot among the results, but there was a wonderful sounding recipe for Brown Rice Pudding with Coconut Milk, and another for Crocked Brown Rice on a Budget that sounded good, and economical. I returned to the Google results, and the second entry did provide instructions on how to cook brown rice in a crockpot. Whether it's the definitive answer or not, only time and experimentation will tell.

So, no, Google doesn't always provide a definitive answer to our questions. If it did, though, it really wouldn't much more useful than Wikipedia, or our old friend, the Encyclopedia Britannica. What it, and other search engines provide is a wealth of resources for most queries that not only typically provide answers to the questions we're asking, but also provide any number of other resources, and chances for discovery.

This, to me, is where the the biggest difference will exist between our existing search engines and Wolfram Alpha: Alpha will return direct answers, while Google and other search engines return resources from which we can not only derive answers, but also make new discoveries. As such, Alpha could be a useful tool, but I'm frankly skeptical whether it will become as important as Google or other search engines, as Nova claims. I don't know about you all, but I get as much from the process of discovery, as I do the result.


Nova released a second article on Wolfram Alpha, calling it an answer engine, as compared to a search engine. In fairness, Nova didn't use the term "Google killer", but by stating the application could be just as important as Google does lead one to make such a mental leap. After all, we have human brains, and are flawed in this way.

As for artificial intelligence, I wrote my response to it in Twitter: It astonishes me that people spend years and millions on attempting to re-create what two 17 year old can make in the back seat of a car.

Blank Slates and new Hard Drives

Shelley Sat, 03/07/2009 - 13:10

The Apple folks were able to replace the hard drive in my Powerbook quickly, and I picked it up last night. I noticed that they installed Tiger, not Leopard, and when I asked why, since I had Leopard, they said that they could only update to what was originally installed on the machine. I can understand their point, but it still took 2 hours to upgrade to Leopard, and another 1 hour or so to do all of the updates.

The machine still feels sluggish, and I was tempted to keep it at Tiger. However, I have software that won't run on Tiger, and when Snow Leopard releases later this year, Macports will only work on Leopard and Snow Leopard (most recent 2 OS versions).

Photoshop was surprisingly easy to reinstall. I had to dig out the old license number for the previous version, but there wasn't any problem with me having to re-activate the application without deactivating a prior copy. Must be machine signature issues.

I also cheated on my iPod/iTunes recovery, by using a shareware application, Senuti to restore iTunes form my iPod. Nice little application, very easy to use, and fast, so it was a good $18.00 spent.

I'm good about backing up, but even so, you can feel the gaps left by losing the original hard drive. Little bits and pieces, not to mention having to set everything up again. This is the first time I've ever lost a hard drive—I know, pretty amazing, eh? I feel like I'm wondering around a familiar room, and someone has moved the furniture and turned off the lights.

I also discovered that it's not a bad idea to completely dump your cookies, and other client-cached data from time to time. For instance, I found that Drupal's caching does not work well when you're using a resizable SVG image, but didn't spot the problem until accessing my sites from a brand sparkly new hard drive. Not sure what's happening, and will need to explore more fully. For now, caching is off.

I also found, and I feel very sheepish on this one, that my experimentation with OpenID actually left me without a way to log into my RealTech site. However, it was very easy to just move the module I had created, and here I am. I know—this was a classic painted-into-the-corner move. Bad me.

One area of concern I did have, is that Apple kept the old drive. However, I called this morning and was told that Apple shreds old hard drives to recycle the metal, and also to ensure that all the old data is gone. The recycling of the old hard drives is all handled in-house, too, and the company has never had a data breach because of old hard drives. So good-bye, old drive, I knew you well.

Semantic Irony

Shelley Thu, 03/05/2009 - 20:21

One of my books finally returns home.

(via David Wood)

Photo backups and hard drives

Shelley Wed, 03/04/2009 - 19:34

First my car, now my computer— I am not having the best of luck with working stuff lately. The verdict at the Genius Bar on my Powerbook is that the hard drive is toast.

No, I don't really believe that Firefox caused my hard drive to fail. I don't think any browser can cause a hard drive to fail; no, not even IE. However, the browser definitely gave the hard drive the coup de grâce.

Now the question is, what did I lose? Luckily I'm good at backing stuff up. I didn't back up all my recent music purchases, but I get music from Amazon, which I can download again, so no loss.

I have some eBooks I'll have to see about finding again. Some were free for a limited time, but I believe are backed up on one of my external drives. I lost all my email since I use a client-based email reader, but you know, old email is like old bread--you always think you'll use it, but you never do.

I do all my web development on my server, or my older Powerbook, so nothing lost there. I had finished all my editing and writing work, so didn't lose any work.

I have to go through the entire process of restoring my Macports installation, which is going to take time. And I have to prepare to argue with Adobe about the Photoshop license. GIMP looks better all the time.

The hard drive failure could have been worst. I had my recent set of photographs on the computer and hadn't backed them up on external hard drive yet. Among the pictures were the last photos of Muchana, a gorilla at the St. Louis zoo who died last Saturday. However, I had developed a habit of not removing photos from my camera's memory card, until I had the photos backed up on external hard drive. The photos are still safe on the camera's card. A hint to the photographers among you.

The Affordable Macs

Shelley Tue, 03/03/2009 - 09:07

Apple has finally wised up to the economy and has rolled out affordable versions of the iMac, the Mac Mini, and MacPro.

The Mac Mini could end up being a TV box killer, especially with the space and CPU. Unlike the AppleTV, you can have your iTunes, and Hulu, too. But it's the iMac that interests me. My computers are getting borderline too old, especially since neither of my laptops will work with the new version of the Mac OS that will be releasing some time this year.

Now, I just have to convince you all to buy a LOT of my books so I can get one.