The H3v web browser. Is it a Dillo killer?
When it comes to browsers, the Unix community is positively spoiled for choice: Firefox, Konqueror, Flock, Opera, Epiphany, Galeon, Kazehakase, Links, Elinks, Lynx, W3m and Dillo. From the minimal to the relatively bloated all life is there. You might just be thinking that we need another browser like Medieval Europe needed the Bubonic plague, but I’m always a great fan of the different and new, of people doing their own thing. Even Firefox had to start somewhere. H3v is a relative newcomer to the browser pack and it definitely falls into the “lean, mean” category. I think it deserves a little more exposure.
Most modern browsers are packed with features to work across a wide range of sites and therefore can handle Javascript, Frames and CSS as standard. Of course, you get a lot of stuff when these features are built in, but if you are security conscious and don’t want to be distracted by extraneous content when you are just doing basic search stuff, the big hitters like Firefox and Opera may be superfluous to the job. At the other end of the scale many people opt for browsers like Lynx and Links which, being text based, reveal the true speed of the internet, even on slower connections. Browsers like Dillo occupy the middle ground, giving you the graphical experience but shorn of the heavy elements that eat memory and processor power. Dillo has occupied that position for some time now and hasn’t really had any serious competition, so I was curious when I bumped into Hv3. It is built on the TKhtml3 engine which is free software; it’s written in C and has passed the W3c Acid2 test.


Browsers are changing ? Which direction to webpage standards ?
Browsers are changing big time to html webpages and motion jpeg. Webpage standardization is a must, to be able to service smartphones now and netphones later.
Browsers are mainly toolbars and taskbars. the operating system of your computer.
Then browsers differ in layout engines. Most layout engines do not comply with foobar, which made us want many webpage formats for different browsers.
This leads to the current slow down in webpage downloads. If net traffic goes up, you are more likely to get a html webpage. No subdivision of html webpage yet. But perhaps in the next few months, use vertical scroll to read many subdivided webpages like Adobe pdf pages with zoom.
Most of us suffered with the present development in webpage standardization process on the fly; some of the webpage trailer codes are not yet perfected. It is not bugs in your browser, but unification of webpage design by faulty conversion codes. Bugs are now in the webpage.
Many browsers will need final changes after the webpage standard had been established. We have to be patient.