Triple-Engine Browser Released As Alpha
jcasman passes along a heads-up on Lunascape, a Japanese browser company that is releasing its first English version of its Lunascape 5 triple-engine browser. It's for XP and Vista only. There are reviews up at CNET, OStatic (quoted below), and Lifehacker. Both the reviews and comments point out that, in its current alpha state, the browser is buggy and not very fast; but it might be one to watch. "How many web browsers do you run? If you're like me, you regularly use Firefox, Internet Explorer, Chrome and Safari. Each of those browsers, of course, has its own underlying rendering engine: Gecko (in Firefox), Trident (in Internet Explorer), and Webkit (in Chrome and Safari). Today, a Japanese startup called Lunascape has released an alpha version of its Lunascape browser ... that allows you to switch between all three of these prominent rendering engines. The company says that the Japanese version of Lunascape has been downloaded 10 million times and touts it as the fastest browser available."
Lunascape supports its own plug-ins and themes...It does not, however, support Firefox add-ons, which is a real drag.
And almost certainly not even worth the look useless unless it will be able to block ads and scripts like NoScript and AdBock can. Using the english page to search the plugins reveals...nothing! Nothing at all! Okay, trying the Google translation of the original Japanese page yields 43 plugins, all related to crap like youtube and twitter...not a single ad or script blocker.
This browser is much more chindogu , than anything else.
This isn't really useful as a diagnostic browser.
There are significant rendering differences between the various KHTML/Webkit implementations (eg Apple uses its own font renderer, which gives seriously different results than most host OS renderers, and Google has provided its own viewport code which gets several things incorrect, such as the placement of background coloration on absolutely positioned bodies, which aren't as silly as they might initially sound once you look into scalable viewports.) It also misses Opera, which still has more market share than Safari on Windows, as well as a variety of small browsers.
On top of that, there's the significant likelihood that this browser injects new differences into the rendering process.
Short version? Switch if you find the browser compelling (does an, but this doesn't substitute for actual browser case testing (it neither correctly nor completely covers the playing field.)
I won't be adding it to my standard six, that's for sure. The last thing I need is another also-ran browser to check.
StoneCypher is Full of BS
How many web browsers do you run? If you're like me, you regularly use Firefox, Internet Explorer, Chrome and Safari.
What person in their right mind needs to "regularly" run 4 different web browsers? I'm a full-blown web developer, and I only use 2 browsers on a daily basis. I use Opera for the vast majority of normal browsing, references, API lookups, etc, and I use Firefox with Firebug for actual development and debugging. Periodically I test with IE and Safari, and maybe Chrome, but I would never say that I "regularly" use IE or Safari. Opera is the only browser I use where I save bookmarks, for example.
I'm having a hard time seeing where there would be an audience for a browser with 3 rendering engines. In Opera I have toolbar buttons to launch the current page in Firefox, IE, or Safari. If I want to test my page with a certain rendering engine, I'm going to launch it in that browser. I'm not interested in testing my pages with "Trident running in Lunascape", I'm interested in testing with Internet Explorer. Period. It doesn't matter if it works in Lunascape if it's broken in IE or Safari or Firefox.
And that's from a web developer's perspective, a normal user wouldn't have the first clue what a rendering engine even is and they wouldn't know when or why they would change the engine to use another one.
If you want 3 rendering engines, download 3 browsers. A single browser with 3 rendering engines is a novelty, nothing more. It is not useful as a development tool because it is not the same thing when something works in Trident vs. working in IE. IE has plenty of room to screw things up besides the engine, testing with the engine is only one part of making sure it works in IE.
How many web browsers do you run?
Like 99% of the rest of internet users, I use one browser (firefox).
I'm rather surprised this has been downloaded 10M times, unless there is some sort of patriotism based motivation going on. For the life of me I just can't picture the average internet user saying "Hey, let's see how this website looks when rendered by the Webkit engine!" while their buddy, looking on over their shoulder responds "Yeah, do it! This is going to be a blast!"
Better known as 318230.
I work for a Japanese video game company, and about a month ago we had a network outage that was traced back to the auto-update feature of Lunascape. I have no idea how many people installed it, but it apparently created enough traffic to take down our internet connection. I hope the developers have improved it by now.
Three engines, for the closest browse yet...
"Strangers have the best candy" -Me