Uzbl: Lightweight webkit browser following the Unix philosophy
uzbl.org
uzbl.org
(I don't need to mention that just because you put a thin layer on top of a monstrous browser library that does all of the above, that doesn't make the scope of your program limited, right?)
The biggest selling point for me was the keyboard-centric control. I use a keyboard-centric window manager and I use vim for code editing, so everything I do on my Linux install is with the keyboard and uzbl makes web browsing keyboard based too.
[1] http://www.opera.com/browser/tutorials/nomouse/ [2] http://www.youtube.com/watch?v=YgAWfqwzxck#t=9m15s
It might not be faster than hitting one key per link, but it's more intuitive than the link-cycling all the other browsers do. Give it a shot, you might like it.
Oh.. I figured that link hinting is the way of navigating links in uzbl, so if you did not discover that (the cheat sheet lists it!) then you really missed out. As for page scrolling, hjkl does that just fine IMHO (actually, I use AltGr+u/j/k/l because hjkl is not convenient on my keyboard layout).
This works in Firefox too, if you dismiss the search box first.
Not really better than link hinting, but good enough that I haven't felt the need to find an extension that does it.
Fun drinking game: drink every time you see a github project, ruby gem, or Linux package labeled "lightweight."
Now I wonder, how can a Unixified browser combine with other shell programs in a meaningful way?
Without having tried it, I'd expect all of the controll stuff (actual browsing experience, ad blocker, bookmarker) to be written specifically for this browser. Is that correct?
Of course, if this project does not get the traction it needs from people willing to contribute (either to the code, with 3rd party scripts/programs, blogposts, ETC), then we will be stuck with programs that do not work well with other programs and turn into Windows. (In fairness to MS, powershell looks like a promising attempt to get a modern UNIX philosophy ecosystem going.)
I'm always annoyed when people don't realize that Firefox is basically Emacs: the actual engine is called XULRunner and has a renderer called Gecko and supports stuff like sockets. Firefox is on top of it, implemented basically in JavaScript and the UIs are described by the XUL format which can be compared to GTK+'s Glade-files, Qt's UI-files or XAML.