Linked by Eugenia Loli on Sun 19th Sep 2004 09:23 UTC
Internet & Networking A few days ago we read about the Deli Linux, which aims to fill-in the gap of Linux distros in the 486/586 machine range by running lightweight/older applications. The disto comes with Dillo and Links as its browsers, but I bet there aren't many people who know that there is yet another very lightweight browser for GTK+ 1.2.x and it is more powerful and more memory-optimized than Dillo: Access' NetFront. Check for info and screenshots inside.
Permalink for comment
To read all comments associated with this story, please click here.

The question is not open-sources or Proprietary

NetFront is surprisingly a better propriatory browser for old i(x)86 computer. Wich is interresting, considering that the industry is looking towards: newer is better and bigger is better.

I never used it, up to now but, if the license software agrement is nice, i will.

The real purpose of theses browsers is to surf the web, no matter how.

Reusing old computer is nescessary, Economically or mostly environmentally.

So all browsers named here have their own purpose... i mean use. In wich they excel.

Say dillo is: Very quick on anything that has a cpu at the expense of being html only, but still render image. Which mean less complexity, and mostly more security.

Say links is: A very good text based browser wich have the most modern rendering.

Say lynx, w3m, debris are: Very good for their purposes...terminal works. Under X11R? or not.

With all of them you can see images through X and "xli %s".

They are all good for slow computer...

>Yes, Mozilla on IRIX (on my SGI Indy) works nice but is too slow. But Dillo is not much faster here (I have no idea why) :-(

The sgi indy is pretty old for a computer and mostly the X server is damn slow, because the port doesn't get much attentions.

Take the sgi R5000 and try browsing in a terminal (no X) with links-ssl and aalib . Oh It is quick again.... You can even use the spare cpu time to listen to music or .... even a server

Somewhere in the article it was said that dillo use a lot of memory. see the .dillo/dillorc for :

# Dicache is where the Decompressed Images are cached (not the original ones).
# If you have a lot of memory and a slow CPU, use YES, otherwise use NO

Charles ;-)