Thursday, January 29, 2009

Lunascape 5.0 rc Released in Japan: Speed, speed, and more speed!

The latest Japanese version of Lunascape was released in Japan on January 27th, boasting breakneck speeds, lower CPU usage, and higher overall stability. In general, over 30 new features and bug fixes were added.

Do you care about speed? If so, this release is for you. And, yes, you'll need to be able to read some Japanese, too. But never fear. The global version, meaning the version in English, is right around the corner. You can test the alpha version here. (

For now, consider this a taste of what's possible.
For Javascript, when using the Gecko engine in Lunascape5.0 rc, compared with either Firefox3.1Beta2 or Google Chrome2.0.157.2, Lunascape comes out ahead as shown in the following SunSpider Javascript Benchmark test. The benchmark was conducted on January 23, 2009, Windows Vista Enterprise SP1, HDD 60GB, Intel Celeron M processory 420 (1.60 GHz) with 1GB of memory.

If you have any questions, feel free to leave a comment here, talk to us on our Twitter account ( or through our website,

More information coming soon.

Tuesday, January 27, 2009

Navigating the Browser Wars: Freedom FROM Choice

At Lunascape, we've been excited about building a fast, flexible, easy-to-use browser since we started coding in 2001 (founded company in 2004). 10 million downloads later and we still feel like we're learning new things every day. But browsers have become, more than ever, the center of many users’ computing life, and we're excited to be part of this part of the software industry.

Have you noticed? If your browser disappeared, or somehow wasn't functioning, how much work could you get done? Some? None? It has become a core technology in your life, along the lines of a telephone. Don't believe me? Try setting up your next business trip to Tokyo without using a browser.

Such a core function should not be co-opted by one company. Browsers must not become like the balkanized cell phone industry in the US, focusing on company territory, neglecting innovation, and innovative technologies. Browsers should be judged on the best code, the fastest test scores, the most interesting use of Internet technologies.

Let's talk about the technology in a browser for a minute. At the core, there is a rendering engine for the browser. The rendering engine is software that takes marked up content such as HTML, XML, image files, and formatting information such as CSS and XSL and displays the content on the screen. It renders all the various parts of a web page properly, in other words. Doing that quickly and efficiently is important.

There are three main rendering engines. Trident, the rendering engine from Internet Explorer, is used by many applications on the Microsoft Windows platform to render HTML, including the mini-browsers in Winamp and RealPlayer. Gecko, the Mozilla project's open source rendering engine, is used by a variety of products derived from the Mozilla code base, including the Firefox web browser. Same goes for WebKit, originally from Konquerer, and currently best known as powering Apple's Safari and Google's Chrome web browsers.

Which is best? Good question. We're not here to try to convince you to use one technology over the other. You should have the freedom to decide.

The problem is, people are already tending to argue which is best based on the company that's producing them, not the technology that’s in them. We're fans of Windows, though many people use IE because it comes installed on Windows. We're fans of open source, too, but that shouldn't be the only qualification for deciding whether you use a browser or not. Is that a good way to choose your most important piece of software?

At Lunascape, we're not pushing one over the other. The Lunascape browser includes all three. You choose. You always have the freedom to choose (you might even say the freedom from having to choose). No more web sites that don't work cause you're using the "wrong" browser. Each of the rendering engines has its good and bad points.

So how are the rendering engines different?

Trident is the engine of the world’s most popular browser Internet Explorer. Not surprisingly, websites around the world are designed to properly display when viewed in IE. However, a lot of W3C guidelines are ignored, and Trident's scores in Acid3 tests are extremely low. Another negative, as the most popular browser, IE is often attacked by hackers, so from a security point of view there's a little bit of worry. On top of that, in comparisons to Gecko and WebKit for handling Javascript, it's slower, and this is noticeable with web services like Gmail.

Extremely fast for handling Javascript. However, for sites designed for Trident, there can be problems with display and there's the possibility of bugs when entering data into forms. In other words, for a country like Korea that embraces IE, there's not much room for users of Firefox (Gecko).

Very fast, runs Javascript at the same speeds as Gecko. It also was the first engine to get a perfect score with the Acid3 test. And just like Gecko, there can be display problems with sites that are designed for IE. Sometimes there are issues with menus, for example.

There’s a quick summary. Obviously that are many issues on technical, aesthetic, or philosophical grounds. We’d love to hear back from you which you prefer and why.

We've heard it said that the next operating system wars will be on browsers. We've heard it said that the next platform play is on mobile. Heck, we've read that operating systems are irrelevant. All that breathless predicting makes us think that, well, that you can't predict next what people will predict.

We're going to focus on building great software. We'll let someone else do the predicting. We think you should do the choosing.