"language_fan" <f...@bar.com.invalid> wrote in message news:hb2ov1$1jd...@digitalmars.com... > Mon, 12 Oct 2009 19:09:11 -0400, Nick Sabalausky thusly wrote: >> A different branch of the this topic started taking about (or rather, >> bashing on) web-apps-being-used-as-desktop-apps, and I mentioned I felt >> that was ass-backwards and that the focus should be the other way >> around: making desktop apps work on the web. >> > [snip] > >> And do so *without* building it on >> top such warped, crumbling, mis-engineered foundations as (X)HTML, Ajax, >> etc.? > > You have probably lived under a rock these days. This is the way the > world is moving. If something can be made Web 2.0 compatible, it is also > what will happen. A new platform might come up in 201x or 202x, but > nowadays the best we have got is Web 2.0. Ever used twitter, facebook, > google wave (or any google's services) etc. ? Large part of the online > enterprises have already jumped on the wagon, not only early adopters. > Modern browsers such as opera 10, firefox 3.5, safari, and chrome already > support the latest standards.
You're misunderstanding me. All of that is stuff that is either A. made for the web using web technologies and then brought to the desktop, still using those god-awful web technologies (twitter, facebook, anything flex), or B. started on the desktop and then completely reimplemented for the web using those same web technologies (google's stuff). But what I'm talking about is taking desktop apps made using nice solid desktop app technologies and making them internet-accessible without ever even touching crap like DHTML, Flash, or even HTTP.