« SVG, comics and E-books | Main | Caching XML data at install time »

Build Your Own Browser

A couple of years ago, Joe Gregorio explained Why so many Python web frameworks? and showed how to create your own Web framework with a few lines of code. The most fundamental bricks are packaged in the standard python library.

There are always been many hypothesis about why the Web was successful, all of them can't be verified, because we can't restart the experiment. But retrospectively, it is interesting to look at what has been reused widely. libwww is a library including all modules to create a Web application, such as http, html, etc. It has been initially written by Tim Berners-Lee, and was freely available. People could just take the library and put an interface on top of it to make a browser, a Web server, an indexing bot.

One of the very difficult and technical parts of a browser is the layout (or rendering) engine. It takes the Web content and displays it after having processed the style and scripting information. Some of these layout engines are open source such as WebKit, Gecko and KHTML. Others are sometimes sold to third parties for developing specific products. Web developers take them and create new browsers or use them in their applications. For sure it is a tad more complicated than just taking the libraries but it became "easier" to create a browser. It is known as BYOB.

Layout engines used in different contexts

Filed by Karl Dubost on September 2, 2008 6:23 AM in HTML, HTTP, Opinions & Editorial
| | Comments (4) | TrackBacks (0)

Comments

Hristo Markov # 2008-09-08

I think that the idea to develop different browsers is not good. The main problem is that browsers would not comply with the standards and will show the pages incorrectly. Even now, the most spread browsers IE and Firefox do not meet the same standards. The problems with the differences are many - html standard, Javascript, AJAX …

I would like to give an example: Cargo Freight Exchange => for every type of browser there are developed different Javascript source code. AJAX has differences in the exchange of data. IE and Firefox do not meet the same html standards. Etc.

I think that all developers of browsers should be obliged to follow the same rules and standards. If not, I think that the development of other browsers will further deepen the problems.

Michael Lambert # 2008-09-17

A small correction:

One of the very difficult and technical part of a browser

Should be

One of the very difficult and technical parts of a browser

Karl Dubost Author Profile Page # 2008-09-17

fixing thanks.

Aaron J Anodide # 2008-11-16

I think that the idea of developing new browsers is not bad - because the forces of ROI are more powerful that cool-factor at the end of the day, so you will either:

make a browser and some people will play with it, but it won't hurt anything

or

you will innovate in some way that creates ROI

that said

you may not have made the worlds most conformant browser, but if you added a feature that helps the masses, it will naturally be consumed and incorporated.

thus

I say that making your own browser is a great way to put your mind in the state such that it is primed to innovate, and innovation is what makes the world change in good ways (in my world at least).

Leave a comment

Note: this blog is intended to foster polite on-topic discussions. Comments failing these requirements and spam will not get published. Please, enter your real name and email address. Every individual comment is reviewed by the W3C staff. This may take some time, thank you for your patience.

You can use the following HTML markup (a href, b, i, br/, p, strong, em, ul, ol, li, blockquote, pre) and/or Markdown syntax.

Your comment


About you

This blog is written by W3C staff and working group participants,
 and maintained by Coralie Mercier.
Powered by Movable Type, magpierss and a lot of Web Technology