Category: Web Browsers

Posted on
by

OSNews reports that Dillo has released a new version for the first time in almost a decade!

Now there’s a blast from the past!

Dillo (as in armadillo) is a super-minimalist web browser for Linux and related systems that’s especially useful on low-end hardware. I used it for a while back in the early 2000s, though not as my primary browser. It was great for reading documentation, though, because it was so fast (and docs usually don’t need JavaScript (and if they do, they shouldn’t)).

I haven’t really kept up with it since 2009 or so, not long after the the major 2.0 release, but I built its RPMs for a while. First on my desktop for RHL/Fedora, then on multi-boot partitions to build for older versions and other distributions like SuSe and Mandriva, then using User-Mode Linux (an older virtualization system). I later moved the build system to an expendable frankenputer after an OS installer trashed my partition table. The last set of RPMs I built were for Fedora and RHEL back in 2009. (These days, with containers and modern virtualization, it would be *so* much easier and safer to do all on one box!)

Apparently the project stalled in 2016 after one of the main developers, Sebastian Geerken died. A few years later, lead developer Jorge Arellano Cid just stopped posting online. A couple of years after that, the domain name expired and was picked up by a spammer. (I should see if I still have any links to the old site on here and update them.)

It’s sad to hear that Sebastian passed away.

I hope Jorge is okay and just off-grid somewhere.

This year’s new project has brought it up to date with modern SSL/TLS capabilities, which is a much bigger deal now than it seemed to be in the early 2000s, as well as improved CSS support and other improvements. I’ll have to try out how well it handles today’s (static) web. I bet it’ll run great on the PineTab2!

Updates: Not surprisingly, Dillo handles Snac pretty well. It’s able to view public Snac posts/timelines and log in to my account here. But posting isn’t working.

Not so much Pixelfed or Mastodon, both of which are JS;DR. GoToSocial static pages are readable, but it’s not using any of the styles.

The new project offers plugins for Gemini, Gopher, man pages and IPFS, as well as something called Spartan that appears to be another minimalist protocol like Gemini.

And it does indeed run quite fast on the Pinetab!

Posted on
by

I never thought I’d see Microsoft throw in the towel on their browser engine. Or that, by the time it happened, I’d see that as a bad thing.

But it’s true: like Opera did a few years ago, Microsoft is dropping not only the old Internet Explorer engine, but the newer Edge engine, and will be building Edge on Chromium going forward. That means Edge, Chrome, Opera and Safari are all built on the same codebase. (Chromium split from Apple’s WebKit a while back, but they still have a lot in common.)

Monoculture is still a problem, no matter who runs it. We’re already at the point where webdevs are treating Chrome like the defacto standard, the way they did IE6 back in the day.

Firefox is going to be even more important in the future, ensuring that the web continues to be built on interoperable standards instead of one stakeholder’s goals.

Mozilla is a non-profit organization, and like many, they’re running a year-end donation drive. Now is a good time to contribute to their mission to keep the internet and the web open. (I’ve already made my annual donation to them.)

I think I may want to finally shut down or retool that old Alternative Browser Alliance site I ran during the Second Browser War. The last time I made a significant update to it, Chrome was the new upstart.

Posted on
by

Opera RingThe reporting is a bit confusing, but it looks like the Opera web browser has been sold to a Chinese consortium. The group wanted to buy the Norwegian company outright, but the bid failed, and they fell back to an alternate deal.

According to NewsWeb:

The following business units of Opera will be included in the Transaction:

· Mobile Browser, including Operator Co-brand solutions
· Desktop Browser
· Performance and Privacy Apps
· Opera’s technology licensing business outside of Opera TV
· Opera’s 29.09% ownership in the Chinese joint venture nHorizon

The Consumer Business will be reorganized into a separate company structure. For
clarity, the following businesses are not included in the Consumer Business or
the Transaction:

· Opera Mediaworks
· Opera Apps & Games (including Bemobi)
· Opera TV

