After avoiding web programming for half a year, I'm back in it doing this diary thing for friends, and it sucks just as much as it ever did. In fact, I have come to a realization: "web programming" in its current state, must be ended. It's breaking the minds of a generation of programmers.
Olive is a far more complex program than the web app I'm working on now, but it's easier and far more enjoyable to develop, for a single reason which can be expressed in a single word: state.
Olive, being a traditional user-space app, has state information. As much state information as I want, all neatly organized in data structures of my own choosing. Web apps, as we're all aware, have no state, forcing the programmer to painfully reconstruct it via a horrible system of parameter passing and parsing, every single time the user does anything.
Someone who knows more about such things than I do needs to come up a stateful connection protocol for writing browser-embedded apps with server-side data storage. I am thinking less XMLRPCHTTPRequest (which, as I understand it, is just far more sophisticated message passing) and more constrained network-transparent virtual memory with XUL and/or HTML as a user interface definition.
The web was meant to be a collection of linked documents; let it go back to that, and let programmers go back to getting work done instead of coming up with package after package to attempt to work around the horrible pain of HTTP.