Linked by Eugenia Loli on Sun 17th Jun 2007 23:52 UTC
Internet & Networking "For the purpose of this article, just like the first one, a WebOS is defined as virtual operating system that runs in a web browser environement. Don't like WebOS? Well, call it OnlineOS, or WebTop if you like. So, here is a review of another 10 functional WebOS', as well as some additional similar services which show promise but aren't launched or fully realized yet." More here.
Permalink for comment 248784
To read all comments associated with this story, please click here.
wider lack of vision ...
by -pekr- on Mon 18th Jun 2007 18:53 UTC
Member since:

I think that what article shows, is a natural trend. Ppl are starting to think - cross-platform, rich-client. JAVA really badly failed here, and mainly imo turned out being a server infrastructure, although we can see some apps even for client (Azureus IIRC). But - that is just recently, whereas it was marketed as cross-platform universal language/environment which takes us into the new millenium. We all probably remember, how we hated, when some page used JAVA for menu in a browser, back in those glory Netscape 3 to 4 days :-)

Then we wanted our browser doing more and more. And even big boys from big companies missused them for the typical "You don't need to install anything, it just runs in your browser" hype. Those guys were lucky - while users would not tollerate that sluggish interface in the case of rich-app, it was pretty normal, that your website is being loaded slow on a dial-up connection, right? :-)

Well, than came Mozilla. Finally the world got at least to basic agreement to "standards" and we moved forward. That was the time, when we started to think of a browser as an universal client even more. XML based stuff was about to save us. But look at W3C, and all those tag based MLs. Well, I will be probably alone, but for me XML failed badly - I ask fundamental questions to myself - is the code more readable? Is that the style I want to code in? Does it really help to automate things? That is naive. I can see no "automatic" automatiton, there is always needed someone, who specifies how to parse data and interpret their meaning, map them to other environment. If you ever looked into stuff as WebSphere, SAP-XI and e.g. connector code, it got rudiculously overcomplicated and bloated.

So, today, I can see browser as a container, for other technologies. We will add more and more. And then we applaud things like AJAX, which should have been here from the very beginning in the first place!

That is what happens, if you lack the vision, or if you missuse stuff which was not supposed to become what it actually became. Was web initially created with distributed apps in mind? We try to fix the situation by adding other and other layers of complexity.

So, that is e.g. why I am with REBOL, and be sure I am not here to propose REBOL this time. But Sassenrath, at least for me, got a vision, of how to reduce communication complexity, in the very roots of the system. With REBOL 3 around the corner, you might actually experience it in less than a half year, especially when whole package is smaller than some of your javascript libraries :-)


Reply Score: 1