Category: Web Browsers

Posted on
by
  • Installed IE8 RC1. Installer crashed, and I ended up with IE7…even though I’d been running the IE8 beta before.
  • IE8 installer crashes system. New HW checks out. Bad RAM may have screwed something up before I replaced it. Time for System Restore. *grr*
  • Wow, System Restore is taking a lot longer this time. Maybe it’s actually working? (Or maybe safe mode just makes it slower?)
  • I can’t remember how many times I’ve rebooted this computer today. (And no, safe mode didn’t solve it)
  • Finally got IE8 RC1 installed by telling it not to install updates immediately. The Malicious Software Scan was crashing the system. WTF?
  • Now that I’ve FINALLY got IE8 RC1 running, a cursory check of websites I maintain shows no glaring problems. *whew!*

Posted on
by

Just a quick note: I finally got around to updating the Alternative Browser Alliance website. Not the full rewrite that I was planning to do two months ago, but at least it’s now current on things like Google Chrome, Firebug, Dragonfly, etc.

I’ve also released that site under the Creative Commons Attribution-Share Alike 3.0 license, which should simplify matters for translations.

Finally, as a compromise between a full blog and little notes on the home page, I added another Twitter account, @AltBrowser*, where I’ll post not just site updates but random bits of news, comments, tips, etc. related to the topic.  I don’t have time to maintain yet another blog.  And I’m not convinced the net needs one.

I still hope to do that major rewrite, but this should bring it mostly up-to-date.

*Deactivated January 2023

Posted on
by

Rather than looking at campaigns for specific browsers, I’m looking at a class of campaigns that are either promoting a group of browsers, or advocating against the current dominant player: Internet Explorer.

Browse Happy — the classic.

  • Goal: Move users away from Internet Explorer.
  • Target Audience: IE users.
  • Promotes: Firefox.  Also Safari, Opera, and… um… Mozilla.  Hmm, someone needs to update that.
  • Pitch: IE is dangerous.
  • Method: Banners

Alternative Browser Alliance

  • Goal: Keep multiple standards-compliant browsers viable.
  • Target Audience: All users
  • Promotes: Opera, Firefox, Safari.  Also Flock, SeaMonkey, K-Meleon, Camino,etc.
  • Pitch: Competition is good for everyone.  See what’s out there.
  • Method: Banners

End 6! (end6.org)

  • Goal: Move people off of IE6
  • Target Audience: IE6 users
  • Promotes: Firefox, Opera, Safari, Flock, IE7
  • Pitch: IE6 is outdated, buggy, and unsafe.  Use something modern instead.
  • Method: Overlay for IE6 visitors

Save the Developers (savethedevelopers.org)

  • Goal: Move people off of IE6
  • Target Audience: IE6 users
  • Promotes: IE7, Firefox, Safari, Opera
  • Pitch: Coding for IE6 is a pain.  Stop putting us through that.
  • Method: Animated drop-down at top of page for IE6 visitors

(Yeah, I’m catching up on old draft posts.)

Posted on
by

After several years of inactivity and a quiet relaunch earlier this year, the Dillo web browser has finally released Dillo 2.0.

The open-source project started in 1999 with the goal of creating a small, fast, highly efficient graphical web browser that could run well even on low-end hardware and software. It’s a UNIX application, and runs on Linux, BSD, Solaris, etc. Things stagnated when it became clear that GTK1 was going to vanish, and GTK2 would not fit the project goals, and eventually the browser was ported to the Fast Light Toolkit (FLTK).

If you’ve used Dillo before, some of the improvements in this release are multiple character set support (the old versions were Latin-1–only), tabbed browsing, HTTP compression, anti-aliasing, improved rendering and UI, and smaller(!) memory usage.

It does have its limitations, and a few major items stand out as missing when compared to other modern browsers:

  • No CSS stylesheet support.
  • No scripting.
  • No plug-ins.
  • Limited SSL support.

That said, it’s useful to keep around on an older system, or for situations where speed is more important than rendering, or to test how a website works without styles, scripts, and plugins.

I started building RPMs of Dillo for my own use back in 2002, and became the official RPM packager for the project the following year. I’ve posted Dillo RPM packages for Fedora 9, RHEL 3, RHEL 4, and RHEL 5. Other distros will have to wait until I get my build system out of storage or figure out how to convince mock to let me build two packages together.

Posted on
by

Now that it’s live, I’ve downloaded the Google Chrome beta on my Windows box at work.  Thoughts so far:

Good:

  • Site compatibility seems to be fine so far, with a couple of minor issues (see the “Bad” section).  Mostly I’ve tested it with a couple of forum sites, LiveJournal, Slashdot, and WordPress.
  • I like the simple settings box, with “Basics,” “Minor Tweaks,” and “Under the Hood.”
  • It does feel fast.
  • Showing the URL of links in the lower left-hand corner is a perfect compromise between the spatial advantages of a permanent status bar and the extra room provided by leaving it out.
  • I like the task manager for the browser itself.  It’ll be good for developers, but it’ll also be good for users: as the comic points out, if your browser starts chewing up all available resources, you’ll be able to tell what page/plugin/program is at fault instead of just blaming the browser.

Bad:

  • Gears support doesn’t seem to work quite right.  WordPress.com doesn’t detect that it’s available.  Local WP installs with Bad Behavior can’t sync completely.  (It doesn’t send an Accept header on the request for one of the TinyMCE files, which causes Bad Bahavior to think it’s a spambot and triggers a 403.)
  • Cookie management is too simplistic.  I like to accept all cookies temporarily, but clear everything when I end my browsing session, with exceptions for sites where I want to stay logged in.  This is easy in Firefox, a little trickier in Opera, and doesn’t seem to be an option in Chrome.
  • I have seen it pause a couple of times, with as few as 5 tabs. [edit: these seem to be related to Flash content]
  • No Incomplete spell-check.
  • I keep hitting the forward-slash key to search within a page, since that’s the shortcut I’m used to in Firefox and Opera.
Debatable:
  • The UI does indeed stay out of your way.  I guess this sort of makes Chrome the Anti-Flock.
  • DNS Pre-Fetching is enabled by default.  This is different from full HTTP pre-fetching in that all it does it look up the IP addresses of the links that you might click on.  It’s not clear at what point it does this — I don’t remember seeing it mentioned in the comic, which (ironically) isn’t searchable.  I suppose it could either hit the domains of all the links on a page, or just those that would trigger HTTP pre-fetching, or even just send the query when you hover over a link (to get a split-second head start before you click). Update Sep. 17: Google has a blog post explaining pre-resolving in detail. Apparently it does check the domains for all the links on the current page.