It’s a shame to see Opera broken up and dispersed…but in a way, that already happened years ago. When they switched to WebKit in 2013, they lost what made them unique and (IMO) valuable: They’d been a solid third-party (well, fourth-party) that helped keep the web from collapsing back into a monopoly. Within a year the community portal was gone as well.

Since then I’ve only bothered with the desktop browser occasionally when I need to test multiple sessions at once. I used to keep a copy on my phone for times when I was stuck on a slow connection, but these days the cell network in my area is a lot faster. When it gets slow, it’s also unstable, so compression doesn’t help much.

VivaldiI think I will check out Vivaldi again, though. Founded in part by Opera co-founder Jon von Tetzchner, it started as a new home for the Opera community. When I first checked out their browser, it was a really rough preview, but it’s at 1.2 now. While it’s using Blink as the rendering engine, they seem to be trying to innovate through the UI instead, with a heavy emphasis on customizing everything.

(via Slashdot)

Posted on
by

Opera IconIt still feels like an April Fool’s joke, but Opera is in fact switching to WebKit and discontinuing their own engine, Presto.

I can sort of understand. They can stop worrying about the long-running headaches of browser-sniffing websites that assume Opera can’t do things that it can. They can focus their efforts on the features they want to add or enhance, instead of maintaining their own separate codebase.

But here’s the thing: Throughout its history, Opera has served as a check against monoculture, against a single engine dominating the web too thoroughly. And now, it’s embracing the engine that dominates the fast-growing mobile web.

Remember the bad old days when people just wrote for Internet Explorer, and there was basically no innovation in web browser capabilities? It took Firefox’s success to turn the tide, but Opera was there, needling the industry with things like the “Bork edition” which turned the tables on browser-sniffing websites. Opera was a constant reminder that no, the web isn’t just Internet Explorer and Firefox, or just Internet Explorer and Webkit, or just two flavors of WebKit. That it was worth building technologies to leverage cross-browser web standards instead of picking the current 800-pound gorilla and feeding it even more.

There’s a real value in having different engines approaching the web in different ways, because it prevents stagnation. And there’s real value in having different engines use different code, even when implementing the same capabilities, because that means when a security flaw is found in one browser, it doesn’t apply to all of them. I go into this in a lot more detail in the old, but IMO still relevant article, Why do we need alternative web browsers?

The problem, of course, is that as much as I appreciate that role for Opera, it’s never really been their goal. Opera’s purpose is to sell web browser-related services. In the past, an open web was necessary to do that. Now, they’re throwing in their lot with the front-runner instead.

That leaves Mozilla, whose mission actually is to promote an open web, to go it alone. Apple and Microsoft certainly don’t care. And Google only really cares to the extent that their services are available as widely as possible. And when you get onto mobile, all three prioritize getting you into their particular silo.

Webkit browsers are a dime a dozen. The only ones that really matter are Chrome and Safari, and Safari is a lot more important on iOS. Opera will soon be just like Dolphin, Rockmelt and others that I have to rack my brains to remember. Maybe it’ll be enough for the company to survive, but it won’t be enough to keep them relevant.

Posted on
by

Opera logo and Opera Unite logoThe Opera web browser has introduced a lot of cutting-edge features* over the years, many of which have since become standard in other browsers like Firefox, Chrome, IE and Safari. But they’ve also introduced features that didn’t catch on. With Opera 12, released yesterday, they’ve taken the first step toward removing Opera Unite and Widgets.

Opera Unite was a fantastic idea to move beyond the standard client-server model that dominates most internet activity and take peer-to-peer communication to the next level. Instead of relying on central servers like Facebook or MSN or Gmail, you could run a chat room, photo gallery or other application directly from your computer.

It never really caught on. If I were to guess why, I’d say that the big reasons were security concerns (turning your computer into a server!), the rise of easy-to-use cloud services, and the increasing move toward mobile computing. It’s one thing to let friends remotely browse a photo gallery from your home desktop that you leave on all the time. It’s another to have them view that gallery data from your iPad over your sketchy and bandwidth-capped cell connection.

