Slashdot Mirror


Meet Uzbl — a Web Browser With the Unix Philosophy

DigDuality writes "Dieter@be over at Arch Linux forums, a release engineer for Arch Linux, got inspired by this post. The idea? To create a browser based on the Unix philosophy: 'Write programs that do one thing and do it well, programs that work well together, programs to handle text streams because that is a universal interface,' among other points. The result? A fast, low-resource browser named Uzbl, based on WebKit, which passes the Acid3 Test with a perfect score. The browser is controlled (by default) by vim-like keybindings, not too dissimilar to vimperator for Firefox. Things like URL changing, loading/saving of bookmarks, saving history, and downloads are handled through external scripts that you write (though the Uzbl software does come with some nice scripts for you to use). It fits great in a tiling window manager and plays extremely well with dmenu. The learning curve is a bit steep, but once you get used to it, it's smooth sailing. Not bad for alpha software. Though built for Arch, it has been reported to work on Ubuntu."

48 of 318 comments (clear)

  1. Really fun browser by Minozake · · Score: 3, Interesting

    This is a really fun web browser to tinker with. However, I'd recommend people should use a backup browser until they get it up and functioning to their specific needs. I'm still trying to work around with the cookies scripts, myself.

    --
    http://sourcemage.org/ - Have fun :)
    1. Re:Really fun browser by Bigjeff5 · · Score: 4, Interesting

      You missed the part about the Unix philosophy, which is "Do one thing, and do it well". It browses the web, apparently very very well. But storing cookies for later use isn't really browsing, now, is it? Neither are favorites or bookmarks or history and all that. If you want that stuff, you have to write scripts for it.

      Neat idea, I'd never use it though. Too lazy.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
    2. Re:Really fun browser by Kjella · · Score: 4, Interesting

      You missed the part about the Unix philosophy, which is "Do one thing, and do it well". It browses the web, apparently very very well. But storing cookies for later use isn't really browsing, now, is it? Neither are favorites or bookmarks or history and all that. If you want that stuff, you have to write scripts for it.

      Until you want to implement something like a privacy button. It needs to clear the disk cache. It needs to clear the cookies. It needs to clear the autocomplete for the navigation bar. It has to delete the page history. But you don't want it to nuke your bookmark database, so you can't just make a "purge all". What's one thing for the user isn't one thing for the developer, which is why you end up building monolithical applications.

      --
      Live today, because you never know what tomorrow brings
  2. And the UNIX philosophy is... by wampus · · Score: 5, Insightful

    Worse is better!

    1. Re:And the UNIX philosophy is... by Brian+Gordon · · Score: 5, Insightful

      Even if few people use it, the world's always better when someone writes an interesting app.

    2. Re:And the UNIX philosophy is... by wizardforce · · Score: 2, Insightful

      how is designing software to do more things badly superior to focusing on creating software thatdoes its one and only job better? The more things software is asked to do the higher the chance that it will do at least some of those things poorly.

      --
      Sigs are too short to say anything truly profound so read the above post instead.
    3. Re:And the UNIX philosophy is... by DigDuality · · Score: 4, Informative

      what the fuck does OS X have to do with any of this? This was a conversation about browsers, i'm sure uzbl can run on OS X just as well as on Linux. Jesus you Mac tards are fucking assholes who just jump at the fucking chance to jam your feng shui tonka toys down peoples throats whenever you're not sipping on a fucking latte.

    4. Re:And the UNIX philosophy is... by Abcd1234 · · Score: 2, Insightful

      Dude, we're in a world of shitty phones that are also shitty music players, shitty still cameras, shitty video cameras, and shitty PDAs. And you're surprised that people don't understand the idea of a well-designed, single-function device?

    5. Re:And the UNIX philosophy is... by wizardforce · · Score: 3, Insightful

      if some people want a simple browser as bare bones as this one they can use it, if other people want more than that they can use other browsers.

      --
      Sigs are too short to say anything truly profound so read the above post instead.
    6. Re:And the UNIX philosophy is... by Blakey+Rat · · Score: 3, Insightful

      how is designing software to do more things badly superior to focusing on creating software thatdoes its one and only job better?

      And what's the "one thing" a web browser is doing, exactly? In the last week, I've used a web browser to:
      * RSVP to a event invite
      * Send/receive email
      * Watch TV shows
      * Share photos with relatives

      A "do one thing and one thing only" philosophy is fundamentally incompatible with the web. Unless you define your "one thing" as "view the web," which is so all-encompassing as to be useless.

    7. Re:And the UNIX philosophy is... by A+beautiful+mind · · Score: 3, Insightful

      You are thinking on the wrong abstraction level.

      A browser should implement HTML4/5, various XHTML versions, Javascript, support various multimedia protocols and that's it. Everything else can be integrated as a plugin.

      The Unix philosophy would demand separation of the code that implements all of this from the actual UI.

      --
      It takes a man to suffer ignorance and smile
      Be yourself no matter what they say
    8. Re:And the UNIX philosophy is... by MadnessASAP · · Score: 2, Funny

      Trolling troll is trolled.

      --
      I may agree with what you say, but I will defend to the death your right to face the consequences of saying it.
    9. Re:And the UNIX philosophy is... by Anonymous Coward · · Score: 2, Insightful

      Why should the rendering engine have to implement JavaScript or a multimedia protocol? A real Unixish browser would be composed of one component that only renders HTML, another one that fetches files and caches them, plug-ins to implement scripting languages and multimedia, and a shell that wraps everything in a GUI to manage bookmarks/history.

      In other words, it would be implemented like IE.

      dom

  3. Browser name should be changed by DiamondGeezer · · Score: 4, Funny

    I suggest NUZBL.

    --
    Tubby or not tubby. Fat is the question
  4. Web Browser? by RalphSleigh · · Score: 3, Insightful

    So it's not a web browser, but rather a HTML rendering widget you can use to write a web browser, or use in other programs? I think .NET has one of those based on the I.E engine...

    --
    Come as you are, do what you must, be who you will.
    1. Re:Web Browser? by Trepidity · · Score: 3, Insightful

      It's somewhat in between, like most Unix-style tools. It's usable as-is as a basic web browser (you can browse the web in it). It's also usable as a tool to build other things out of, but in the "app that other apps can talk to" sense, not the .NET or Java "a class library that you can link your apps to" sense.

      It's partly a philosophy of general- versus special-purpose end-user programming, monolithic vs. interlocking-parts design, etc. No real right answers, but I see a space for this. In particular, those of us who like a particular window-manager approach, and heavily use its scripting, have long complained that the web is sort of a black box out of our reach--- either you make do with what you can do with wget or links or something, or you've got to relinquish control to Firefox. Sometimes you really do just want a one-window X11 app that renders a modern web page.

  5. vi? by clang_jangle · · Score: 4, Funny

    I'm very tempted to try it, but it has those nauseating, voodoo-like vi keybindings. What's wrong with using the sweet and pure emacs keybindings? Well, I'm going to go take a look now and see if that's configurable.
    MODERATOR HINT: I'm guilty of attempted humor, not flamebait.

    --
    Caveat Utilitor
    1. Re:vi? by clang_jangle · · Score: 5, Informative

      Oh wow, now I've gone and looked at it and it's really cool! It's a collection of python scripts, so it should run on pretty much anything. And yes, keybndings (and most everything else) are easily reconfigured -- if you know python.

      --
      Caveat Utilitor
    2. Re:vi? by Anonymous Coward · · Score: 3, Informative

      There's no constraint that says you need to use python. You can you /any/ programming language that can read/write text files.

    3. Re:vi? by FlyingBishop · · Score: 2, Funny

      I'd be happy to help, but AC, you have an annoying fickleness. I'm not really sure I can trust you to follow through.

  6. Re:Reinvent the browser again? by Brian+Gordon · · Score: 4, Insightful

    The goal isn't to gain popular market share.

  7. Re:Reinvent the browser again? by retchdog · · Score: 3, Insightful

    I don't think they're looking for standard users, and kind of the whole point was to create a learning curve. This implies that it's targeted at powerusers and developers. With the script-integration, this could be useful for quickly churning out a limited-use kiosk with a few helper apps or something (e.g. a novelty photo booth with web integration).

    Anyway, the price is right.

    --
    "They were pure niggers." – Noam Chomsky
  8. Yes, but by mujadaddy · · Score: 2, Interesting

    Does it run on Windows?

    --
    Populus vult decipi, ergo decipiatur...
    "Force shits upon Reason's back." - Poor Richard's Almanac
  9. "The Unix Philosophy" by 93+Escort+Wagon · · Score: 4

    The learning curve is a bit steep...

    Yup, say no more - that's the Unix philosophy in spades.

    --
    #DeleteChrome
    1. Re:"The Unix Philosophy" by DigDuality · · Score: 4, Insightful

      it has been my experience that everything regarding steep learning curves in *nix, ends up revealing benefits those who never try will never know of. Try explaining to the average windows user how vim is better than notepad vs watching someone learn vim and having their face light up everytime they figure out they can do something very quickly that's impossible in a standard text editor

  10. Re:Reinvent the browser again? by causality · · Score: 3, Insightful

    Novel ideas usually don't live on by themselves unless they become useful. The worst thing the developers did (besides the name) was create a "steep learning curve" for the common web browser. The best thing the developers could do is work with an existing product that already has market share and works great like Chrome (also based on Webkit) and make their additions to it in support of better key bindings.

    That depends on whether the goal is to obtain the largest possible marketshare. If that is the goal, or if that is your sole definition of "useful," then what you say does apply. If they don't give a damn about competing head-on with the likes of IE or Firefox then what you say is completely irrelevant. What I don't understand is the (usually) unstated assumption that marketshare numbers are the only reason why anyone creates any piece of software. While it's important in terms of attracting developers and, in the case of browsers, for putting pressure on Microsoft to make IE more standards-compliant, there are many reasons why someone might write a browser and this includes reasons that wouldn't personally motivate you.

    I see the same sentiment shown when some people discuss Linux as though its only purpose is to compete with Windows. They then act like Linux is a complete and utter failure if it doesn't bust up the Windows desktop monopoly. I disagree with this; Linux just "is." If it happens to displace Windows, that's great. If it doesn't, that's fine with me too. Though I have happily introduced folks to Linux who showed an interest in it, I'm not out to win converts; I just want something that works for me. There are those of us for whom Linux is a good solution, who have no dependency on any Microsoft products, and who are able to do our computing completely aloof from Microsoft, unaffected by any decision Microsoft makes. It's abundantly possible that this is intended to be a niche browser, designed for the relatively small number of users who are technically inclined and willing to tinker with something like a Web browser and its supporting scripts.

    --
    It is a miracle that curiosity survives formal education. - Einstein
  11. Re:Could use a better name by Bambi+Dee · · Score: 3, Interesting

    It's pronounced "useable", I suppose?

  12. Re:Reinvent the browser again? by s4m7 · · Score: 4, Informative

    but you could say the same about the Chrome developers

    Ahem. Chrome was based on webkit which was derived from the Konqueror browser for KDE. Maybe not a huge market share but probably in the hundreds of thousands of users globally at the time.

    and I guess we could say the same about Firefox..

    Firefox was based on mozilla which was the open sourced version of the venerable and at one time market-dominating Netscape Navigator.

    No, it doesn't matter if the browser has useful features to YOU. it matters if they are useful to someone. And apparently someone out there wanted a modular browser with vi keybindings out there bad enough to write the damn thing. If it's not for you? Don't use it.

    --
    This comment is fully compliant with RFC 527.
  13. Nitpicks by SanityInAnarchy · · Score: 4, Interesting

    I like the idea, and I'd love to play with it a bit, but there are a few stupid design decisions:

    Why don't you just use a reasonable config by default?

    There really is no excuse for this. I mean, yes, I can understand where not everyone would want that "reasonable default", but that's why it's a default.

    We don't want to store anything "automagically" in the users home. Some people prefer different file/directory layouts

    Uhm... ~/.uzbl? How difficult is that? And if you don't like it, rm -rf ~/.uzbl!

    Or just create an example script that sets up the default config, and put it in your FAQ.

    We considered the option of having a global '/etc/uzbl' which user specific ones could override but that would overcomplicate things.

    I'm sorry, but even mplayer is officially friendlier than uzbl. How the fuck is it "complicated" to read one config file, then another?

    Uzbl itself doesn't use much gtk stuff (only the statusbar) so we could do without gtk. But Webkit needs a widget toolkit to create widgets (think javascript popups, html forms etc). Officially, it also supports QT and wxwigdets.

    So, why doesn't uzbl also support these options? I'm using KDE, so Qt makes sense.

    Uzbl.run( )
    command is any uzbl command as defined above
    return value: a string, either empty or containing the output of the command. Very few commands return their output currently, including js, script, and print.

    They obviously realize that JS runs in a single thread. So the obvious implementation here would be to use a callback, not a return value, so you don't block the entire page while you run that script.

    I mean, I want to like it, but that's a number of facepalms right off the bat, so I think I'll stick with Chrome until I have time to fix them.

    --
    Don't thank God, thank a doctor!
    1. Re:Nitpicks by martin-boundary · · Score: 2, Insightful

      It *is* preferable to have a separate ad-blocker, that should be a no-brainer within the unix philosophy. What you're thinking of is a client/server model where right clicking the ad in the UI (which UI? Maybe there could be several to choose from) should initiate a conversation with the ad-blocker daemon.

  14. 50 tabs? by ArchieBunker · · Score: 2, Funny

    What are you doing that requires 450 or even 50 tabs for that matter? You sound like an RMS nutjob.

    --
    Only the State obtains its revenue by coercion. - Murray Rothbard
  15. dupe! by CODiNE · · Score: 3, Interesting

    http://slashdot.org/article.pl?sid=98/02/24/114700

    11 year old dupe article.

    Hmmm... as an aside... wonder why no posts there.

    --
    Cwm, fjord-bank glyphs vext quiz
    1. Re:dupe! by armanox · · Score: 2, Informative

      Because the discussion system didn't exist back then on Slashdot?

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    2. Re:dupe! by Trepidity · · Score: 4, Informative

      It did--- Slashdot's had a discussion system since the beginning (or at least very close to it). Pre-account-system comments aren't archived, though, it seems. You originally just entered a name and a comment and posted it, the way most blog comment sections still work today. Impersonation of well-known users was getting too common, though, so they introduced an account system in mid-1998, requiring that you either post as Anonymous Coward, or register an account to post as anyone else. It seems that the old stories only archive comments made after that switch, so the pre-mid-1998 comment threads are mostly in the bitbucket, except to the extent that the Wayback Machine got them.

  16. It's Webkit by PhunkySchtuff · · Score: 4, Informative

    This browser is simply a wrapper around Webkit - so things like passing Acid3 with a 100/100 score is something that it inherits by default. It's not like the developers of this project did anything in particular, other than chose to use Webkit, to make it pass Acid3 or be standards compliant in other areas...

    As mentioned above, Webkit isn't the most unix-like unix software being a big, monolithic program written in C++ .

    All this project does is wrap a purposely obtuse front-end around a popular, open source browser engine.

  17. wget? by Joe+Mucchiello · · Score: 2, Interesting

    If it does more than wget, doesn't that mean it already has too many features?

  18. But that's a faulty comparison by Sycraft-fu · · Score: 2, Insightful

    Notepad is, and was designed to be, an extremely basic text editor. It doesn't have lots of features not because those would necessarily make it hard to use, but because they'd take resources to develop. It is just a simple program to display a text file, little more.

    Now compare Vim to something like UltraEdit. Here you have a tons of features. Maybe even more than Vim has. However it is still simple to use the basics. You can fire it up and open up a file and edit it with no more effort than notepad. It is easy to do the simple stuff.

    The real mark of well designed complex software is where the learning curve is variable, meaning it is only as steep as it needs to be for a given thing. Simple lings are easy to learn, more complex things are harder. You don't have to bash your head against a wall learning all sorts of complicated things to accomplish the basics. The complex capability is there, but it doesn't interfere with simple stuff.

    That's why something like Vi fails to impress me. When I got my current job, I had to learn about it, since it is the only text editor that comes with Solaris by default. I was annoyed with it as it is the first and only text editor I've ever encountered that I couldn't edit text in without a manual. I tried to use it, and couldn't make it work. Our Solaris guy had to show me how it worked. He, like you, seemed to assume I'd love it once I learned about it because of its power. I challenged him to show me something it could do that UltraEdit couldn't. He wasn't able to come up with anything.

    The real challenge to good software is to make things as easy as possible, and make it so the complicated doesn't interfere with the simple.

    1. Re:But that's a faulty comparison by Trepidity · · Score: 5, Insightful

      I challenged him to show me something it could do that UltraEdit couldn't.

      How about use it to edit a remote file over ssh, from an Android phone? Or do complex things without using the damn mouse? Or write macros in a usable macro language?

      More generally, with commonly used software, some of us just don't care about the learning curve. With the tools I use daily, I don't even remember what the first hour of using them was like, because it was so many thousands of hours ago. I even find it interesting to learn about new ways of doing things, so I don't resent an hour or two of getting up to speed, even if I don't end up using the tool. I could see if I had to learn a new tool an hour before a deadline I'd be annoyed, but the simple solution to that is not to schedule your new-tool experimentation an hour before a deadline. =]

    2. Re:But that's a faulty comparison by Al+Dimond · · Score: 4, Insightful

      OK. So Vim isn't the ideal editor today -- it was designed around limitations of earlier computers and when you remove those limitations you can get rid of stuff like modality that's not really necessary when you have a mouse. So lots of people get attached to modality and hjkl navigation because they spent time learning them, just like people get attached to the emacs OS, even though neither are, today, what anyone designing a new editor would make. They are historically notable -- both were more powerful and easy to use than what came before. I don't think either is very Unixy -- they're each platforms unto themselves at this point. Whatever the first Notepad-like editor was, that introduced the basic elements we consider to be standard text-editing controls today, is definitely historically notable also, and a great achievement -- it flattened the learning curve and (mostly) shattered modality.

      Vim and Emacs don't have a lot to do with this browser project, despite the red herring of vi-like keybindings. This project is an experiment about building a browser that's really part of Unix, so as far as an analogous editor goes, perhaps Plan 9's acme, which also relied on external scripts for much functionality. The point isn't to be the greatest or most impressive anything, because... really, who cares? The point is to be a useful tool within the Unix system. If a more self-contained browser is easier to use in many cases that doesn't make it useless.

    3. Re:But that's a faulty comparison by Draek · · Score: 3, Insightful

      The real challenge to good software is to make things as easy as possible, and make it so the complicated doesn't interfere with the simple.

      When they're designed for ease of use. When they're designed for *efficiency*, however, as ViM is, the challenge is to keep the complex possible while making the simple as fast as you can. How easy it is to learn never enters into the equation.

      The editor designed for *power* is Emacs, whose LISP interpreter can't be beat in that department.

      --
      No problem is insoluble in all conceivable circumstances.
    4. Re:But that's a faulty comparison by petrus4 · · Score: 2, Insightful

      Some of us have better things to do than be computer dorks, we grew up, have families and other priorities and likely a higher quality of life than those of you glued to your crappy hard to use editors.

      Yes, because having a wife, kids, a mortgage, and probably a 16 hour a day job is definitely going to be less stressful and better for your health than living alone, without all that extra weight.

      There is no better or worse, my friend. The grass is always greener...

    5. Re:But that's a faulty comparison by shutdown+-p+now · · Score: 2, Insightful

      How about use it to edit a remote file over ssh, from an Android phone? Or do complex things without using the damn mouse? Or write macros in a usable macro language?

      You make requests in a way that predetermines the answer. For example, what's a "usable macro language"? And, obviously, there's no Notepad (or UltraEdit) on Android, but a clone could be easily written, and yes, it could also work over ssh - there's nothing specific about Vim design that enables it to work better over ssh than any other text-mode editor.

      At the same time, any decent editor these days lets you do fairly complex things without using mouse. Even though for a large number of such things, using a mouse is actually faster than trying to concoct a cryptic Vim command that would have the same effect - that's because mouse was designed to solve certain tasks well, normally those involving dealing with selection and highlighting in 2D space, and thinking that keyboard can beat it at that with equal amount of training is simply delusional.

    6. Re:But that's a faulty comparison by shutdown+-p+now · · Score: 2, Insightful

      When they're designed for *efficiency*, however, as ViM is ...

      Vim commands weren't designed for efficiency; like traditional Unix command names, they were designed for terseness to remain usable over slow (think 300 baud) terminal connections.

  19. Re:Reinvent the browser again? by techprophet · · Score: 2, Insightful

    "The guy had an itch and he scratched it, there is nothing wrong in that. Not everything that is made has to be useful."

    That's true, and so is the fact that Uzbl is about as attractive and useful as a dirty stranger scratching an itch.

    A www browser controlled by vim-like key bindings? Well that isn't unique, there are other browsers which do that already, in fact you can do that even with Firefox or Opera, as well as some of the console based browsers. It's the kind of throwback 'feature' that excites impressionable students, idiots, and people who write desperately bad distro/free software reviews where they claim they "fall in love" with "wonderful" "awesome" "elegant" "smooth" "integrated" applications and distros (visit LXer.com for acres of that kind of inane verbiage).

    The point was not to have vim-like keybindings. They can be changed easily. That is the point. Change is easy.

    And the UNIX philosophy is "do one thing and do it well", not "duplicate something badly for no useful purpose" (c'mon, everyone knows that's the Arch philosophy).

    You, sir, are the biggest fucking idiot I have met all day.

    It doesn't dupe FF, IE, or Chrome. It displays web pages. That is ALL. Firefox displays them in tabs, along with having bookmarks, skins, downloads, and addons. All internally! IE has nearly as extensive a list (no skins) While Chrome does it with just tabs, downloads, and bookmarks. None of those things are necessary. I like slim. Slim is good. Uzbl is slim. Firefox is not. IE is not. Chrome is not. If you disagree, keep using IE/FF/Chrome. I don't want to.

    It, actually is very attractive. Very, very attractive.
    *runs off to play with Uzbl wmii scripts*

  20. Re:New name by techprophet · · Score: 2, Interesting

    It's not being marketed. At all. STFU and go back to Firefox. This isnt for the masses. It's for us geeks who like slender forms.

  21. I thought that would be called "Emacs"! ;) by Hurricane78 · · Score: 2, Interesting

    On a more serious note:

    Why is it, that all the GUI desktops abandoned Unix's philosophies completely and instead went the Windows way (which of course actually is the MacOS/Xerox/$otherProductItGotTakenFrom way)?

    I mean, imagine how great it would be, if we had all the tools of Gimp, Openoffice, Firefox Add-ons, etc, as separate entities, only bound to a document / data trough its mime type. You could mash up and reconnect everything at will. Pipe stuff trough that wizard, and then trough that.
    Or connect a OOo tool and a Gimp tool trough pipes, and then draw with them, etc.

    Imagine it like this:
    - A global toolbox with all the
        - tools (something you "draw" with),
        - wizards (something that you apply to the selection/document) and
        - views (a view and controller for the model [file]).
    - A window for every view of a file.
    - A location bar, showing the current position/selection as an XPath.
    - A properties box, showing all the properties of the current element/selection.
    - The things in the toolbox would itself be normal files -- scripts or libraries implemented in every language with an API for it to be exact -- that you could show in views, edit with the properties box, apply wizards and tools to, etc.
    (Yes I got to this ideas a long time ago. I just got no time or money to implement it. If you do, please tell me. )

    You could build your own tools like with shell scripts. And because that would make it much easier to create new apps by slowly growing them, we would get much more innovation.
    Also it would pose no problem for those noobs who dislike the shell for no reason. :)

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
  22. Re:About damn time by harry666t · · Score: 2, Informative

    > Have you ever had a few hundred applications open at once like that? It
    > doesnt work there either. I will wait while you try it in unix or windows
    > with say paint. You will quickly see what I mean.

    Soooo, just for the kicks, I held Mod4+Z (my keybind to open an urxvt) for a couple of seconds, waited for all the windows to appear, and issued "ps aux|grep urxvt|wc -l". Over 200 terminals + one zsh for each. System load went from about 0.2 to about 5.8, then quickly dropped down and has been around 0.4 now for a couple of minutes. The system feels fully responsive (although changing back and forth from/to the virtual desktop on which the terminals are takes a slight moment). Total memory consumption went up from about 700mb to about 1700mb.

    Now, opening 200 terminals at once slowed the system down a bit, but only for a moment, and no kitten was killed and the WW3 didn't start. Memory is another problem, but I suppose that in such a "multi-process" web browser things like password vaults, history, bookmarks, etc could be implemented as separate daemons and only communicate to the UI what is necessary.

  23. Re:Reinvent the browser again? by Minozake · · Score: 2, Insightful

    OTOH the modal interface of vi gives an additional error source because you always have to remember if you are in insert of command mode.

    That's not the correct way to use vi. Command mode is normal mode. Never leave it in any other mode, including insert mode. Ever. Only use insert mode when you're actually inserting something.

    There's also usually a status area which tells you which mode it's in as well.

    --
    http://sourcemage.org/ - Have fun :)