Hi, just one more practical explanation of the advances the more ressource friendly fltk2 has. BTW: fltk2 does not necessarily depend on GL. Imagine you have a device with limited ressources. Running a browser bigger than dillo might be possible. Perhaps even a bigger loading time might be ok in some situations. For example if you hve only gprs to connect to the internet, then loading of many pages takes ages anyway. But in case of multitasking there is really a harder limit. If you have multiple applications running which are a bit bigger, then you really have problems when you start a fat browser. Here is an example: Just some days after I got my freerunner I started a long bicycle trip and had not find time to install dillo. On one of the first evenings I visited one or two pages. That was not so nice but bearable with the default browser really because I was not surfing very much (of course having dillo is much better). Some days later, I was abroad and I found one wifi hotspot. I had more applications open (at least my mapping program (with a hotspot list loaded) Starting the default browser has frozen the system. That is completely unbearable. In that situation having a browser with a lower ressource usage is essential. Greetings Andreas Kemnade