Sponsored Link •
I believe that using a typical web browser as an interface to certain online services is inherently flawed and a better separate technology is need.
I have been using SourceForge.net a lot (I just made release 2.1 of the YARD parser and release 1.0.0 of the OOTL library) and I am really frustrated with the web interface. It is very slow and complicated and lacks a lot of features. It also requires numerous other pieces of software to access advanced functionality (such as ftp, sftp, ssh, cvs, etc.). I do not believe the problem with SourceForge however is the fault of the implementation, but rather the fault of the limitations of using a web browser and http!
In the case of SourceForge for developers, the most logical choice of technology for implementing the interface is html. There are several reasons for this AFAICT:
I want to explain why I said "tolerated". If I wrote almost any piece of PC software for a client (say for the sake of argument a word processor) which had the same kind of user interface as a web site (e.g. didn't save work on crashes, pauses of multiple seconds, etc.), they would fire me. We have become very complacent with regards to web site interfaces, simply because it is the best that exists.
Any thoughts or comments? Would you like to see a new kind of interface to your online services which was easier to use for you and your clients?
|Christopher Diggins is a software developer and freelance writer. Christopher loves programming, but is eternally frustrated by the shortcomings of modern programming languages. As would any reasonable person in his shoes, he decided to quit his day job to write his own ( www.heron-language.com ). Christopher is the co-author of the C++ Cookbook from O'Reilly. Christopher can be reached through his home page at www.cdiggins.com.|