As for widgets, they were sort of an odd thing to begin with: not quite applets, not quite extensions, and in competition with native widgets on both Windows and Mac OS that didn’t depend on having a browser open. (Though these days, when don’t you have a browser open?) Honestly, I’m still somewhat mystified as to why Opera created them in the first place.

Opera 11 introduced an extension system, and they’ve released a reference on converting widgets to extensions.

Widgets and Unite are still present in Opera 12, but turned off by default for new installations, and will be removed from a future release “before the end of this year.”

*I still disagree on the issue of tabs, on the basis that a tabbed interface is distinct from MDI.

Posted on
by

Microsoft has jumped on the ditch-IE6 bandwagon with IE6Countdown.com, following in the footsteps of such campaigns as Browse Happy, End 6, and Save the Developers.

Of course, since it’s a Microsoft-sponsored campaign, it’s only promoting upgrades, rather than promoting an upgrade-or-switch message.

Static HTML points out why you might want to put your effort into some other campaign instead. Because IE6 Countdown is only an upgrade campaign, and IE6 users are all on Windows XP or below (Vista ships with IE7), they can only ever upgrade as far as IE8. Given the huge gap between IE8 and IE9 in terms of standards support, HTML5, CSS3, and so forth, IE8 will soon become the new millstone around the web’s neck.

So instead of plugging IE, consider plugging your own favorite browser, be it Firefox, Chrome or Opera. Or perhaps plug another switch campaign. After all, there are quite a few alternative web browsers out there!

Posted on
by

Apparently there are websites out there that are redirecting Internet Explorer users to the Alternative Browser Alliance. This is, IMHO, both counter-productive and counter to the open spirit of the web.

For all the same reasons that you shouldn’t block visitors using Firefox, Safari, Chrome or Opera, or anything else unless there’s an actual, genuine technical reason (and unless you’re doing serious multimedia that has no fallback option, there is rarely a genuine technical reason), you shouldn’t be blocking visitors using Internet Explorer…

Because you’re not going to change them. You’re just going to make them angry.

They arrived at your site looking for something. Slapping them in the face and sending them off to another site is not going to get them to change their behavior and come back. It’s just going to make them look somewhere else for someone offering the same thing who won’t make them jump through hoops.

Case Study

Last week I received a message through the Alternative Browser Alliance’s contact form asking, “What does this have to do with cpanel?” I wanted to reply, “Nothing, why do you ask?”…but the person who asked the question hadn’t left an email address, just the name “King Kong.”

(Tip: If you want an answer to a question, give people a way to contact you!)

So I checked the server logs and saw that he(?) had arrived on the Why Alternative Browsers? page and had left no referrer. Great, another dead end.

I was ready to write it off as spam, but then I decided to search the logs for cpanel, and found several hits referred by a cpanel tutorial. I visited the page and didn’t see any links to my site, but when I looked at the source, I spotted this script:

if(navigator.userAgent.indexOf("MSIE")!= -1)
{
   window.location = "http://www.alternativebrowseralliance.com/why.html";
}

Wow. They just redirected all IE users with no explanation — not even pointing out that they were being shunted off to another website! Imagine opening the front door of a computer repair shop and walking inside to find a political activist’s office instead!

Presumably “King Kong” had searched for cpanel, followed a link to this tutorial, and found himself looking at a page about alternative web browsers. No wonder he didn’t leave a contact address. He didn’t want an answer. He was angry and blowing off steam — at me, for something that someone else did.

And did badly, I might add: Three of the five visits I could actually identify in the logs claimed to be Opera Mini, not Internet Explorer. I don’t recall whether Opera Mini can masquerade as another browser (the current Android version doesn’t offer the option, but this claimed to be an older Java version), but the desktop version certainly can. Older versions of Opera used to deliberately identify themselves as IE (with a tag adding that, no, actually it’s Opera), and would have been caught by this script!

The User-Agent isn’t a reliable indicator. It was never intended to be. If you must single out Internet Explorer for some reason, use conditional comments. That’s what they’re designed for.

If what you want to do is block IE visitors, though, think about what you’re really accomplishing. And please, don’t just silently shove the “problem” visitors onto someone else.