Slashdot Mirror


Online Ajax Pages The New Web Desktop?

SphereOfInfluence writes "With our existing models for operating environments aging badly, how do we manage our information and software as we get increasingly mobile and short on attention? In a ZDNet piece, Dion Hinchcliffe discusses the rise of the new dynamic, online, roaming Ajax desktops like Netvibes, Live.com, Protopage, and Pageflakes. Will concerns about privacy and reliability kill these or is this the wave of the future?"

266 comments

  1. Privacy by Anonymous Coward · · Score: 3, Insightful

    Although cool and nifty, who is really going to want a remote desktop which governments can potentially access at their free will? Especially nowadays with lax wiretap laws and the like.

    1. Re:Privacy by sleeper0 · · Score: 5, Interesting

      I think the popularity of web based email answers that question. People will use non private web based applications for private data.

      The real question is who needs it at all? The linked article mentions consumers probably not being ready for this kind of service for 1-2 years. The reality is that the market is fragmented, and while there are API's the results generally just resemble personalized home pages. I saw much better technology die on the vine at desktop.com 6 years ago - it was cool stuff looking for an audience. The same team had made what became yahoo mail - much simpler tech but in the end much more popular. The same situation probably stands today - (semi) cool tech looking for an audience. More or less we've long gotten past personalized home pages as a neat new thing - just adding AJAX doesn't change the paradigm. Desktop.com went some major steps beyond that but didn't just get killed by the bubble... they also never had an audience.

    2. Re:Privacy by Anonymous Coward · · Score: 0

      who is really going to want a remote desktop which governments can potentially access at their free will?

      No one wants it, but who'll let them? Mostly the same people who let the government potentially access their telephone lines or homes who are mostly everyone.

    3. Re:Privacy by Greg+Merchan · · Score: 4, Interesting

      If more people could safely run their own servers from home, we could have the benefits of these web-based apps without entrusting our data to strangers.

      I think the first barrier to this is the ISPs: I don't know of any broadband provider in my area that allows one to run a server. (The cable provider even tries to get people to pay extra to set up a router.) I'd think there must be little demand, but then I see ads on TV for remote access (to Windows machines).

      I guess no one has found a way to make a profit providing some sort of secure server appliance that allows a house to be networked and provides a remote connection. It seems we've had the parts of the technology for over a decade, but noone has put them all together. Heck, it's only in the last couple of years that we've seen home entertainment center computers, and those were possible at least as early as 1992.

    4. Re:Privacy by javaman235 · · Score: 4, Insightful

      I think the popularity of web based email answers that question

      I'm not so sure it does. The difference is that my email goes over the internet whether I use outlook or gmail, but my journal never does...And I'm not so sure I feel comfortable having my journal online, but I do feel okay with having it on my box.

      --
      -The art of programming is the pursuit of absolute simplicity.
    5. Re:Privacy by MichaelSmith · · Score: 1
      Although cool and nifty, who is really going to want a remote desktop which governments can potentially access at their free will?

      The whole thing is exactly like the distributed java/network computer model of 10 years ago. I suppose that failed because people didn't want or need it.

      Are we really different now?

    6. Re:Privacy by shmlco · · Score: 4, Interesting
      Agree. Most of the examples shown were "Yahoo" with the ability to drag stuff around and edit-in-pace. Wow. Color me... unimpressed.

      Take a look at your personal computer's desktop. Do you have every document, email, and application you own open on it, running side-by-side at the same time? No? Then why should I expect the wave of the future to be a personal web page?

      Want the future? Extrapolate from an "always-connected" world. Figure servers will increase in power exponentially. Figure the devices we carry will increase in power exponentially.

      With all that, the "future" is an oversized web page? Please.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    7. Re:Privacy by zoloto · · Score: 2, Interesting

      I just finished watching "I, Robot" moments ago so take this with a grain of salt if it seems I'm a little wary (wait... that's normal - nevermind)

      I believe there very well will be a means of having a "central system" to hold some of our types of data we really need access to. School reports, dissertations, files for work or more where we simply can't keep them on one computer. Your /home or /Users or 'Documents and Settings\user' may be on remote systems when you "sync" your directories designated to be on a central (at least for your own access) system. Something tells me that data encryption isn't going to be a part of the equation. The google's of the world would LOVE to read your data to profile you. (re: also governments)

      I would never really allow my files, even encrypted, to be stored remotely. My own computer practices of this are evident as I have a particular laptop that is never hooked up to the internet. This iBook has no wireless and I've put in "blanks" into the dialup, ethernet, usb & firewire plugs to prevent "mistakes". All updates are downloaded individually as they appear to me on another iBook when I see that "Software Updates" has an update waiting and transferred using CD-R's. All data to and from this system are handled by the same method. It's for things that I both want and need to keep private out of neccecity and choice. Things of financial, housing, family information, contracts, journal and some phd work as well. Normal things you really want to keep private from others.

      All in all, I recommend people doing something similar. The dual iBook thing on my part was only due to extreme luck on ebay where I picked up two for the price of one, so find something for your financial ability to use.

    8. Re:Privacy by Rocketship+Underpant · · Score: 1

      Yeah, I can't exactly see independently-minded Chinese lining up to keep their important documents and links at Yahoo! Desktop (or whatever Yahoo comes up with).

      --
      He who lights his taper at mine, receives light without darkening me.
    9. Re:Privacy by putko · · Score: 2, Interesting

      If you can find a good, smaller ISP, they'll let you do what you want.

      Perhaps MSN doesn't allow you to run a server, but the smaller folks don't care.

      Basically, the phone company forwards them the packets. If you run your own server, that's less work for them. As long as your modem can connect, via the phone system, to their network, their job is essentially complete.

      Also, users that are savvy enough to run their own server typically don't have all the bullshit Windows problems, so they are constantly calling with some malware/shitware related problem.

      --
      http://www.thebricktestament.com/the_law/when_to_s tone_your_children/dt21_18a.html
    10. Re:Privacy by Nosklo · · Score: 2, Insightful
      Although cool and nifty, who is really going to want a remote desktop which governments can potentially access at their free will?
      People who have nothing to hide?
      --
      find -name "*base*" -exec chown us {} \; ; ln -s /dev/zero /dev/chance ; make time
    11. Re:Privacy by Jaruzel · · Score: 3, Insightful

      Also, users that are savvy enough to run their own server typically don't have all the bullshit Windows problems, so they are constantly calling with some malware/shitware related problem.

      You were doing so well... until you threw in a random anti-windows statement.

      I run my own web servers at home, on my network, with forwarding from my internet facing router. These servers run Windows 2003. These servers do a variety of public and private web-serving. For a while I even ran a MUD server on another Windows box.

      For those that don't have access to a copy of Windows 2003 Server, Windows XP's IIS Web Server implementation is more than adequate to serve several low traffic sites (including those with dyanamic content)

      So, I resent your inferred statement that to have a workable at-home server solution it has to be be on a non-windows platform.

      -Jar.

      --
      Together, We Can Make Slashdot Better. I Do NOT Mod ACs. - Check Me Out
    12. Re:Privacy by dangitman · · Score: 0, Flamebait
      who is really going to want a remote desktop which governments can potentially access at their free will?

      Suckers and Patriots. I hear there's one born every minute.

      --
      ... and then they built the supercollider.
    13. Re:Privacy by ZeroExistenZ · · Score: 1
      The difference is that my email goes over the internet whether I use outlook or gmail, but my journal never does...And I'm not so sure I feel comfortable having my journal online

      Some do, or even crave it. And there are more.

      --
      I think we can keep recursing like this until someone returns 1
    14. Re:Privacy by Bloke+down+the+pub · · Score: 1

      Bill? Is that you?

      --
      It's true I tell you, feller at work's next door neighbour read it in the paper.
    15. Re:Privacy by SillyNickName4me · · Score: 1

      until you threw in a random anti-windows statement.

      Lets see.. the grant parent said that those people don't suffer from the typical windows related problems,. This can of course be because of running Linux, it could also be because of having a clue about running a server on Windows.

      Wether that is a statement about the users or the product is not clear, so I'd say you are reading more into the statement then was being said,

      I'd like to ask you however how likely you think it is that many home users are going to buy Windows 2003 Server for having a tiny private website with their own information... Ever looked at the price for that? It is pretty reasonable to assume that most people will not use it for this.

    16. Re:Privacy by Anonymous Coward · · Score: 3, Insightful
      Although cool and nifty, who is really going to want a remote desktop which governments can potentially access at their free will? Especially nowadays with lax wiretap laws and the like.
      The thing you need to realize is that the vast majority of people out there just aren't terribly concerned about privacy. Most folks figure their lives aren't interesting enough for a hacker/police/whatever to go digging into their email...and if it did happen, there's very little of importance to be found there. Maybe some love letters, or an embaressing photo...but most people don't have classified information going through their email.

      Convenience is a very important factor these days. At my job we set up VPNs and VNC/RDP sessions left and right - because people want the convenience of being able to access their computer/work/data/programs from wherever they're at. Services like Log Me In and Go To My PC are insanely popular.

      If you told the average user that they could use their computer from anywhere in the world through a web browser... That all their programs/documents/settings/whatever would all be there... That it would be just like sitting down at your PC at home/work, but from absolutely anywhere with Internet access... Most of them would leap at the opportunity, and privacy be damned.

    17. Re:Privacy by Anonymous Coward · · Score: 0
      Let's see, he specifically said

      "For those that don't have access to a copy of Windows 2003 Server, Windows XP's IIS Web Server implementation is more than adequate to serve several low traffic sites (including those with dyanamic content)"

      Gee, it looks like he's saying you don't need 2003 Server. Learn to read idiot.

    18. Re:Privacy by SillyNickName4me · · Score: 1

      Gee, it looks like he's saying you don't need 2003 Server. Learn to read idiot.

      Hmm yes, calling people names is always a good idea when trying to make a point..

      Lets ignore it..

      GP indeed said:

      For those that don't have access to a copy of Windows 2003 Server, Windows XP's IIS Web Server implementation is more than adequate to serve several low traffic sites (including those with dyanamic content)

      Lets see how much that helps..

      Last time I checked, Windows XP home edition is preloaded on virtually all computers sold to individuals.
      Windows XP home edition does not include IIS, it doesn't even include the personal web services from previous versions.

      That means that in most cases people will have to pay for XP Professional beforehand or when they encounter needing a web server.

      So... it may be somewhat cheaper then Win 2k3 server, but the problem is the same.

      Your point was?

    19. Re:Privacy by BillGod · · Score: 1

      me.... no.. but i did laugh

      --
      MISSING - Sig file. 2 years old black and white and very funny. If found please email me.
    20. Re:Privacy by airjrdn · · Score: 0

      Ahh yes, because the *only* webservers available for Windows are the ones that come with Windows.

      Of the probably 20 people I can think of off hand that are running Windows XP, one is running home. And, before you ask, none of the ones I'm referring to are pirated copies.

    21. Re:Privacy by fury88 · · Score: 1

      Haven't they tried this years back? I seem to remember online calendars and scheduling tools that were around 5-8 years ago that never caught on. I agree, email is ok, but I just don't see people moving purely online. You still have people who won't even purchase things over the web with there credit card.

    22. Re:Privacy by Aceticon · · Score: 1

      Also, users that are savvy enough to run their own server typically don't have all the bullshit Windows problems, so they are constantly calling with some malware/shitware related problem.

      --

      You were doing so well... until you threw in a random anti-windows statement.

      I read it like - "Users savy enough to run they're own server don't constantly call [the ISP] with malware/shitware related problems."

      At the moment this kind of problems (and users) are pretty much only to be found on/using a Windows environment. (which IMHO has a lot more to do with the popularity of Windows that with the security of the latest Windows versions)

      I saw no reference about savy-users NOT/NEVER using Windows.

    23. Re:Privacy by LurkerXXX · · Score: 1

      "So... it may be somewhat cheaper then Win 2k3 server, but the problem is the same." The problem isn't the same. You don't need 2003 server, or even XP Pro to run a web server. You know they do make version of Apache and quite a few other web servers that will run just fine under XP home. But just keep claiming the grandparent wanted folks to all buy 2003 server, because you can't possibly run a web server on XP home... "Your point was?" If someone is clueless enough not to know that you can get a webserver running under XP Home, their chances of doing so securely under *nix are pretty much nill.

    24. Re:Privacy by Anonymous Coward · · Score: 0

      Or they could run Apache on WinXP Home. But seriously, running a web server on Windows is being negligent with security.

      OpenBSD is perfect in its default configuration for running a small website. A security audited and patched Apache is included in the base install. The user only has to change one line in a config file to turn it on, chrooted by default.

      In the process you save $$$$ on MS corporate-ware and MS security training, because Windows is not secure by default, nor between the time a 0-day exploit appears and MS releases a patch two weeks later.

    25. Re:Privacy by SillyNickName4me · · Score: 1

      Ahh yes, because the *only* webservers available for Windows are the ones that come with Windows.

      Claim was that IIS on Windows 2003 Server can work fine (I happen to agree with that) and that XP with IIS would do as well.

      Alternative (free) webservers? Sure, those exist and are being used. It wasn't the argument being made however, not to mention that imho getting something like Apache to work on Windows is more efford then installing Suse with a webserver for example.

      Of the probably 20 people I can think of off hand that are running Windows XP, one is running home. And, before you ask, none of the ones I'm referring to are pirated copies.

      Good for them, but it isn't what the typical consumer has. We were talking about the average person running their own webserver for their own data, and those usually run home edition.

      For now it is substantially cheaper to use an alternative to IIS when wanting a web server, esp. for the average consumer. Using a nicely integrated package (ie, Suse with apache, but there are quite a few alternatives) provides much if not all of the ease of use, for a better price (ie, free in many cases).

      Oh and for that matter, most people do not have a MSDN subscription, and I am pretty sure Microsoft is not going to send free versions of their software to the large majority of their users either, so no, MSDN subscribtions don't work for getting stuff for free for this situation.

      Regardless of what you use, you'll need some knowledge about what you are doing, platform nor choice of webserver matter for that (they only matter for what and how much you need to know exactly). Most people who have enough of a clue to run their own webserver at this moment also have enough of a clue to not have most of the issues that the typical Windows user has, regardless of if they are using Windows or not.

      In other words, all I was pointing out is that knowledge is what makes the difference here, not so much the platform. Statements like the one about not having the typical windows issues should be read that way and not as 'windows bashing'.

    26. Re:Privacy by SillyNickName4me · · Score: 1

      The problem isn't the same. You don't need 2003 server, or even XP Pro to run a web server. You know they do make version of Apache and quite a few other web servers that will run just fine under XP home.

      I have used Apache on a variety of Windows versions. It works, tho 'fine' isn't exactly what comes to mind. That said, it is a workable solution in many cases.

      But just keep claiming the grandparent wanted folks to all buy 2003 server, because you can't possibly run a web server on XP home...

      The parent claimed that IIS was fine for this. I pointed out that running IIS will take buying a new version of WIndows for many people. There are free alternatives.

      If someone is clueless enough not to know that you can get a webserver running under XP Home, their chances of doing so securely under *nix are pretty much nill.

      Definitely, and what is more, it works the other way around as well, because while the platform can help with security, understanding what you are doing is the first thing required for doing that thing in a secure way (regardless of what 'that thing' is). That was also the point of my original post (not having the typical Windows related problems does not refer to using another platform, but to knowing what you are doing)

      This all said, if you are going to use an alternative webserver anyway, and you do have the knowledge to securely run a webserver, you may be better off using a nicely integrated and server oriented system for it, and there are indeed good alternatives to Windows with regards to that.

    27. Re:Privacy by soliptic · · Score: 1
      Yeah, but what do you expect, this is slashdot, where the fact they haven't looked at a Microsoft OS since 8 years ago is no barrier to judging it (against the latest and greatest release of Disro-of-Choice).

      Every single MS story comes with a wave of "hilarious" Blue Screen jokes despite the fact that XP has never given me, or anybody I know, a blue screen, in several years of heavy use (including as a DAW platform).

    28. Re:Privacy by MattWhitworth · · Score: 1

      That can be used to justify every invasive measure by the government. For example, placing cameras in every room in your house. Well, you've got nothing to hide, have you?

    29. Re:Privacy by MBGMorden · · Score: 1

      You can always use dyndns.org. I don't serve anything to other users, but I do have my machines setup so that I can remotely check my mail via SquirrelMail (or Mutt if all I can get is an SSH connection) on my Linux machine. I have my router setup to route different ports to different machines on the net, so by setting up eMule's web admin feature on Windows I can also check my downloads through it's web interface.

      To be honest, I truly love the idea of being able to remotely access my data from anywhere. HOWEVER, I will not trust that data to any person but myself. One reason is security, but the other is simply that while web-based apps make good make-shift solutions when I'm away, they in no way compare to a good local application when it comes to functionality. I've never found a web email client that could stack up to Thunderbird or Eudora. Same goes for every other web based interface I've seen compared to a local application. They're good on the road, but when I get home, I want to use a full fledged client.

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
    30. Re:Privacy by LurkerXXX · · Score: 1
      "That was also the point of my original post (not having the typical Windows related problems does not refer to using another platform, but to knowing what you are doing)"

      Then why not say uneducated-user problem rather than the much more inflamitary "Windows related problem"? Obviously you have a bias against windows.

      "This all said, if you are going to use an alternative webserver anyway, and you do have the knowledge to securely run a webserver, you may be better off using a nicely integrated and server oriented system for it, and there are indeed good alternatives to Windows with regards to that."

      If you know how to securely run a machine, it doesn't really matter what OS you chose to use. I've run windows machines for may years and never had mine hacked. I also run a number of OpenBSD machines and can say the same for them.

      If folks are running XP Home, then either they have specific applications they want to use that run only under XP or they prefer XP for some other reason, or they are uninformed enough about the options that they wouldn't be clued-in enough to run an alternate OS securely. In either case, telling them they would be 'better served' by another OS is pointless.

    31. Re:Privacy by SillyNickName4me · · Score: 1

      Then why not say uneducated-user problem rather than the much more inflamitary "Windows related problem"? Obviously you have a bias against windows.

      Because that same Windows (XP home edition) caters to those uneducated users. It should indeed be safe to use without much education. Matter of fact is that only educated users can use it safely. XP pro, most Linux distributions and the like do not cater at those uneducated users. The chance of someone actually running into substantial security issues with Linux as an uneducated user are small for now (since that user will have a problem getting it to run and connect to begin with)

      Anti Windows bias? Well, I believe there are better alternatives, but I do not believe that all versions of Windows are useless from the start.

      If you know how to securely run a machine, it doesn't really matter what OS you chose to use. I've run windows machines for may years and never had mine hacked. I also run a number of OpenBSD machines and can say the same for them.

      If folks are running XP Home, then either they have specific applications they want to use that run only under XP or they prefer XP for some other reason, or they are uninformed enough about the options that they wouldn't be clued-in enough to run an alternate OS securely. In either case, telling them they would be 'better served' by another OS is pointless.


      Which part of "and you do have the knowledge to securely run a webserver" was not clear in my statement?

    32. Re:Privacy by djg1977 · · Score: 1
      Most of the examples shown were "Yahoo" with the ability to drag stuff around and edit-in-pace. Wow. Color me... unimpressed.


      Well, that's the point. The advantages of a web based desktop should be obvious - you can access it from anywhere in the world. The main drawback for web desktops so far, has been limitations on the user interface. Now, with AJAX and related technologies, you can develop a quite nice user interface that runs through a browser.

      Just look at Gmail - most of the time I find it easier to compose, read and search my email through Gmail's web interface, than through my desktop client.

      The network is finally beginning to look like a computer.
    33. Re:Privacy by dw09577 · · Score: 1

      probably a valid point about gov and others, but I could easily see an AJAX-based "desktop server" sitting inside the firewall. All we would need then is the ability to edit documents, etc. via web application, and you could replace every machine on the network with a thin client running a browser. No viruses Office lic., Vista lic., (+ graphic card, etc.)...

      Sounds good to me. give them a browser, port inside apps over to web-based, let them do web mail + web desktop and apps, and you'd just have o worry about the server center, instead of the user community...

    34. Re:Privacy by willCode4Beer.com · · Score: 1

      "governments can potentially access at their free will?"

      Seems like in the current (sad) state of affairs they can do this ehether on your desktop or a remote server. Whats the difference?

      --
      ----- If communism is a system where the government owns business, what do you call a system where business owns govern
    35. Re:Privacy by Anonymous Coward · · Score: 0

      Ajax is based on 8 year old technology - i dont understand the current hype.

      Alot of the time it is

      10/10 for prettyness
      10/10 for style
      0/10 for ease of use
      0/10 for usefulness

      There are some good things you can get done with ajax.

      Gmail is a good example but all these so called "os" are just crap.

    36. Re:Privacy by willCode4Beer.com · · Score: 1

      "If you told the average user that they could use their computer from anywhere in the world through a web browser..."

      You just described VNC :)

      Most VNC servers also serve a webpage with a VNC client applet. I think the only thing people behind firewalls and NATs need is a public server that can proxy the VNC traffic. And make the vnc server actively connect to it just in case it happens to be behind a firewall (oh wait, I do that with SSH). Use any OS for a desktop, and access from any OS, woohoo.

      Seriously though, it seems the objective of this technology already exists. The only "real" difference is that with the AJAX web desktop, you move the "desktop" away from your desktop.

      --
      ----- If communism is a system where the government owns business, what do you call a system where business owns govern
    37. Re:Privacy by GeekTW · · Score: 1

      I'm not so sure it does. The difference is that my email goes over the internet whether I use outlook or gmail, but my journal never does...And I'm not so sure I feel comfortable having my journal online, but I do feel okay with having it on my box.

      You are correct in saying e-mail is different, e-mail isn't secure, no matter what service you're using, unless you have it encrypted. You know that, I know that, and probably 90% of Slashdot knows that. But for Joe User, he/she doesn't know how insecure e-mail is. They don't realize an e-mail from me, may not be from me. If they did, phishing scams wouldn't work like they do. My point is, people may be naive enough to subscribe to a roaming desktop, without concern for security.
    38. Re:Privacy by Quarters · · Score: 1

      No. The first barrier to your idea is that for 99.9999% of the computer using population setting up, configuring, and maintaining a second computer, let alone a dedicated server, is either a terrifying proposition or something of 0 interest.

    39. Re:Privacy by Anonymous Coward · · Score: 0

      So - if we don't want to trust third parties to hold some of that info, who is going to start building an open-source version of these, so we can host it ourselves? Is someone already working on one? Where? I'd help out...

    40. Re:Privacy by sadler121 · · Score: 1

      true, google is in the market of parsing documents (web/email) and returning target ads, but that wouldn't kept another company (or even google) for a fee, to allow you to store data on their servers, encrypted, with a key that only the owner of the information knows. that way, when the FBI/CIA/NSA come knocking at the door with a national security letter, the buisness can give them an encrypted mess. The FBI/CIA/NSA would have to goto the owner of the information to get the key, or spend time cracking the info.

    41. Re:Privacy by agallagh42 · · Score: 1

      "Just look at Gmail - most of the time I find it easier to compose, read and search my email through Gmail's web interface, than through my desktop client."

      Don't you think that has more to do with Gmail's threading and labels than with the fact that it's web based? The web based aspect only gives you consistent access from any computer (a huge plus on it's own of course), but all webmail products give you that. The biggest benefit of Gmail is the radical new interface design.

      --
      Carpe Cerevisi - Seize the Beer
    42. Re:Privacy by djg1977 · · Score: 1

      Well, could be, but the fact that Gmail's web interface does NOT turn me off, is the key here.

    43. Re:Privacy by pigwin32 · · Score: 1

      Windows XP IIS web server is completely inadequate for running any form of site. IIS on XP has a 10 connection limit discussed ad nauseam. Of course Apache will also run on XP so technically you are correct, it is possible to adequately serve several low traffic sites on XP.

      Of course suggesting that a home user slap up a Front Page site on their XP Home Edition and connect it to the internet would be somewhat disingenuous.

    44. Re:Privacy by Nosklo · · Score: 1

      That's a different story. I don't want the government to be seeing my butt. I dont have my butt's picture on my computer.

      --
      find -name "*base*" -exec chown us {} \; ; ln -s /dev/zero /dev/chance ; make time
  2. On the whole they are closer to solution. by luvirini · · Score: 4, Interesting
    The way these services and others make place irrelevant is a good thing, people have tried many different solutions from PDAs and laptops to remote control software to achieve the same goal.

    But this solution has also it's own problem, like all the earlier attempts, in this case the problem is a lot about security and secrecy.

    When these applications start to be sold to companies to run on the company's own servers, some of the problems do go away ofcourse..

    1. Re:On the whole they are closer to solution. by killjoe · · Score: 3, Insightful

      Aaaah good old incompetent Sun and it's stupid management. Only if they had any foresight, will, and brains we would not all be hyping AJAX all to hell and be perfectly happy using applets and java web start. We would forever be saved from trying to shoehorn applications into a stateless publishing technology.

      Too bad they could not figure out how to make AWT look nice, how to get swing into every desktop, how to make multipe applications run in the same VM, how to make it easy to build swing apps, how to make gui threading managable by humans, how to not make java web start be the butt ugliest thing in the face of the planet.

      Instead we are forever doomed to try and build applications in XML and javascript quite possibly the worst combination of tools to build a applications ever invented by mankind.

      Thanks Sun, I blame you, you could have saved us from all this madness but you just couldn't capitalize on the golden goose sitting in your barn.

      --
      evil is as evil does
    2. Re:On the whole they are closer to solution. by shmlco · · Score: 4, Funny

      Don't worry. There's always Flash...

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    3. Re:On the whole they are closer to solution. by SillyNickName4me · · Score: 1

      The way these services and others make place irrelevant is a good thing, people have tried many different solutions from PDAs and laptops to remote control software to achieve the same goal.

      But this solution has also it's own problem, like all the earlier attempts, in this case the problem is a lot about security and secrecy.


      To me the two biggest issues (besides security and privacy) seem to be:

      1. need network access to get to my data (compare to a PDA which works perfectly fine without it, tho your data may not always be uptodate)

      2. due to needing network access, the cost in battery use for accessing information is a lot higher.

      Those two things make this a nice but not very workable idea for many of the situations I encounter, and yeah, I do have internet access from almost everywhere, can link my laptop to it from almost everywhere etc, regardless, there are often places where I need access to my data and where there is NO network coverage (read, NONE of the 6 GSM/GPRS networks that I could possibly use is reachable there).

      Hence, this is for me an unworkable solution, it is simply a lot worse then using a PDA and syncing it wirelessly.

    4. Re:On the whole they are closer to solution. by Dom2 · · Score: 3, Informative
      You jest, but Adobe's Flex stuff looks quite useful...

      -Dom

    5. Re:On the whole they are closer to solution. by helix_r · · Score: 1


      Indeed.

      I don't have as bleak a view, however. The web-app crap that is today's fad will eventually be replaced by better and cleaner technology.

      Its just a question of how many years developers have to suffer through the pain of consecutive "frameworks" that seem to be coming out at a rate of one per week. None of these frameworks give a damn about addressing developer productivity.

      Anyways, in the not too distant future, I look forward to making a living unplugging old ugly j2ee apps and replacing them much better apps developed in a fraction of the time.

    6. Re:On the whole they are closer to solution. by rubypossum · · Score: 1

      Amen to that.

      So I want to develop a cross platform application in a post-Sun-screwup world? Well first I need a cross platform Widget set. Hello 3-6MB of WxWidgets, QT etc. I want to do so in a RAD language? Hello 2-5 MB of interpreter (python, perl, ruby, etc.) I want to make the silly thing network transparent? Hello hellish cross platform threading, mysterious lockups and incompatible socket libraries.

      Coupled with this my employer will probably be using Microsoft .NET or MFC, so the knowledge I gain in creating my application won't have a market value.

      This is what makes creating an application in a document display platform almost appear appealing. I can be reasonably sure (if I write it well) that my AJAX application will work cross platform, will be network enabled for remote access, will not require tens of megabytes for an installer and will have a large userbase that already has the display platform and interpreter (a web browser.)

      It's not quite RAD but with a prebuilt javascript widget library (and a session managment library on the CGI/ASP/PHP side) it's almost.

      Thank you Sun, you screwed the pooch and the pooch has screwed us all.

      --
      I have a theory that the truth is never told during the nine-to-five hours. - Hunter S. Thompson
    7. Re:On the whole they are closer to solution. by lewi · · Score: 1

      Agggh!!! (panting and sweating)

      It was only a dream. It was only a dream. It was only...

      (continues rocking and mumbling)

  3. Buzzword alert by Viol8 · · Score: 3, Insightful

    Oh dear, its only a short article and its got "leverage" and
    "rich" (as in experience). Pass the sick bucket. Still, I
    persevered. Not sure why I bothered. Seems like just another
    snake oil "evangelist" (he missed that one) trying to flog yet
    more CPU sucking eye candy that will have a large impact on your
    computers power consumption but a small impact on how much more
    usable the web will be. Is it just me? Is there really something
    wrong with clear, simple HTML pages that load quickly without all
    this flash/ajax/flavour-of-the-month-tool crap shoved in just to
    please web fashion victims?

    1. Re:Buzzword alert by BrynM · · Score: 3, Funny

      "Online _____ is the new ____!" If there was some way to monetize every time I hear this.... It would be the new money. Thus, online bullshit is the new bullshit - only digitized!

      --
      US Democracy:The best person for the job (among These pre-selected choices...)
    2. Re:Buzzword alert by numLocked · · Score: 1

      Ajax runs quickly and isn't graphic-intensive.

      There is nothing wrong with HTML pages, but pages are a sight more useful when they display exactly what you want. This is a very natural evolution of web pages, I don't see what the problem is.

      Yeah, Ajax has been a buzzword recently, but you seem to have an issue with the technology, and not the buzz. Have you used any of these services? You'd notice that they're REALLY COOL! There's nothing wrong with easily organizing content. Try it before you knock it.

    3. Re:Buzzword alert by MadJo · · Score: 2, Funny

      It makes a great drinking game...

      pass that bottle again!

    4. Re:Buzzword alert by Viol8 · · Score: 2, Insightful

      I don't want "REALLY COOL" "dude". I'm not 12. I just want
      information. Google manages to present relevant information from
      a couple of billion web pages with a simple HTML front end.
      Why can't other sites manage it? Why do they have to resort to
      some developers wet dream to get their info across? Because most
      of them wouldn't know good usability design if it the dictionary
      definition was stamped in red ink on their foreheads, thats why.

    5. Re:Buzzword alert by sleeper0 · · Score: 2, Insightful

      just so you know, one of the primary reasons that the world caught on to what is now called AJAX applications is google's use of the technology - granted not on the search homepage but in several other big apps.

    6. Re:Buzzword alert by Dominic_Mazzoni · · Score: 4, Informative

      I don't want "REALLY COOL" "dude". I'm not 12. I just want
      information. Google manages to present relevant information from
      a couple of billion web pages with a simple HTML front end.


      I hate to break it to you, but Gmail and Google Maps are totally AJAX, and even a basic web search on Google makes use of JavaScript. Google integrates it all so seamlessly, you don't even realize that they're using fancy "Web 2.0" tricks to give you what looks like a simple HTML page.

    7. Re:Buzzword alert by numLocked · · Score: 1

      It does really take longer to go from slashdot, to amazon, to your email, to a to-do list, to cnn.com than it does to see all that information presented in one place. There isn't really any kind of tradeoff for that functionality. When I say REALLY COOL, what I mean is REALLY USEFUL. It's easier to keep tabs on what's going on. If you don't regularly check a number of sites, then yes, it may not be that useful for you, but for me, getting all the information I regularly read in one place is very convienient.

    8. Re:Buzzword alert by Jugalator · · Score: 2, Funny

      Your lack of respect for exciting Web 2.0 user experiences is disturbing!

      --
      Beware: In C++, your friends can see your privates!
    9. Re:Buzzword alert by Viol8 · · Score: 3, Insightful

      I wasn't talking about Gmail or maps. And yes the search page
      uses javascript but so what. That takes no longer to load up
      and run than HTML. And even overuse of javascript can be a pain.

      If some people want to ultimately have their browser as some
      kind of web based virtual computer thats up to them. But I don't
      see why that sort of crap should be foisted upon the rest of us
      who just want to look for stuff and do it quickly. I still have
      to use dial up at home and I don't appreciate having to download
      a 1 meg app just to view a friggin web page which could have been
      rendered in HTML in a few kilobytes, albeit with a few less
      poxy graphics (Boo bloody hoo).

    10. Re:Buzzword alert by LordLucless · · Score: 1

      I use personalized google too, but you do realize that none of that functionality is really AJAX? The AJAX component is the drag-and-drop style of configuration. All the grunt work is done via traditional methods. So, in this case, AJAX really is used for nothing more than eye-candy.

      Of course, there actually are some places where AJAX provides functionality and not just good lucks (gmail for one), but personlized Google isn't a good example of this.

      --
      Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
    11. Re:Buzzword alert by Anonymous Coward · · Score: 0

      He was talking about google search, ie the search page. Mod parent down.

    12. Re:Buzzword alert by Westley · · Score: 2, Insightful

      Do you have any examples of the 1MB apps you're talking about? Most AJAX usage I've seen has been really small.

      As for doing things quickly - I totally agree, which is why I infinitely prefer the Google maps way of doing things to the "old" way where you were basically in the "North by a square, north east by a square, only show me 3x3 squares at a time" trap. Did you really find that more usable than Google Maps?

      Jon

    13. Re:Buzzword alert by bustersnyvel · · Score: 1

      I feel the same way. Nowadays, websites aren't about information
      any more, they are about looking cool and providing a "look"
      for the company behind it. Sure, good looks are nice, but more
      and more people trade looks for usability. I prefer clear,
      easily usable, quickly loading website. I don't care about the
      underlying technology.

    14. Re:Buzzword alert by lucas+teh+geek · · Score: 1
      If some people want to ultimately have their browser as some kind of web based virtual computer thats up to them. But I don't see why that sort of crap should be foisted upon the rest of us who just want to look for stuff and do it quickly. I still have to use dial up at home and I don't appreciate having to download a 1 meg app just to view a friggin web page which could have been rendered in HTML in a few kilobytes, albeit with a few less poxy graphics (Boo bloody hoo).
      out of context, 10 out of 10 people would guess your rant was about flash. do you actually know what you're ranting about? AJAX is very lightweight, though I'd love to see this 1MB page youre complaining about.
      --
      TIAEAE!
    15. Re:Buzzword alert by Anonymous Coward · · Score: 0

      I agree with you, so don't get me wrong. BUT.... I used esentially the exact same argument in debating www in the days when gopher ruled. Flash certainly does not cut it in terms addressed, but objectively I can see AJAX comming on - mainly because it does something useful (albeit by breaking the std page refresh model).

    16. Re:Buzzword alert by Vo0k · · Score: 4, Interesting

      Is there really something wrong with clear, simple HTML pages that load quickly without all this flash/ajax/flavour-of-the-month-tool crap shoved in just to please web fashion victims?

      Yes. Amount of repeatable content, basic pain of CGI/PHP. Take a GOOD application of AJAX: DeviantArt comments. Each art piece posted to the site may be commented by the users. Sometimes there's 200-300 comments, discussion occurs etc. Indentation provides some threading, there are some basic forum-like features etc. You probably want to cut on page switching when you dig into the comments. You set it to display 100 per page. Including links, avatars, smileys and some more such crap plus bandwidth throttling from the server if you're not a subscriber, it starts getting really lengthy to load the comments page. But it's still better than loading 20 separate pages 10 comments each. Then you want to participate in the discussion...

      Non-AJAX, non-javascript, pure CGI way: Click "Reply" in given thread. Wait for the "reply" form for given thread to load. Type your answer. Click "preview". Wait for preview to load. Click "send". Wait for the whole discussion page, 100 posts, plus your answer to load.

      AJAX way: Click "Reply". Immediately a textarea appears, where your post would go, with "send", "preview" and "cancel" buttons. You type in your reply and press "preview". The border around the textarea blinks for a moment and then turns into your post's final look, in context of the 100 other posts, differing only by "preview" replaced by "edit" (which with no further delay gets you back to editing your post). You click "send" and the border blinks a moment more. Buttons vanish, your post is placed in the context amongst all the rest, where it was supposed to be. No single other post gets reloaded.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    17. Re:Buzzword alert by aussie_a · · Score: 1

      This is a very natural evolution of web pages, I don't see what the problem is.

      If I want an application, I'll run a program locally (where I'm not dependant on a stable internet connection). I've been using Gmail (a fairly simple (and thus in my opinion, better then most) Ajax program) and for 3 reasons only.
      1> It is nice to be able to know I'll never run out of e-mail space. I never would have thought it was such a big feature before I got it, but now I wouldn't want to do without it.
      2> It's nice to be able to access my e-mail anywhere.
      3> The label system was fairly intuitive with no other e-mail system like it.

      However I have never been a big fan of the interface. Not only does it not work correctly on some computers (most likely something to do with their configuration, and being a beta I do have to expect problems), but it doesn't load quicker, and it does take a bit to open gmail in the first place as the interface loads up. If it's meant to show off how great Ajax is, it falls short considerably, as anything in it can be done just as well with "normal" HTML, CSS and JavaScript with a MUCH smaller amount of overhead. I do realise Ajax is little more then just a fancy name for JavaScript and HTML (and a couple of other technologies put together), but all Ajax systems appear to share an unnecessary amount of overhead. It isn't needed.

      Now compared with a locally installed computer program, Gmail definitely falls short. I have recently converted to Opera and am quite impressed with it's built-in e-mail program that functions nearly just as well as Gmail, but is much faster with less load times. It is even able to mimic Gmail's label systems via it's Filtering system. Although it does fall short in that you can't put an e-mail in more then one filter (and as such, primarily acts like a folder). But having said that, I seldom put e-mails in more then one label anyway (so my labels did tend to act like folders).

      I compared Gmail with a more traditional program, because it is often touted as the ability to migrate programs onto an online setting. Well it does it, but with significant overhead, and no added bonus (except you can access it from any computer, if your internet connection isn't down).

    18. Re:Buzzword alert by Temporal · · Score: 1

      Do you even know what AJAX is? It sounds like you're ranting about Java or Flash. AJAX doesn't even have anything to do with graphics.

      AJAX is just Javascript that communicates with the server in the background. Obviously not every web site needs it, but stuff like Google Maps is clearly far superior to anything you could create with static pages. Google Maps is much faster and less bandwidth-hungry than the mapping sites that existed before it.

      If Slashdot used AJAX, you'd be able to read it a lot faster on your dial-up line since you wouldn't have to re-download all of the page formatting for every comment you read.

    19. Re:Buzzword alert by ajs · · Score: 1

      There's some BAD AJAX out there. Mostly, you'll see this when crappy tools are used to generate exceedingly crappy JavaScript + CSS + XHTML with loads of redundancy and automated cut-n-paste.

      Then again, there's that kind of bad code in just about every language.

      AJAX is not a bad tool, it's just prone to be used by people who don't understand it.

    20. Re:Buzzword alert by SillyNickName4me · · Score: 1

      Yes. Amount of repeatable content, basic pain of CGI/PHP. Take a GOOD application of AJAX: DeviantArt comments. Each art piece posted to the site may be commented by the users. Sometimes there's 200-300 comments, discussion occurs etc. Indentation provides some threading, there are some basic forum-like features etc. You probably want to cut on page switching when you dig into the comments. You set it to display 100 per page. Including links, avatars, smileys and some more such crap plus bandwidth throttling from the server if you're not a subscriber, it starts getting really lengthy to load the comments page. But it's still better than loading 20 separate pages 10 comments each. Then you want to participate in the discussion...

      Lets analyse this a little bit deeper..

      Art piece gets posted, now lets assume this is a big picture and give it 2mb.
      comments get added, lets assume people really have something to say, and write 300 comments that average 2k bytes each.
      Now, the page also contains some other stuff like menus, logo etc, lets say this is another 50k for the html and 200k for pictures (logo etc).

      So, the first time you look at this, regardless of it using AJAX or some PHP based solution or the like, you need to download some 2850k.

      Next refresh this will be 650k in case of a traditional (CGI/PHP whatever solution), everything else will c ome from cache, and that is if the comments changed at all. It will be 600k in case of AJAX when the comments changed (the comments have to be loaded, the page layout etc not). In either case it will be a few bytes if the comments didn't change (and the server is smart enough to realize).

      So, total gain for this example would be a bit less then 50k. Not really impressive, and not the huge kind of difference you seem to believe is possible.

      Non-AJAX, non-javascript, pure CGI way: Click "Reply" in given thread. Wait for the "reply" form for given thread to load. Type your answer. Click "preview". Wait for preview to load. Click "send". Wait for the whole discussion page, 100 posts, plus your answer to load.

      Yes, and the fact that AJAX hides this a little bit betetr in no way changes that the same underlying things are happening, taking approx as much time and bandwidth.

      AJAX way: Click "Reply". Immediately a textarea appears, where your post would go, with "send", "preview" and "cancel" buttons. You type in your reply and press "preview". The border around the textarea blinks for a moment and then turns into your post's final look, in context of the 100 other posts, differing only by "preview" replaced by "edit" (which with no further delay gets you back to editing your post). You click "send" and the border blinks a moment more. Buttons vanish, your post is placed in the context amongst all the rest, where it was supposed to be. No single other post gets reloaded.

      Ah yes... and luckily the JS code AND layout data for doing this didn't have to be sent to your computer beforehand, regardless of if you were going to reply..

      If a website presents you with a form, it did have to send you that form first, REGARDLESS of AJAX. The form did not just magically appear in the memory of your computer.

      AJAX has some very nice things, but it is not the silver bullet you seem to think it is when it comes to nice responsive web applications.

    21. Re:Buzzword alert by ObsessiveMathsFreak · · Score: 1

      If Slashdot used AJAX, you'd be able to read it a lot faster on your dial-up line since you wouldn't have to re-download all of the page formatting for every comment you read.

      Are you insane?! Under this system, comments would have to be fetched and transmitted to the client on a client by client basis. No more static html pages for CmdrTaco.

      Ajax would quickly result in the Slashdot servers going critical and the resultant thermal shockwave would obliterate Taco in a spray of charred bones and vaporised Jolt where he sat debugging the godawful mess that had become Slashdot.

      --
      May the Maths Be with you!
    22. Re:Buzzword alert by The-Bus · · Score: 1

      Are you one of those suicidal internet users in Japan? Because not only does that headline repeat itself, but the articles repeat themselves so much that you'd probably die of alcohol poisoning before the end of the day.

      As far as "AJAX 2.0 Blognets! being the Next Sliced Bread" I have two methods of working when I am away from home. I can access anything I need if I can go through FTP (or fill in your favorite existing technology which has allowed you to do this for the past ten years). My mail is forwarded to Gmail so I can read and respond when I am away.

      Anything more complex and I'd just use a laptop.

      --

      Small potatoes make the steak look bigger.

    23. Re:Buzzword alert by Vo0k · · Score: 1

      > Art piece gets posted, now lets assume this is a big picture and give it 2mb.

      Let's assume it's average and it's 100K. It's meant for viewing online, not printing. Some morons like to post 3000x2000 GIFs but most people try to stay around 800x600.

      > comments get added, lets assume people really have something to say, and write 300 comments that average 2k bytes each.

      Counting in the HTML overhead (borders, links, styles etc) yes, about 2k each.

      > Now, the page also contains some other stuff like menus, logo etc, lets say this is another 50k for the html and 200k for pictures (logo etc).

      Probably more but DA puts in lots of crap, so let's say yes.

      > So, the first time you look at this, regardless of it using AJAX or some PHP based solution or the like, you need to download some 2850k.

      Including HTTP headers for each request, about 1M. (100k instead of 2M)

      > Next refresh this will be 650k in case of a traditional (CGI/PHP whatever solution), everything else will come from cache, and that is if the comments changed at all.

      Add about 50 HTTP requests 1k each, checking if things (pics) didn't change since the last time. "Next refresh" occurs after you added your comment so the comments DID change. So, about 700k.

      > It will be 600k in case of AJAX when the comments changed (the comments have to be loaded, the page layout etc not).

      No, you load only new comments. Old ones remain in place. If one comment of 2k was added, there was about 1k of content, 1k of HTML overhead which sits inside the JS so isn't downloaded, 1k of xmlhttprequest overhead. So about 2k downloaded. Other comments didn't change, remain untouched.

      > In either case it will be a few bytes if the comments didn't change (and the server is smart enough to realize).

      They did, because you added one yourself.

      > So, total gain for this example would be a bit less then 50k. Not really impressive, and not the huge kind of difference you seem to believe is possible.

      700k - 2k = 698k. Profit: bandwidth usage reduced by 99,7%. Considering the server-side throttling (on one hand) and lag for exchange of the AJAX dialog (on the other hand), you get waiting down from about 40s to 2s.

      > Ah yes... and luckily the JS code AND layout data for doing this didn't have to be sent to your computer beforehand, regardless of if you were going to reply..

      Once. <script src="...">
      Later just 1k to check if the script changed and needs to be reloaded. No matter how many pages of different artists I visit. With some luck, at next visit it will be still in the disk cache.

      > If a website presents you with a form, it did have to send you that form first, REGARDLESS of AJAX. The form did not just magically appear in the memory of your computer.

      But it sent everything in one batch, using heavily paralell transmissions. I didn't have to wait for the form to load separately. Before I click and I see the result, it takes at least some 2s, no matter how big is the page. But this is moot, the form being placed there dynamically is just a convenient trick. The idea is that after I add a comment, I don't wait to see it in context with the page reloading from scratch. It gets included at once, and I can go back to reading/writing more without waiting for the updated comments page to reload. 2s instead of 40s.

      > AJAX has some very nice things, but it is not the silver bullet you seem to think it is when it comes to nice responsive web applications.

      "nice" - needs good design.
      "responsive" is the keyword, and it IS the silver bullet here. You wait ONCE. Like with local apps, I start up my favourite GIMP and go read /. before it loads, but when it works, it works, same here, you need to let the AJAX app to load, go, read some other page in a different tab or have a cup of coffee, but then you go back to the AJAX-enabled page and everything gets very fast and responsive. Your workflow isn't continuou

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    24. Re:Buzzword alert by MadJo · · Score: 1

      You do know that GMail is Ajax-based? *drinks another one*

    25. Re:Buzzword alert by SillyNickName4me · · Score: 1

      No, you load only new comments. Old ones remain in place.

      That is a possible implementation indeed, insert the new comment somewhere into the DOM.

      While this works very well for adding new things (or replacing existing things), it becomes a real pain when the application (either server or client side) has to keep track of what is there.

      Also, this concept was there with HTTP and DHTML, so while you are definitely right about this being a potentially smart way to do this, it has nothign to do with AJAX other then that AJAX does not conflict with it, and in fact suggests using such solutions.

      If one comment of 2k was added, there was about 1k of content, 1k of HTML overhead which sits inside the JS so isn't downloaded, 1k of xmlhttprequest overhead. So about 2k downloaded. Other comments didn't change, remain untouched.

      See above. You are right about the saving this can give, but it is not something that requires AJAX.

      700k - 2k = 698k. Profit: bandwidth usage reduced by 99,7%. Considering the server-side throttling (on one hand) and lag for exchange of the AJAX dialog (on the other hand), you get waiting down from about 40s to 2s.

      The issue is that AJAX basicly adds an alternative for GET/PUT requests, no more and no less.
      You can use that in all kinds of fancy ways, but very few of those ways are unique to AJAX, they just happen to work well with it.

      AJAX also makes that your implementation gets a bit cleaner maybe because of not having to figure out a way to preserve a DOM or do requests in the background (both are not very difficult, but they are a bit hacky).

      But it sent everything in one batch, using heavily paralell transmissions.

      It is either one batch or heavily parallel transmissions...

      Regardless, you load everything upfront indeed.

      I didn't have to wait for the form to load separately. Before I click and I see the result, it takes at least some 2s, no matter how big is the page. But this is moot, the form being placed there dynamically is just a convenient trick. The idea is that after I add a comment, I don't wait to see it in context with the page reloading from scratch. It gets included at once, and I can go back to reading/writing more without waiting for the updated comments page to reload. 2s instead of 40s.

      Yes, that is all nice DHTML, AJAX adds a clean way to do asynchronous requests to it, but there were already ways to do that anyway.

      "nice" - needs good design.
      "responsive" is the keyword, and it IS the silver bullet here. You wait ONCE. Like with local apps, I start up my favourite GIMP and go read /. before it loads, but when it works, it works,


      Ah.. I gues that is why so many operating systems delay loading of libraries untill they are actually used, hell, even do that with memory pages from executables..

      I also guess this is why KDE for example loads itself and its whole bunch of applications all at once, you might just need them..

      (oh, and Gimp 2 takes all of 11 seconds to load here anyway..)

      same here, you need to let the AJAX app to load, go, read some other page in a different tab or have a cup of coffee, but then you go back to the AJAX-enabled page and everything gets very fast and responsive.

      Absolutely usefull for quickly looking up information and such.. Oh, I should just keep the page open all day just in case I guess..

      No, it doesn't compare to local applications at all. Most local applications here have initial load times in the order of 10-30 secs.

      Your workflow isn't continuously interrupted by longish waits. If by "responsive" you mean "loads fast", that's a misunderstanding. Instead of 40 breaks of terribly annoying useless 10s each, you get one of 60s which you just wait through doing something productive (or not) and 39 of nice, friendly 2s.

      Well, if that is the one web application you are going to need for the next 30 minutes or so you have a poi

    26. Re:Buzzword alert by Lawrence_Bird · · Score: 1

      eek! you mean.. the marketing people have gotten hold of the corp web site? What's next? Overstated product claims placed online?

    27. Re:Buzzword alert by Temporal · · Score: 1

      Err... AJAX clients communicate with the server using plain old HTTP. You can cache the responses for common requests just as easily with AJAX clients as with regular static HTML clients. In fact, because these responses would be much smaller than full HTML pages, you could cache far more of them, further reducing load.

    28. Re:Buzzword alert by Anonymous Coward · · Score: 0

      You must be a Lisp programmer.

    29. Re:Buzzword alert by nate+nice · · Score: 1

      You, like most people, have absolutely no idea what AJAX really means. It has nothing to do with flashy graphics or UI's that are more interactive. It allows for these to exist, but this is simply some eye candy some people, as you pointed out, evangelised a bit too much.

      Seriously, the purpose of this technology is really simple. you can now send user data back to the server and have it send messages back to any client with this data to allow the DHTML to be updated and rendered again without an explicit postback. Besides a nice GUI it allows for things like preemptive database searching (send search data in as it's being entered so the search comes back faster from the users perception), realtime data sharing between users and really the ability to make better UI's for some Web applications...like Gmail for instance.

      Sure, some people have basterdized AJAX and really only think it's for making a better UI. But it's all the little things you can accomplish with it by now having an actual pipe and rendering system available to Web clients. Now it isn't such a "stateless" system and you can interact with user explicitly or "behind the scenes".

      I mean, you can't be negative about a technology that when wielded correctly gives you more options.

      I know some Web programmers don't like it because it's something new to learn.

      --
      "If you are a dreamer, a wisher, a liar, A hope-er, a pray-er, a magic bean buyer ..."
    30. Re:Buzzword alert by dodobh · · Score: 1

      Non-AJAX, non-javascript, pure CGI way: Click "Reply" in given thread. Wait for the "reply" form for given thread to load. Type your answer. Click "preview". Wait for preview to load. Click "send". Wait for the whole discussion page, 100 posts, plus your answer to load.

      Right click, select open in new tab, continue reading the next comment while the tab opens. Then reply. You don't _have_ to stop. And for most web fora, the context switch cost from comment to reply to comment is small and can be ignored.

      --
      I can throw myself at the ground, and miss.
    31. Re:Buzzword alert by ObsessiveMathsFreak · · Score: 1

      But what about AJAX's "no page reload" paradigm. How is the Slashdot server to survive when thousands of clients are making dynamic changes, submitting them, and calling for customised updates to their local copies?

      --
      May the Maths Be with you!
    32. Re:Buzzword alert by saltydogdesign · · Score: 1

      What you want is good designers, not dictates on technology. If you think every aspect of every body of information can be served by plain text, you're a fool. Check out Tufte.

      --
      // This is not a sig.
    33. Re:Buzzword alert by Random832 · · Score: 1

      How do usenet servers survive? The "customized updates" happen at the client side. As far as the server cares, the client is just downloading individual posts.

      --
      We've secretly replaced Slashdot with new Folgers Crystals - let's see if it notices.
    34. Re:Buzzword alert by Temporal · · Score: 1

      How on Earth is that any harder than what Slashdot is doing already?

    35. Re:Buzzword alert by xero314 · · Score: 1

      I think alot of people may be missing the point of the potential benifit of some of the newer technologies like AJAX and why it's not just about fancy graphics. The key with AJAX is that it can happen asynchronously (which any one that communicates by IM or email regularly can see the benefit too) and therefor does not need to impede the user experience. I would think, correctly applied, these technologies would actually reduce the amount of network traffic, and increase the relative spead for those using slower connections, by not having to transmit layout and display information in each request. Instead the process should be to load a basic HTML page (I'm not talking about web apps, since they should not be written in document markup) which will include a small library for accessing the serve, and when you move from "page to page" an AJAX request would be sent to the server and return only the new content which is placed where need by a client side processor. If you combine that with binary encoded XML and you get very small and quick to parse packets, greatly reducing network traffic.

      Like any other technology, new web techniques can be miss used. Try not to judge the concept on poor implementations.

    36. Re:Buzzword alert by Vo0k · · Score: 1

      Also, this concept was there with HTTP and DHTML, so while you are definitely right about this being a potentially smart way to do this, it has nothign to do with AJAX other then that AJAX does not conflict with it, and in fact suggests using such solutions.

      How else are you going to replace a piece of page with data from the server which wasn't available while the page was loaded, without reloading the whole page? Sure, DHTML using DOM, but you don't just paste what you typed in and send a copy to the server. You send your data to the server, it parses it, replaces markers with icons, validates for no malicious HTML, sends back parsed version and allows the app to include it in the page. (there are a few hackish ways to load external data without AJAX, say var import=createNode('script'); import.src="http://....js"; document.appentChild(import)) but generally AJAX is considered THE way to do it.)

      The issue is that AJAX basicly adds an alternative for GET/PUT requests, no more and no less.
      and inserting the results into current page without replacing it whole.

      I also guess this is why KDE for example loads itself and its whole bunch of applications all at once, you might just need them.

      We're not talking about desktop environment or operating system. We're talking about an application. Most apps load up all the needed libs on startup.

      (oh, and Gimp 2 takes all of 11 seconds to load here anyway..)
      Feel lucky.

      Well, if that is the one web application you are going to need for the next 30 minutes or so you have a point. That works for some applications and not for others.

      And here I agree 100%. If you looked at my /. user page, you'd see one of two accepted stories is "AJAX sucks most of the time". It really does, because in most of cases where it's used, it's misused. There are few cases where it makes sense and does a good work. I gave one of these examples - I'm really happy with this new feature of DA, because it seriously cuts on page load times and in my case they were often horrible.

      Oh, and I still wonder why people think it is efficient to load everything upfront, regardless of if it is going to be used. Not only does it affect initial load time, it also affects overall resource use of the application in a negative way.

      because for the user there's way less difference between 40 and 50 seconds than between 0.5s and 3s. One long disruption of flow is way less annoying than lots of small ones. Ever used Windows running out of RAM and going on Swap? When you press Start, wait 5s for the menu to show, hover the pointer over "Programs", wait another 5s, move the pointer to "Applications" and from habit move it right, before the submenu opens, so Start Menu closes and you need to repeat, "start", 5s, "Programs", 5s, "Applications", 5s, "Notepad", 30s. But somehow people don't complain much about Windows load times. Don't you hate when you travel the directory tree and the computer freezes, while spinning up the CD to read contents because they happen to be linked? It could have done this before, while you didn't look. Maybe it would waste some resources. Maybe you wouldn't ever open the directory. But if you did, you wouldn't wait. CPU time is cheap. User time isn't.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    37. Re:Buzzword alert by ObsessiveMathsFreak · · Score: 1

      Slashdot currently serves static HTML pages. User clicks, a wad of text/html is sent to their client. No mess no fuss.

      With AJAX, Slashdot must serve terse content on the fly. Users will each request different updates, to different sections at different times. Th eserver will have to analyse th erequest, fetch the data from a database, and send that to the users. Searching a database is a far, far more computationally intensive operation than simply serving up a static webpage.

      If you decide to somehow solve this by feeding some kind of static "update page" to the AJAX clients, that won't work either. Most clients will get a lot of comments they weren't going to read anyway, so you've just wasted bandwidth. A lot of clients won't get what they want, or won't get it fast enough, so you'll have to either give them everything in the beginning and frequent updates, or go back to the custom request database model mentioned above.

      AJAX on Slashdot sounds nice in theory, but is in fact a rather silly idea.

      --
      May the Maths Be with you!
    38. Re:Buzzword alert by Vo0k · · Score: 1

      Okay, you use tabbed browsing, tricks that turn linear back-forward navigation into tree-like structure. It works, it works okay. But still the AJAX thing does it cleaner, faster, easier, more pleasant.
      (plus DA puts really LOTS of crap on each of the pages and on my low-end computer loading it even in a separate tab freezes the whole browser for a good while, but that's not something you should fix by using AJAX but rather by rethinking the HTML structure...)

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    39. Re:Buzzword alert by Temporal · · Score: 1

      I understand what you are saying, but I have no idea how you came to these conclusions, since they are completely wrong. AJAX would NOT require more database queries. In fact, a well-designed AJAX app would require LESS database access.

      Let me give you an example.

      I go to slashdot.org. First I receive the HTML layout and Javascript code bundle, which itself is obviously static content. The script then requests the front page article list. For most users, this list is identical, and therefore the Slashdot server can return a cached response. No database query is required.

      In fact, it can go further. Maybe I have my options set to filter out all posts by Zonk. Under the current system, the Slashdot server must apply this filtering dynamically, which probably means it can't serve cached responses for users like me. However, under AJAX, this filtering could be done client-side, so the server can respond the same as it would to anyone else.

      Same goes for comments. I click on an article. The AJAX app sends a request to the server for "All posts for article X with score 3 or more". This is a common request, so the server has a cached response ready to go. No database query required.

      But, say I have an option enabled to promote funny posts by 2 points. Now, under the static HTML scheme, this means that Slashdot can't serve that cached response anymore. It is forced to do a separate database query and rebuild the complete page. But, under AJAX, the client code could intelligently divide the request into two parts. First it would do the common request above, then it would additionally request "All posts modded funny with score 1 or 2". Although the latter request probably will require a database query, it is much smaller in scope, and should run faster. Again, the AJAX version is far more efficient.

      You seem to be dwelling on this idea of AJAX clients requesting custom updates to the data they already have. So let's try that. Now I want to know if any new comments have been modded up to score 3 or more since my original request. My client could issue a request like "All posts which were promoted to score 3 or more since time X", and another request like "All score changes made since time X for posts having score 3 or more". These requests would require the least bandwidth, but, as you have pointed out, they might be expensive for the server to process, depending on how the database is designed.

      So, OK, let's say it is discovered that these requests are way too expensive (or the programmers are too lazy to implement them). Instead, the AJAX client can be programmed to simply redo the original "All posts with score 3 or more" request. The server can then respond from its cache, avoiding the database. The client can do the work of reconciling this list with what it already has, or it can just throw out what it has and start over. In any case, this strategy would be at least as good as what Slashdot currently does, since under static HTML it would have to serve a new copy of the whole page.

      Or, you could have the best of both worlds: The AJAX client could send both of the above requests, and say "respond to whichever one you prefer". The server could then decide what to do based on its current load. If it has time to spare, it will go ahead and do the more expensive request to save bandwidth.

      Of course, all along, the responses to AJAX requests would be much, much smaller than equivalent HTML responses, since the AJAX responses only need to contain raw data, leading it to the AJAX client to add the formatting and layout client-side. So, lots of bandwidth would be saved.

      So, as you can see, an AJAX Slashdot would not only use far less bandwidth, but would actually reduce load on the server if written correctly. The point is, you can program an AJAX client to work however you want, and if server load is a big problem for you, then you can write your client to make requests in a way that reduces this load. You do not have this freedom with plain old HTML requests.

      Does this make sense now?

    40. Re:Buzzword alert by ObsessiveMathsFreak · · Score: 1

      Does this make sense now?

      No. I still cannot see how AJAX can magically make bandwidth "disappear" by implementing dynamic formatting. You seem to assume that Slashdot is already using such a database query system. It isn't.

      Content on slashdot is delivered using perl to generate html when customisation is needed. This introduces overheads, but is still a largely minor operation. Database caching is used to cut down substantially on overheads.

      With AJAX, you introduce search, communication and query overheads that a simple perl script based on string queries simply does not have. Users clients will request data all over the place, and with AJAX, typically there is no idle time as comments are constantly being retrieved and updated. In other words, AJAX clients will want "everything", and they will go looking for it. Otherwise, what's the point of AJAX? Your database caching will now have to cache "everything", not just what people are looking at.

      And the cost of such a system? Enormous. Both in terms of time, money, and testing. Not to mention the fact that javascript is not a standard browser feature. Many clients have it disabled. So now what? Serve HTML and AJAX?

      What's the benefit of AJAX? All that additional code and complexity for perhaps 20% bandwidth gain on markup costs? And how much of that will you lose on all the additional communication overheads and extra queries, not to mention all that unrequested data being shuffled to clients.

      Running AJAX on Slashdot would be like running a newsreader that fetches all messages _and_ their content on USENET. All you want with a newsreader is the headers, and then you decide if you want to get the rest of the message. This is what Slashdot currently does and this is the smart way to do it.

      If you've got some smaller site with perhaps 500KB worth of comments, fine, go ahead and use AJAX for that "loadless" feel, but be prepared to pay the price for it. On Slashdot, that price would quickly entail Taco's vaporisation faster than you can say "Skynet has gained sentience".

      --
      May the Maths Be with you!
    41. Re:Buzzword alert by Temporal · · Score: 1

      Running AJAX on Slashdot would be like running a newsreader that fetches all messages _and_ their content on USENET.

      There is no requirement that an AJAX client receive "everything". That's silly. When you use Google Maps, your browser does not download a map of the entire words. It only downloads what you're looking at. When you use GMail, your browser does not download your entire e-mail history. It only downloads the e-mails you click on.

      In reality, AJAX applications typically make the same pattern of requests to the server as simple HTML applications (as I demonstrated in my example), except that the responses contain only the relevant new data rather than an entirely new copy of the web page.

      All that additional code and complexity for perhaps 20% bandwidth gain on markup costs?

      The page I'm looking at right now is 5k in size. Your post itself is around 2k. An AJAX client would not have to re-download the page layout when I click to read your post; it would only download your actual post text. That's at least a 50% savings. However, most posts are significantly shorter than yours, while the page layout remains about the same size, making the savings even greater.

      Also, when I clicked the "reply" link under your post, Slashdot had to send me a completely new copy of the entire page, including your post, with a reply box underneath. An AJAX client would not even have had to make a request to the server.

      I'd conservatively estimate at least a 50% reduction in total bandwidth usage site-wide if Slashdot were entirely AJAX-based.

      Of course, the real advantage of AJAX is the ability to provide a better user interface, not the bandwidth savings.

  4. Madness the new reason? by Anonymous Coward · · Score: 0

    scnr

  5. For Your Clicking Convenience by Anonymous Coward · · Score: 3, Informative

    Netvibes, Protopage, Pageflakes, Live.com, and a bonus Google Personalized

    Ah hypertext links. What wonders have Tim Burners Lee wrought. And look, I'm anonymous so no karma whoring.

    1. Re:For Your Clicking Convenience by Flossymike · · Score: 2, Interesting

      Just to add to the url links, here's an interesting looking project:-

      http://www.eyeos.org/

    2. Re:For Your Clicking Convenience by MadJo · · Score: 1

      EyeOS, aptly named. That site just destroyed my eyes...

      gray on light green.. what a combination!

    3. Re:For Your Clicking Convenience by Anonymous Coward · · Score: 0

      The goggles, they do nothing!

    4. Re:For Your Clicking Convenience by Flossymike · · Score: 1

      Then you'll be glad to see that theme support has just been added.

    5. Re:For Your Clicking Convenience by MadJo · · Score: 1

      actually I meant the website... I'm sure they meant something nice, but lime green with light gray text is very hard to read, and will not entice me to try their product.

      First impressions and all that.

      I'm sure that the OS is pretty solid (at least I hope it is), but I just won't try it, if I have to destroy my eye-sight (I already wear glasses) just to find a download screen.

  6. A partial solution by JanneM · · Score: 5, Insightful

    I think Google and Gmail illustrate the limits of online apps (that would include Ajax as well as any other remote system). I see three basic issues:

    * I (like many others) use mail as a general information storage system. And whenever I'm offline, that information is unavailable. And yes, offline still happens quite regularily - there's still plenty of trains, planes, trainstations and airports, hotels and conference venues that don't have it, have it but at ridiculous cost, or have it but some random component is down leaving everyone offline.

    I need to have data cached locally - but if I'm going to have a local solution set up anyways I might as well go with that and avoid the hassle.

    * If I leave data at Google (or some other off-site organization), my data integrity is only as good as their security. That is something I do not have any control over and (as has been demonstrated) even supposedly very security conscious companies regularily goof.

    * Google and Yahoo have amply demonstrated a third issue: jurisdiction. If I have information stored with Google, I may suddenly be exposed to liability and possible data seizures in both my own country as well as Googles base country (USA at this time). If I am a company owner, do I really need the headache of reading up on data retention minutiae for a country on a different continent?

    As a private citizen, there are today plenty of books and audio recordings that are in the public domain in Europe but not in the US. Also, rules about fair use are different. If I store an mp3 of an early Elvis recording in a service run by a company that is based in the US, will I get hit by a lawsuit, or have my (perfectly legal) recording deleted with no warning? I do not need that headache.

    I think these kind of apps really will find their niche as internally run company-wide systems, where you have control, not primarily as the kind of third-party enterprises we usually talk about.

    --
    Trust the Computer. The Computer is your friend.
    1. Re:A partial solution by jetxee · · Score: 3, Insightful
      I would like to add to your three points (no offline availability, requirement for trust, jurisdiction issues) yet another three:
      • Backup. I case of GMail I may do backup with POP. In case of general web-desktop service I will not have such an opportunity. This is close to the concept of lacking `local cache'.
      • Permanence of service conditions. One may never be sure that the service he is using will remain available on the same conditions. I expect GMail to remain free, but I would not be amazed if any `no-cost' (or low-cost) web-desktop suddenly asks for some more compensation from me. They have my data. Why not?
      • Choice of environment. Now to change my computing environment I just need to copy my data and install appropriate software for the new environment. Even if I change an OS, it is not much a problem. I expect, it would not be so easy to move between remote web-desktops. Even further, I expect, that those desktop may discourage moving from web-desktop back to the traditional computing.
    2. Re:A partial solution by ^Case^ · · Score: 1
      That is something I do not have any control over and (as has been demonstrated) even supposedly very security conscious companies regularily goof.

      The question is: Do they goof more or less than you? I can relate to the idea that oneself is more concerned with the security of ones data, the question is if you really are better at securing data than a company or not. It might be true for a small minority but the population at large might very well have a lot better security by using these online services.
    3. Re:A partial solution by Jens+Egon · · Score: 1

      You should also be concerned about employees accessing from other nations.

      If your employee goes on a vacation in X-land and accesses his work account from there can local X-land police get to you?

      Can Homeland Security?

      If you need to answer these questions before using a service my guess is that yuo don't really need it that bad.

    4. Re:A partial solution by carlvlad · · Score: 0

      * I (like many others) use mail as a general information storage system. And whenever I'm offline, that information is unavailable I know how you feel. Having an online bussiness and constantly on the move has its down when you have no net access. My only alternative is to store data on my gmail account and visit it on my mobile at m.gmail.com

    5. Re:A partial solution by SillyNickName4me · · Score: 1

      the question is if you really are better at securing data than a company or not. It might be true for a small minority but the population at large might very well have a lot better security by using these online services.

      You don't have to be for 2 reasons:

      1. you are a less easy to find target
      2. there is a lot less to get from hacking your system then hacking a system that contains all your data besides that of thousands of others.

      No, that is not security through obscurity, it is looking at the risks and noticing they are a bit lower, hence you will have an easier time compensating for them with your security measures.

    6. Re:A partial solution by saltydogdesign · · Score: 1

      my data integrity is only as good as their security

      Point of fact: unless you are an expert, their security is probably better than yours. And the vast majority of people are not experts. You are welcome to keep your email on your machine. I do. But you can't ignore the benefit Google is offering to the masses.

      --
      // This is not a sig.
  7. Privacy and portabillity by rizole · · Score: 1, Offtopic
    How about a portable USB drive with Portable Firefox on?

    Add other portable apps and what else do you need? More storage space? How about a 20GB media player? Iriver works for me.

    1. Re:Privacy and portabillity by Anonymous Coward · · Score: 0

      How about a complete Linux OS on a USB drive configured to run everything through Tor, an anonymous overlay network?

      Buy it ready to go for $45 or build it yourself with 3 simple commands.

    2. Re:Privacy and portabillity by Vo0k · · Score: 1

      Been there. A Knoppix CD and a mp3 player for /home. Three months of heavy use (writing my thesis and lots of software associated with it, plus building a custom IDE for further work on that software). Ended up busting the Flash of the mp3 player.

      mp3 players use cheaper, less durable flash memory than pendrives - meant to withstand one-two write operations per block a day, for several years. If you perform 10 write operations a second (Firefox cache?) you will murder it really fast.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    3. Re:Privacy and portabillity by SillyNickName4me · · Score: 1

      If you perform 10 write operations a second (Firefox cache?) you will murder it really fast.

      Definitely.

      I'm currently building a bootable FreeBSD flash drive image for similar purposes. Having some experience with flash made for ensuring the Cache dir points to a memory file system.

      Yeah, cache is gone after reboot, but that is not as big an issue as the speed at which you waste flash memory otherwise.

      Of course one could also only cache to memory... but somehow I have bad experience with doing that (mostly firefox starting to eat memory like nothing)

    4. Re:Privacy and portabillity by Paraplex · · Score: 1

      I agree, portability appeals to me.
      There are two things i'd like to see:

      In the short term I'd like to see a portable interface, so I can bring my windows mouse gestures, keyboard macros saved passwords etc to other computers and just utilise their processing power. I customise my interface as many do, to the point where it is vastly different from others. I can only see interface diversity increasing in the future.

      The other is I would like the data throughput of the net brought up to a speed that can handle the information on a screen and the keyboard & mouse information in real time.
      My mind can only ever access 1280x1024 pixels of data and keyboard/mouse input at any given moment (more as the HCI advances) so the HD space & speed of the interface computer becomes redundant. We should really work on taking advantage of this to decentralise rather than shift the centralisation to corporations.

      Perhaps if remote desktop became more user friendly and accessable, companies could host processing farms and you could use your own portable OS to access as many processors as you could afford for a given task.

  8. Need an offline "backup" application by broothal · · Score: 2, Insightful

    I used to think this would be the future, but my views on that has changed. Lately, it's been very obvious that any script-kiddie with control of a sufficient amount of compromised machines (zombies) can ddos any webserver, almost regardless of the capacity of the datacenter.

  9. Left hand, meet right by 1u3hr · · Score: 1
    Saying 'No' to an Executable Internet.

    His point basically was that MS will bulldoze its version of an Internet desktop to become standard, with their famous attention to security. Maybe overstated a tad, but nowhere in the current FA were the issues of data security, from accident, malice, government, hackers, big companies... addressed.

  10. Reliability? by cperciva · · Score: 4, Insightful

    Will concerns about privacy and reliability kill these or is this the wave of the future?

    If you think reliability is likely to kill this, I have two questions for you:
    1. When was the last time Google stopped working?
    2. When was the last time Windows stopped working?

    The simple fact is that a single centrally administered server farm is vastly easier to administrate -- and will be vastly more reliable -- than a hundred million home PCs, most of which are managed by people who are vastly less competent than the average server farm administrator. Of course, if Windows broke and your home PC isn't working, you won't be able to use it to connect to sites online; but this isn't much of a problem. People care far more about their data than their hardware; if all else fails, they can borrow a friend's terminal.

    Privacy and security, on the other hand, are much more serious issues; but (sadly) I don't think they have much chance of stopping something like this. Computer security is something which most people simply don't understand.

    1. Re:Reliability? by killjoe · · Score: 3, Insightful

      Google stopped working when windows stopped working.

      Something to think about who wears the pants in that relationship.

      --
      evil is as evil does
    2. Re:Reliability? by Vo0k · · Score: 4, Insightful

      Worse.

      Google stopped working after last storm that broke my ISP's router.
      Google slowed down to a crawl when I was delaying paying my ISP bills.
      Google stopped working when the Ethernet plug got loose in the hub.
      Google stopped working when power supply in my firewall box died.
      Google stopped working while the ISP network was down for maintenance.
      Google stopped working when the local DNS got poisoned.
      Google stopped working when a neighbor was driving his car with broken ignition near the WiFi accesspoint.

      Common home networks are too unreliable to base your desktop and mostly everything you do on them.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    3. Re:Reliability? by matvei · · Score: 1
      When was the last time Google stopped working?

      Let's see.. the last time was when my ISP was doing some upgrades. Both Windows and I kept working without Google, though.

    4. Re:Reliability? by BenjyD · · Score: 1

      Exactly - the internet connection is pretty much the least reliable part of any home computer. What would probably happen is that web app developers will realise this and start pushing more of their webapps client side for reliability, until we end up in exactly the same position as today, except with our apps written in javascript.

    5. Re:Reliability? by Angostura · · Score: 1

      1. When was the last time Google stopped working?

      Just now, when I was in a taxi and there was no wireless coverage.

    6. Re:Reliability? by Tim+C · · Score: 1

      1. When was the last time Google stopped working?

      I've lost access to google for various amounts of time due to:

      * my ADSL link going down
      * google deciding to temporarily block my subnet due to excessive traffic

      In all of those times (and the first happened a lot for a number of months until I bought a new router) Windows was just fine.

      Also, as others have pointed out, if Windows goes down, so does your access to google...

    7. Re:Reliability? by SillyNickName4me · · Score: 1

      1. When was the last time Google stopped working?

      A couple of hours ago when my internet connection was down (ok, not their fault, but it doesn't matter for me, I cannot use the g* apps, and that is what counts)

      2. When was the last time Windows stopped working?

      In my case, about a decade ago, I replaced it with something that was more of my liking, that I got a say in (ok, a small one, but still), and that turns out to be utterly reliable and stable for local applications.

      The simple fact is that a single centrally administered server farm is vastly easier to administrate

      Slightly easier then fixed function distributed environments. The trick is stopping users from changing the system, a central server may help in that but is nowhere a requirement.

      A central service of some sort is a requirement for centralized administration of course.

      At any rate, it quickly becomes a lot more difficulkt to administer when having to cater to the requirements of different users, and not having 'company policy' dictating what a user is supposed to do.

      -- and will be vastly more reliable

      It will only be as reliable as the conenction between it and the intended users, lots of things outside your control on the way that can go wrong.

    8. Re:Reliability? by Anonymous Coward · · Score: 0

      You can go "administrate" all over yourself. Try "administer" instead.

    9. Re:Reliability? by Qbertino · · Score: 0

      2. When was the last time Windows stopped working?

      Must have been 3 or 4 years ago when I stopped using it. OS X crashed once on me (some obscure OSS game I think it was) and Linux like once or twice.

      --
      We suffer more in our imagination than in reality. - Seneca
    10. Re:Reliability? by DJK · · Score: 1

      > Google stopped working when windows stopped working.
      >
      > Something to think about who wears the pants in that relationship.

      Funny, Google worked fine for me the last time Windows stopped working.

      Of course, Google was loaded on my other PC running Firefox on Ubuntu... :-)

    11. Re:Reliability? by muellerr1 · · Score: 1

      3. When was the last time World of Warcraft stopped working? Oh, wait...

    12. Re:Reliability? by LurkerXXX · · Score: 1

      3. When's the last time the feds came to your house and pulled a bunch of you data off your machine?
      4. When's the last time the feds went to Google and potentially pulled a bunch of your data off their machines?
      5. In which case do you think you might actually get a notice that they took your data?

    13. Re:Reliability? by nigham · · Score: 1

      1. When was the last time Windows stopped working?
      2. When was the last time Windows stopped working?


      I don't know about Windows, but I just can't remember the last time Linux stopped working. Google stopped working a few hours ago, when for some reason my ISP's DNS server went down.

      --
      I don't want to read /. I want to go home and re-think my life.
  11. There is one true thing about the internet by Anonymous Coward · · Score: 0, Funny

    And that is someone will proclaim THE REVOLUTION THAT WILL CHANGE EVERYTHING FOREVER at least once every three months

  12. online!=always available by J0nne · · Score: 3, Insightful

    If you rely on webapps exclusively, you can't reach your information all the time. Your internet connection could drop out, or you could be someplace without an internet connection (wardriving might be easy, but I never find an open access point when I need one).

    Webapps complement regular apps, they don't replace them. It's good that websites are finally feeling more like real applications, and it's nice to be able to reach your information from everywhere, but they'll never replace them completely.

    Why does one technology have to kill the other technology? Both can coexist fine. I use Gmail, but I still use Thunderbird to read and send my e-mail when I'm at my computer.

    1. Re:online!=always available by pho3nixtar · · Score: 1

      It has to kill the other so there can be more of a monopoly on information and the access to that information. At least, that's the conspiracy. To me the whole idea of a hardware-less platform is purley contradictory - how on earth do you access live.com without some sort of handheld/cellphone/laptop/whatever device? Does live.com literally appear out of thin air as if we were living in a perpetual holodeck? Always available? HA! That's bunk, and they know it. It's just marketing hype.

  13. Online apps the new desktop? by Jugalator · · Score: 3, Insightful

    Online Ajax Pages The New Web Desktop?

    I think I'd be happy to see this... as long as the Internet transfer speeds would equal that of a hard drive, and I wouldn't have to pay just to stay online and do my work.

    --
    Beware: In C++, your friends can see your privates!
    1. Re:Online apps the new desktop? by SanityInAnarchy · · Score: 1

      I wouldn't.

      There's a very simple reason for that. I like being in control of my data. And when I found that the only reliable way to do that was to ONLY access web resources from my desktop or laptop, even if they were on my own server, I lost much of the inscentive for putting my stuff online in the first place. After all, desktop/laptop are both Unix, so I can rsync anything that isn't on the server already.

      --
      Don't thank God, thank a doctor!
  14. Is this the wave of the future? by cerberusss · · Score: 4, Funny
    Is this the wave of the future?

    No.

    --
    8 of 13 people found this answer helpful. Did you?
    1. Re:Is this the wave of the future? by antic · · Score: 1
      Is this the wave of the future?

      No.

      This is the wave of the future.

      --
      'Thats they exact same thing a banana wrench monkey.'
    2. Re:Is this the wave of the future? by cerberusss · · Score: 1

      I get strong vibrations from that bear.

      --
      8 of 13 people found this answer helpful. Did you?
  15. Rage of the Future....for a while by bm_luethke · · Score: 2, Interesting

    General consumers do not care about privacy until they get bit by it or a "trustworthy" news agency makes it sound like the whole world will collapse.

    That's not really being stupid - just relativly uneducated and most people are too busy with other things to really think it through. I talk people out of using this type of stuff all the time - simply tell them how it can be abused. Until then they usually just look at the marketing hype about how useful it is when it works.

    The first major public group that looses something important through a lack of privacy and it will stop. Just as people didn't lock doors at the turn of the century (who cared about privacy?) once it was obvious it was going to be taken advantage of it changed. Though it will probably swing back too far the other way in trusting almost nothing.

    But hey, maybe they will fix thier privacy issues too, it *could* happen.

    --
    ------- Sorry about the spelling, I suffer from two problems. Dyslexia makes it difficult to spell well, lazy makes it
  16. XUL by pubjames · · Score: 3, Interesting

    The problem with AJAX as I see it is that it is a bit of a Kludge.

    Why did XUL never take off? I think that is a really interesting technology, much better than AJAX, but I guess being mozilla only it will never really reach mainstream? I guess it wouldn't be possible to create a XUL plug-in for IE?

    1. Re:XUL by Vo0k · · Score: 3, Informative

      XUL is a language for writing GUI looks with room for hooks. It's not all that much better than HTML for it. Both for XUL and for HTML you need the same Javascript backend, and if given JS backend to HTML includes xmlhttprequest() for dynamically changing the HTML content (through DOM tree), it's called AJAX.
      The kludginess of the solution lies in less-than-perfect reliablity of xmlhttprequest and hideous access to the DOM tree in JS. (e1=document.getElementById('e1'); e2=document.createNode('H1'); e2.value=reqResult; e1.parentNode.replaceChild(e1,e2); e2.id='e1';)

      With XUL it would look just the same, very similar DOM tree with the same hideous access methods, same unreliable xmlhttprequest and only different tag names. It could look differently, it could be more sleek as a GUI because it was meant to be a GUI in the first place, but it would be just as kludgy inside.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    2. Re:XUL by Gavin86 · · Score: 1

      I'm a bit late to the game and have no personal perspective on XUL (I'm a youngin'), so forgive me if I seem out of touch.. I'm not sure why it -hasn't- taken off.. But what I do know is that I have been experimenting with it a lot lately, and I greatly enjoy it! Currently, popular Mozilla-based applications such as Firefox and Thunderbird are on track to be integrated with XULRunner (which recently achieved version XULRunner 1.8.0.1 as a developer preview!), so hopefully this will give XUL a little kick in the pants, something I would love to see :)

      From one of the XULRunner pages, "The goal of XULRunner is to provide a solution for deploying XUL applications (primarily Firefox and Thunderbird), as well as providing an embedding mechanism."

      --
      "Progress comes from the intelligent use of experience."
    3. Re:XUL by Florian · · Score: 1

      XUL did take off as the framework for Mozilla/Firefox plugins and crossplatform applications (including Sunbird, Songbird etc.). But it was never intended to be a replacement for web applets - for good reasons, since it offers no sandboxing and no safety constraints for code. Making the XUL interface world-writable from web sites would be the ActiveX fiasco all over again. This is why Firefox tries its best to prevent XUL plugin installations from untrusted sources.

      --
      gopher://cramer.plaintext.cc http://cramer.plaintext.cc:70
    4. Re:XUL by kyofunikushimi · · Score: 1

      Javascript's DOM access is hideous? I've always thought it was rather straightforward and relatively powerful. How would you do it?

      --
      oo
    5. Re:XUL by Vo0k · · Score: 2, Informative

      document.e1.modeType='H1'; document.e1.value=reqResult;

      or

      e1=document.createElement('h1',id='e1',value=reqRe sult);
      document.e1.replaceWith(e1);

      or generally anything that would make it less verbose. Every smallest operation requires kilometers of DOM methods. Why the hell call parentNode.replaceChild() if you know the element you want replaced and you're really not interested in the parent? Why fun, pleasant methods like innerHTML are essentially made useless in the specs? ('adds a new page in history stack' or something). Why not push around some plaintext HTML strings and then call something like document.rerender(); to apply changes? Why no easy aggregation methods of changing multiple things at a time? Why no new data types that support new kinds of values? (document.class('header').style.fontSize+='1px'; document.form2.replyarea.style.{height:"5em + 8px",padding:"4px"} ?

      Sure it IS powerful. But
      - you need to spell out the least detail of everything you want. No 'default actions', want an element? First specify type, then create attributes, one a time, then find the location of the parent in the tree, then use not-too-fun methods to put it at desired location between the children.
      - Awkward traversing of the element tree. this.parentNode.nextSibling.firstChild ? or document.forms[1].radio2[4].checked ?
      - Extreme verbosity. e=document.pleaseVeryMuchGiveMeAnElementWhoseNameS oundsLike('x');
      - Specs asking to shoot yourself in the foot. (are newlines between tags 'textNodes'? How to find first non-textnode child of an element easily then? When ".value" is equal to innerHTML and when it's something different?)

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    6. Re:XUL by kyofunikushimi · · Score: 1

      Okay, very valid points. I agree with you on most points: Adding one attribute at a time can be time consuming, though i suppose you could write a function and pass it all the values and let the function handle it for you (though that certainly wouldn't limit the number of bytes involved). Traversing the tree can be relatively cumbersome, but at least it is _somewhat_ standard. Replacing children and oh-my-god-insertBefore absolutely suck.

      I think, though, that a lot of this is encumbered by not being able to swear up and down that the data is valid xml data. Javascript can't be allowed to die a horrible, horrible death upon finding nodes that are a little out-of-spec. If all the data was in xml format, then why would you expect to be able to pull plaintext (containing line-breaks) out of a paragraph? should pulling the textual data from <p>some text<br />some more text<p> really return <br /> as part of the text string? Should it return all the text minus the break? I think the current implementation (a collection of two text nodes and a br node) makes more sense those two options.

      And more importantly, is there a programming language that already handles this in a sensible and concise manner? Something that can set the stage? I haven't played with the DOM in anything other than javascript and php.

      Thanks for the insight(s). I really am curious to see if there are some really good implementations of DOM parsers out there.

      --
      oo
    7. Re:XUL by Vo0k · · Score: 1

      Adding one attribute at a time can be time consuming, though i suppose you could write a function and pass it all the values and let the function handle it for you

      You can write a function to do everything. You can write perl interpreter in Javascript and that would certainly speed up development of further programs (writing in Perl is very fast and easy) but I guess that somehow misses the point.

      I think, though, that a lot of this is encumbered by not being able to swear up and down that the data is valid xml data. Javascript can't be allowed to die a horrible, horrible death upon finding nodes that are a little out-of-spec
      Some of it, true. Most of it is just some legacies of design though, I think. Quite a few things could be made easier without loss of "durablity".

      Grabbing content of <p> like in your example sure makes sense.
      But what about this:
      <p>[\n]
      <b>Hello World!</b>[\n]
      </p>

      The specs say the single newline should be ignored. So some browsers ignore it by not rendering it, but the DOM still contains a text node consisting of a single linebreak before <b>. Some browsers ignore it totally, removing it from DOM. Shooting in the foot. Sure in your example <p> had 3 legal children. In my example it has between 1 and 3 depending on implementation. Which option is correct?

      And more importantly, is there a programming language that already handles this in a sensible and concise manner? Something that can set the stage? I haven't played with the DOM in anything other than javascript and php.

      If there is any, I don't know it. But I just mean we are stuck with uglinesses of javascript DOM in AJAX, no matter if it's underlying HTML, XUL or whatever else.

      And don't get me wrong. It's powerful, it gives a lot of possiblities, it is quite reliable and has a lot of virtues. But it's really ugly. The backend is strong and reliable. But the "DOM Frontend", syntax, functions, programmer's interface, this all is one horrible kludge that shouts "ICK!" and should be rewritten from scratch.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    8. Re:XUL by misleb · · Score: 1

      A couple issues with XUL:

      1) Very Mozilla centric
      2) Not very well polished. This goes along with 1). Mozilla develoopers have only developed XUL as far as Mozilla/Firefox interface required. Although I imagine that widespread applicaiton development woudl solve this.

      That said, I have written an XUL application (which uses AJAX to comunicate with a server for data) and it was pretty good. A lot more "desktop-like" than any HTML solution. It actually has real widgets rather than the CSS/JS hacks you see for HTML. Plus a real box-model layout system.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  17. Web 2.0: The Jakob Nielsen Nightmare by thespace101 · · Score: 1

    I could just imagine a blind person listening to his/her Web 2.0 Desktop. Web 2.0 is b.s. unless used wisely under normal usability standards. And as far as I'm concerned, Ajax desktops are still a pipe dream. Get widgets, get a mac.

  18. Ajax all you want by palad1 · · Score: 2, Informative

    But please make your ajax scripts available through https or half of the corporate users won't ever stand half a chance of seeing your 'loading please wait' splash screen...

    Hint: https://mail.google.com/mail (thanks google)

    1. Re:Ajax all you want by oni · · Score: 1

      make your ajax scripts available through https or half of the corporate users won't ever stand half a chance

      corporate users aren't allowed to use http?

    2. Re:Ajax all you want by palad1 · · Score: 1

      Nops, but they are allowed to use http through often poorly configured proxy which tend to cache or sometimes just not serve application/javascript mime type.

  19. Better solution by newend · · Score: 1

    Get our network infrastructure updated so we can connect via remote desktop, vnc, etc. and have a useable connection to our home systems.

  20. Application Layer on top of Application Layer by layer3switch · · Score: 5, Interesting

    Although I do think, Ajax with javascript/dhtml is pretty cool, it's a bit overkill to think that it will be the "desktop" platform of the future. My beef would be an idea of a secondary application layer (only logical, not literal) over OS and within browser application framework. The shared load between Javascript JIT compilation and native applications to make Ajax application smooth, stable and functional would be hard to implement especially for portable PDAs with underpower processors and limited memory and buffer cache. Not to mention Ajax applications will always have to be confined within browser application, not able to compete with multithreaded and compiled bytecode applications.

    Try benchmark Javascript against your machine here;
    http://www.24fun.com/downloadcenter/benchjs/benchj s.html

    I think, for web "desktop" to be successful and attractive for "users," the web browser platform itself has to change dramatically to give Ajax applications an development edge and ability to compete with native applications. Otherwise similar fate of Java Applets may be ahead for Ajax.

    --
    "Don't let fools fool you. They are the clever ones."
    1. Re:Application Layer on top of Application Layer by Rob_Warwick · · Score: 1
      Ajax with javascript/dhtml

      Quickly querying Google to make sure I've got my definitions right, DHTML is a combination of HTML, Javascript, and CSS.

      Asynchronous Javascript and XML with Javascript/HTML, Javascript and CSS.

      Mmmm...buzzword redundancy.

    2. Re:Application Layer on top of Application Layer by layer3switch · · Score: 1

      hmm, let me clarify...

      Ajax using JavaScript coding or combination of JavaScript, HTML, CSS such as DHTML coding...

      You know what I mean...

      --
      "Don't let fools fool you. They are the clever ones."
    3. Re:Application Layer on top of Application Layer by Rob_Warwick · · Score: 1

      Sorry, not meaning to poke fun at you. The intention of the comment is to make a joke out of how many different ways we describe what's essentially the same thing.

    4. Re:Application Layer on top of Application Layer by Anonymous Coward · · Score: 0

      Under powered processors in PDAs? Most new processors are 200 to 400mhz+! Now, I don't know about you, but in circa 1999 my IBM Thinkpad 600e was ALMOST at 400mhz, with a whopping 395mhz. Under powered? No, the mobile devices are quickly catching up to our main machines.

    5. Re:Application Layer on top of Application Layer by Bloke+down+the+pub · · Score: 1

      Whenever I see the word javascript, I think "which one?".

      --
      It's true I tell you, feller at work's next door neighbour read it in the paper.
  21. It's... by ShaolinTiger · · Score: 2, Insightful

    Not like we have a WHOLE load of privacy online or offline now, your PC is under the jurisdiction of the government if they so wish to search it, what's the difference with storing it online?

    Even if you encrypt it you have to give up the key or go to jail.

    Why not just sit in your tin-foil hat with a copy of DBAN boot-and-nuke in the drive ready at all times..

    --
    Share your Knowlege - Kung-Fu Geekery
    1. Re:It's... by miro+f · · Score: 2, Interesting

      the difference is that if the information is stored on your computer, the feds can't get to it without a search warrant

      if it's online, they only need a subpoena. Much easier to get, however, if it's a serious issue I don't think they're going to give up just because they need a search warrant.

      however, look at the recent DOJ subpoena. There's no way they can subpoena information that is on your computer. so there's a difference. If you're doing illegal stuff, you would have to be a moron to do it through a medium that stores all your information online

      --
      being vague is almost as cool as doing that other thing...
    2. Re:It's... by Anonymous Coward · · Score: 0
      Even if you encrypt it you have to give up the key or go to jail.
      Not to go off on a tangent, here, but am I really the only one who'd go to jail before giving up his encryption keys without a grade-A damned good reason?

  22. Due to moving I switched ISP's by SmallFurryCreature · · Score: 2, Interesting
    Not my choice but that is live. Anyway I went from xs4all.nl to tiscali.nl Now those who are dutch might already know what is going to come next but for the 99% of /. readers who aren't let me explain. xs4all is a bit crap, they are expensive, their helpdesk is always busy and they have network problems from time to time. In short, they are the best.

    Odd conclusion? Well no. They are expensive but that is because they do not actually have a datalimit, or rather you have one 100gb on my account but they don't actually measure your data throughput. Tiscali does and the limit is 1gb for half the price. Mmmm. 40 bucks for 1gb or 80 for unlimited.

    Next is that their helpdesk is always busy, this is nasty but at least the helpdesk fucking knows their business AND is available in the weekend. Oh and their online help is good enough that the only thing I ever needed from them is password resets.

    So who cares about this? Is this on topic? Well no but I am getting there. Next is reliability. I said xs4all sucks? Well it does, it always managed to drop my connection at least once per month. Fucking annoying.

    Offcourse that was until I moved house and now am on tiscali. Wich drops the con every 10 minutes. Suddenly the internet is totally different. Even simple browsing becomes a pain when every 4th click results in a minute long wait for the modem to reconnect.

    Why is it crap? Oh who knows. I actually have worked for tiscali (then worldonline) in the distant past and they never struck me as the brightest bulb (they hired me after all) but perhaps it is just the phone line.

    But it really doesn't matter. On my old con it was already troublesome that a couple of times per year I could not google or whatever but with this ISP can you imagine using web apps? It would be like trying to do work on windows 95 adware edition.

    And that is my fundemental, and I think everyone elses, problem with the whole idea of webapps. Very nice until your connection drops out.

    As long as we got joke ISP's with idiotic data limits web apps are never going to take off. Think of it like this. Who here does not have some kind of emergency equipment like a flashlight for when the elec drops out or camping gas stove for when the gas drops out? And that is (at least in holland) extremely reliable stuff. Trusting my internet connection to determine wether I can work or not does not sound very smart to me.

    Oh and as far as mobile computing is concerned. Those who can afford mobile connection costs don't need it, they got secretaries and those who need it can't afford it.

    You can forget the net 2.0 the same problem that killed the 'bubble' ideas of the net are killing any new ideas. The ISP's simply ain't up to the task of providing reliable constant connections. Oh the better ones come close but xs4all in holland is tiny. The best and reviewed that way by consumer organisations but still tiny.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:Due to moving I switched ISP's by SillyNickName4me · · Score: 1

      Hrm, wtf move to Tiscali? I am not aware of any location within the country where Tiscali has coverage and XS4ALL doesn't.
      Oh, and when you had to leave XS4ALL anyway, I'd have gone with Versatel before Tiscali (despite having family working at Tiscali and being able to get a reduced price for my subscription). Versatel has so far served me well (for about 3 years now). Have had 2 connection drops over the last 6 months, and those usually happen during the night. Getting the promissed download speeds (not on adsl2 here btw, only 'regular' adsl, but 12mbit downstream is what they promise and what I am getting most of the time)..

      I have yet to get any complaints from them about data limits (while 100GB+/week is no exception for me at all)

      Yeah, their helpdesk sucks (tho got a lot better over the last year) and they are not the cheapest,

      At any rate, they make for an alltogether better choice imho.

      Oh... this was about AJAX... sorry for the off-topic rant :)

    2. Re:Due to moving I switched ISP's by moonbender · · Score: 1

      Aren't there any better options for you? I always figured Holland to be some sort of internet heaven, you always seemed to get the good stuff some time before we did. If I can get 6 Mbit and no cap for 50 Euros, so can you! No? Maybe moving wasn't such a good idea. ;)

      --
      Switch back to Slashdot's D1 system.
    3. Re:Due to moving I switched ISP's by swilver · · Score: 1
      We can get 6 MBit no cap for 50 euros, and xs4all has full coverage as far as I know, so why he switched to tiscali is beyond me.

      I'd never switch from xs4all. They offer unlimited bandwidth (even in their fair use days), allows you to run servers or connect as many computers as you wish (we had a company of 100 people running on a few of their "home" connections), they give you a fixed IP, the line drops literally once a month at the most, bandwidth is always what they advertise (I never had any congestion problems), support Linux, etc..

      They're not the cheapest ISP, but I doubt any of the others comes close to their reliability or service.

    4. Re:Due to moving I switched ISP's by Aceticon · · Score: 1

      Cable is relativelly good (4Mb/s, unlimitied data traffic, 45 EUR/month) if you're in an area with good cable connections. However if you're in an area with old cable installations (eg Amsterdam) it's sheer hell.

      Reliability isn't bad (about one serious connection drop per month).

      Oh, and their support is pretty much clueless and seems to have recently been outsourced to Belgium.

      In general in Holland there are a lot of choices on the lower end of the market (the 256Kb/s for 12,5 EUR kind of thing), but less so at the higher end. Due to the above mentioned issues with cities with old cable installations, some people don't have access to reliable cable internet, thus leaving only ADSL as an option.

      PS: In Holland XS4ALL is available with ADSL. They have long been known as the techies (i'm avoid saying hackers here 'cause people confuse it with crackers) ISP in the sence that they're support is not clueless, they don't simply give away any user's information without a court order and they don't do any sneaky blocking of ports for P2P or home servers.

    5. Re:Due to moving I switched ISP's by SmallFurryCreature · · Score: 1
      Perhaps I should have explained, it ain't my con. I am sharing it with another tenant and he barely uses it. In fact he thinks that it is normal for adsl to behave like this.

      Not my choice until I get a house of my own again.

      --

      MMO Quests are like orgasms:

      You may solo them, I prefer them in a group.

  23. Scary news by Exaton · · Score: 3, Funny

    "roaming Ajax desktops"

    I swear that statement would scare my mother.

  24. Subscription model by jaymz168 · · Score: 2, Interesting

    We've all heard over the last few years that Microsoft et al want to move all their software to a subscription model. Gone will be the days when you pay for a piece of software once and it just works for a very long time. This isn't going to happen overnight, but this all ties together and that's where these guys want this to go. Thank god for F/OSS.

    1. Re:Subscription model by dustmite · · Score: 1

      So the future is 'like UNIX but with a subscription model', hooray!

      Seriously, I remember being able to access my UNIX desktop from anywhere in the world already ten years ago. The media rage about the idea as if it's some coming wave of the future, and certain companies market it as such as they add more elements from UNIX over the years to their systems. But the media rage about it as if it's new because they don't know any better - I mean, they don't know what UNIX is and what it could do 20 years ago already - and although that's partially symptomatic of what's wrong with modern "journalism", it's also perhaps a sign of the failure of the UNIX and F/OSS "communities" to market their solutions better.

  25. False premise. Next article! by Max+Threshold · · Score: 3, Funny
    "With our existing models for operating environments aging badly . . ."

    sh has aged very well, thank you very much.

  26. theres a good side to this by wwmedia · · Score: 4, Insightful

    Theres a good thing about remote applications

    if theres a security bug,
    ALL the clients can be fixed in ONE update

    none of that microsoft / symantec patching every so often business

    1. Re:theres a good side to this by raynet · · Score: 1

      But if there is a security hole, all client data could be stolen before the update is installed. With local apps you could add extra security whatnot, but with remote apps all your eggs are in one basket.

      --
      - Raynet --> .
    2. Re:theres a good side to this by SillyNickName4me · · Score: 1

      Theres a good thing about remote applications

      if theres a security bug,
      ALL the clients can be fixed in ONE update


      There is a bad thing about centralized remote applications

      if there is a security bug
      ALL clients get compromised at the same time.

    3. Re:theres a good side to this by earthbound+kid · · Score: 1

      Haven't you seen "I, Robot" starring Will Smith!? Once the master computer turns alive and evil, it will use auto-update to infect every computer/robot in the world! Turn off auto-update now, while you still have a chance to enjoy Converse tennis shoes and [insert product placement]!! If you don't, the consequences could be dire.

      This message brought to you by Sony Home Entertainment.

    4. Re:theres a good side to this by MasterC · · Score: 1


      if theres a security bug,
      ALL the clients can be fixed in ONE update


      Except the browser isn't a remote application. "They" can't even get something like HTML, CSS, or javascript to work the same across browsers, so why should security be any diffferent? Generally: a security hole in your remote app (SQL injection) leads to losing control of that information; a security hole on your browser or server (WMF exploit) can compromise the whole machine.

      But, yes, finding a bug in your app avoids having to make millions of individual updates. Definitely a plus. Just saying that that is not the end of the story. Just look how prevalent IE & Outlook exploits were/are/will be -- virus scanning/Windows update will still be needed to some degree.

      --
      :wq
    5. Re:theres a good side to this by StikyPad · · Score: 1

      if theres a security bug, ALL the clients can be compromised in ONE vulnerability

      There.. fixed that for you.

  27. The problem... by Gavin86 · · Score: 5, Insightful

    The problem I see with AJAX technologies is that almost none of them have been put to any good -use-. Everyone keeps talking about the 'potential' of such applications, the 'implications' AJAX-like setups can have for software and desktops.... But how many actually -useful- applications do I use a day? What, Gmail? Every now and then when I get directions or I'm board enough to check the satallite photos, Google Maps. And really, those things are the cream of the crop for AJAX applications. Most other sites integrate AJAX in a small way, ways that are helpful and I'm sure appreciated by their users, but nothing earth shattering and certainly nothing that ushers in the obvious defeat of the modern desktop as we know it. Most of these things are subtle improvements on an existing platform.

    Frankly I would be both a bit suprised and pissed if the user interface of webpages -didn't- evolve into something much more responsive and a bit more slick. Am I the only one who sees this as a completely expected progression and not the eXTreM3 R3V0LUTION 3.0??

    I understand AJAX from a technical perspective, I've made a few "AJAX" applications myself, I just don't see the results and the real world practicality to back up the absurd wave of hype. Consider me slightly amused and half-interested until I see the types of applications that fundamentally shift the ways I'm using this machine as I've been promised.

    I'm new to the business world and particuarily the business/marketing aspects of software developement and website design, but do all industries act like this? Am I getting bent out of shape over nothing, or is the hyperbole really hitting the roof on this one?

    --
    "Progress comes from the intelligent use of experience."
    1. Re:The problem... by Tarwn · · Score: 4, Insightful

      Excellent, if I had mod points I would have burned some. I completely agree. Everyday some new set of articles is posted about "Web2.0", etc and yet things like AJAX don't seem to be revolutionary as much as small steps and, in most cases, gap fillers.
      I've written some "AJAX" stuff in the past. Granted only a few of sites I wrote using javascript and asynchronous XML calls were written after there was a name for it, but as the parent poster said, it is not revolutionary. There are some sites out there that are heavily AJAX-ified. Some of them are useful, some of them are just feature-filled for features sake. In most of the cases I have seen, though, AJAX has been used to fill the gaps, as a polish, if you will. Now don't get me wrong, this is not a bad thing, but even GMail and Google maps are far from the promised revolution we read about in articles such as this.

      All this AJAX "revolution" does for us is allow us to treat the frontend web page as a bit more of a client, as opposed to treating it as content in a thin client. Flash did as much, if not more. The only difference here is that AJAX isn't a platform that requirs a plugin, it is instead (at it's core) a group of existing plugins accessible by the browser. How long has AJAX been around as the cool, hip thing? It's already available to every developer with notepad/vi and a browser, it's not very complicated to implement, so where is this revolution that has been remarked on since the day it got an acronym all it's own?

      And a commentary on the original article: I lost interest in reading it right after the author said that our OS's are out of date and what we really need is a web-based desktop to truly leverage all of the fantastic capabilities of our machines...right. I didn't look too closely, but to me it just looked like he was selling start pages, similar to what Yahoo and many others have had for ages...personally I like my desktop environment to do a little more.

      --
      Whee signature.
    2. Re:The problem... by FlynnMP3 · · Score: 1

      The original article is an opinion piece. While they bolster their argument with existing AJAX technology pages, it doesn't change the fact that the author is extrapolating in hopes of being correct.

      AJAX is a tool like everything else. It is not the end all to be all that some people may think it is. Some existing web based operations benefit from it, but quite a few won't. Security concerns are huge and most people haven't realized that yet. For example, you wouldn't want your online banking information flying around on the Internet in a spiffy new AJAX front end. The client side javascript has nearly all the algorithms to decode the information coming back from the bank servers. Not good.

      In my opinion, AJAX works fine in trusted networks (like business intranets) and a few support critical areas. Other than that, it will be a nice tool for web toolkit designers to use when making the next version of blogging software or something like that. Using AJAX effectively requires design knowledge of three tiered systems. Without tools for the greater public to use, AJAX is a non-starter.

      -FlynnMP3

    3. Re:The problem... by ducttapekz · · Score: 1

      I understand that it much of this does seem like the next progression and expected progress, but that doesn't make it less interesting. The next progression for cars is supposed to be better gas mileage and flying. I'll still be excited when that happens even though we all expected it by the year 2000...

    4. Re:The problem... by Anonymous Coward · · Score: 1, Interesting
      There are other useful ways in which "AJAX" (yuck, hate that term) can be very useful and non-obtrusive.

      For example, check out http://svn.code-host.net/svn/Insurrection/ for some ways in which this can be used in "minor" but very "useful" ways. (That is, the site does not depend on it but it is much nicer and lower bandwidth due to it)

    5. Re:The problem... by swilver · · Score: 1
      For me it is the biggest hype there is, and having seen (in 2004) a perfectly good web application being completely ruined because the marketing department thinks it would be "bitchin'" to have tabs, sortable grids with draggable columns, checkboxes that change content when they're checked, a window manager and a menu bar (inside the web window) (trust me, it was totally insane).

      Not only could we only support Internet Explorer (because there were so many issues that work slightly different in Firefox), but IE would often crash if you used the web-app to intensively (consuming over half a gig of memory wasn't that rare either). Back button was totally ruined, browser history was useless, bookmarking was something we had to MAKE work for every page, same goes for printable views...

      Not only that, but server load increased by atleast a factor of two. The application was making so many call backs (typing letters in a field resulted in a call back so it could you show you the closest matches) that we could only support half the number of users on the same hardware. Stuff that used to be "fill in the form" [send request] "fix errors" [send request] became 30+ requests because of dynamic changing layout, content assist, etc..

      In the end, it all comes down to what you want. If you want a light weight app, that requires no install and runs on anything, then stick with simple HTML with the occasional java script.

      If you want a fancy windows application with trees, editable comboboxes, grids, drag&drop, then write a Windows application (or Java SWT / Swing) and make it communicate with the server.

      If you want both, you'll end up with neither; AJAX is not lightweight, nor will it EVER look as good and work as smoothly as a real Windows app.

      AJAX is more of kludge than anything; real progress will have to come from an extended HTML spec which will allow for more types of controls and more interactivity.

    6. Re:The problem... by infinii · · Score: 1

      No the problem is you are focussed on the technology and not the actual application. Google's Maps and Earth products will evolve into the next generation GPS systems (they already have partnered with VW to bring u such a thing). Just imagine, a nav system with satellite photos :D

    7. Re:The problem... by Anonymous Coward · · Score: 0

      I don't care who you are, or how whiz-bang your ajax is, keep your damned hands off of my desktop. When I want to look at your ajax, I will open a browser. Until then, it is my desktop, my machine, and I will run software locally. If you don't like that, then you can go take a flying leap.

  28. i18n by Yvanhoe · · Score: 1

    Security aside, is there a good ajax word processor with internationalization support ? I'd like to see a french dictionary, the two I tried were english only...

    --
    The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    1. Re:i18n by Anonymous Coward · · Score: 0

      www.writely.com is pretty good but not perfect yet. It could prove to be pretty good in the future though. I use it to work with a few others...

  29. Roar by Mike+Savior · · Score: 0, Flamebait

    I must be the only person under the age of 25 who hates the advent of all this "Web 2.0" Ajax stuff. I grew up around computers despite being young now, even as a small child, and they were more of a tinkering toy than a game machine or a tool to get on the internet in the mid-90's. I witnessed the rise and fall of the first internet wave, I played with alot of technologies when they were brand new, laughed at the stupidity of those who waited out in line to get Windows 95. Even the browser wars, but I digress, because I guess these things aren't important.

    I suppose the meaning of this comment is that the ugly webpages and first gigantic annoying ads, and Cnet's pages, all that, were just plain old HTML (mostly). Why can't we go back to that? Just content, no neat looking flash, no CSS layouts that are manipulated just so, that when you scroll the page the colors kinda change. Provided these "technologies" are useful and they themselves aren't bad (maybe except flash), but their media overrated-ness and even their usability aggrevates me. Every time I go onto one of these new Web 2.0 sites it's like making yourself at home in a Windows install. Overwhelming, too many things to click. I guess I'm just old-fashioned and bitter. Or I want my scrolling marquees back.

    --
    space is pretty cool.
    1. Re:Roar by Anonymous Coward · · Score: 0
      Just content, no neat looking flash

      That is what AJAX is all about. AJAX requires no Plugins, hell, you can't even draw images with AJAX.
      no CSS layouts

      Download Mozilla and go to View --> Use Style --> None.
      Voilà, all CSS disabled.
      It seems to me like you just didn't understand what this AJAX and Web 2.0 stuff is all about.
    2. Re:Roar by Mike+Savior · · Score: 1

      I understand what it's all about, and sure, I can turn off styles and that. I'm not discounting the -usefulness- of these things, I'm more aggrevated at the sites that overuse it or all the hype about it. I certainly don't mind a site with "web 2.0" here and there sparingly, or if it's put to especially good use, but alot of these websites are following the same trend. Gradients, dragging of everything, colors, layouts, and it's beta. Everything is beta.

      --
      space is pretty cool.
  30. just spending your money in a different place by sl4shd0rk · · Score: 1

    I can garantee, this will not be a panacea for those of us who do not want to be 'computer savvy' and have to mess around installing software, or maintaining it. It is just as easy to get digitally-screwed with online content whether it's your desktop or your pay-pal account. One good thing is that it's another option in the desktop area. We need more of those.

    --
    Join the Slashcott! Feb 10 thru Feb 17!
  31. Zonk does more Microsoft PR by Anonymous Coward · · Score: 0

    What you're meant to catch on to is the Office live connection. Subtle, but it's still Microsoft PR from the master of Microsoft PR.

  32. Agreed by coder111 · · Score: 2, Insightful

    I'm sick sick sick to see HTTP+HTML+JS used for APPLICATIONS instead of a thin client. Browsers make horrible thin clients, and HTML+HTTP+JS is a horrible way to write remote applications for thin clients. Some solution that was designed from the start for this purpose would be so much better. HTML+HTTP should be used for information transfer and PRESENTATION, not applications... To bad- while Microsoft controls desktop, this isn't going to change.

    Sun did have a shot at this with java, but they failed horribly, and this opportunity is lost forever. It's a shame, i'd like to see java dominating desktop application programming, not .NET

    Oh, and one more thing. If all (ok, most) applications become web applications, who needs a computer anymore? A zero-administration appliance with integrated browser would do just as well... This reminds me we're living in a post-Microsoft computer renaissance, client-server model of computing was used and then abandoned in favor of MS solutions years ago. It is comming back now.

    --Coder

    1. Re:Agreed by jellomizer · · Score: 1
      The best languages and designs are rarely used in the mainstream. Why HTTP why not LaTex, Why Windows why not Mac OS, or Unix. Why VB over PRP (Python/Ruby/Perl). There are a million of reasons why they may have failed, Pricing, Licensing, Legal Battles, Marketing.... But for the case of the popularity of Web Apps, which I agree are not the best way to go but have the following benefits that make it popular.
      1. Good enough platform independence. Every modern computer has a web browser, Linux, Solaris, Windows, OS X, xBSD... And even though the graphics may not render the same they are for the most part usable.
      2. Installation Ease. Every OS Normally comes with a "good" web browser by default. So when creating a new web app all you need to do is put a link on the default home page. and not go to every system and reinstall update the libraries, check to see if it works then check the other apps and make sure you didn't break anything else.
      3. Networkable if a person is located in your office or on the moon (provided they had an internet connection) there is a way they can use the application.
      4. High level of "trained" people. Most kids out of high school know HTML to some degree, and as far as some businesses go adding Ajax support and Javascript is just an extending the same language and though process (which is wrong but it is what they think) So it is easy to find "qualified" people to maintain the apps
      5. Fancy Graphics. With the web designed for presentation those apps usually look a lot better then those VT100 Apps, and even many of the VB apps.
      6. Psychological advantage for training. Everyone know hows to navigate a web page, people need training for a new application outside of the web. Even though the interface on the web app may be the same as the normal app.
      7. Controlled server. IT can manage the App in one spot and use common tools to do the job

      Web Development is flaky and has a lot of stupid workarounds and hacks to get it to work and there are a million of tools that can do every function in the web better. But shit happens and you either deal with it and make the best out of the situation or complain and fuss about it until they find another person who can do you job without the mouth.
      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:Agreed by coder111 · · Score: 1

      The best languages and designs are rarely used in the mainstream. Why HTTP why not LaTex, Why Windows why not Mac OS, or Unix. Why VB over PRP (Python/Ruby/Perl).

      I know that, and it is a very sad situation when marketing/sales trumps technology/engineering/quality in Information TECHNOLOGY market. Unfortunately this problem will only be worse in the future, as people who make the decisions are not and never will be able to competently judge the quality, price/performance, TCO, quality of IT products. So they listen to marketspeak and base their decisions on that

      1. Good enough platform independence. Every modern computer has a web browser, Linux, Solaris, Windows, OS X, xBSD... And even though the graphics may not render the same they are for the most part usable.

      Well, with web apps you might have "platform" independence, but you run into problems of browser incompatibility, especially so with AJAX apps. And these problems are not much easier. In a way, "platform" becomes the browser, not the OS. Besides, you can have good enough platform independence with java/PRP.

      2. Installation Ease. Every OS Normally comes with a "good" web browser by default. So when creating a new web app all you need to do is put a link on the default home page. and not go to every system and reinstall update the libraries, check to see if it works then check the other apps and make sure you didn't break anything else.

      Thin client apps can also have similar installation ease. Take a look at applets/java web start. They might not be the best possible solutions, but they are the way to go. And about not breaking stuff- you can install these apps sandboxed, like java applets. These don't break anything. Or like AJAX webapps- make thin client only run widgets and place the app logic on the server, just use some sensible protocol and client instead of HTTP/HTML.

      3. Networkable if a person is located in your office or on the moon (provided they had an internet connection) there is a way they can use the application.

      Well, thin client apps are networkable by definition, they run on server. And they should have higher performance and allow for bigger network latency than AJAX apps, because with good design, they would need less communication with the server. Especially AJAX suffers from poor response times and requires a fast (low latency, not high bandwidth) connection to the server. So if you'd use AJAX apps from the moon (300000 km/300000km/s = 1 second), you'd have 1 second latency due to speed of light, which means that each click on smart AJAX control would thing for 1 second before responding. This would make a WEB2.0 app completely unusable.

      4. High level of "trained" people. Most kids out of high school know HTML to some degree, and as far as some businesses go adding Ajax support and Javascript is just an extending the same language and though process (which is wrong but it is what they think) So it is easy to find "qualified" people to maintain the apps

      Well, sorry but this is bull. It takes well trained people to write web apps, especially AJAX web apps. And don't get me started on fancy Model-View-Controller/component and Object-Relational mapping frameworks, these are not easy to learn and they are pretty much required if you make a larger/more complex application

      5. Fancy Graphics.
      Agred. HTML can be designed by designers and it usually does look better.

      6. Psychological advantage for training.
      Also agreed.

      7. Controlled server.
      Same thing is possible with thin client apps.

      Web Development is flaky and has a lot of stupid workarounds and hacks to get it to work and there are a million of tools that can do every function in the web better. But shit happens and you either deal with it and make the best out of the situation or complain and

    3. Re:Agreed by Anonymous Coward · · Score: 0

      Why HTTP why not LaTex

      If you had said HTML instead of HTTP, I'd give you the benefit of the doubt and read the rest of what you wrote. But you didn't. So I didn't.

    4. Re:Agreed by jellomizer · · Score: 1

      Thin client apps can also have similar installation ease. Take a look at applets/java web start. They might not be the best possible solutions, but they are the way to go. And about not breaking stuff- you can install these apps sandboxed, like java applets. These don't break anything. Or like AJAX webapps- make thin client only run widgets and place the app logic on the server, just use some sensible protocol and client instead of HTTP/HTML.

      Well with Java Applets and with Java not comming with Windows or some of the more Anal GNU Linux Distributions by default it is up the IT staff or the User to install Java on their system, plus you get some nasty compatibility issues across different java versions. At lest with Web Apps the browsers are usualy part of the normal updates.

      Well, thin client apps are networkable by definition, they run on server. And they should have higher performance and allow for bigger network latency than AJAX apps, because with good design, they would need less communication with the server. Especially AJAX suffers from poor response times and requires a fast (low latency, not high bandwidth) connection to the server. So if you'd use AJAX apps from the moon (300000 km/300000km/s = 1 second), you'd have 1 second latency due to speed of light, which means that each click on smart AJAX control would thing for 1 second before responding. This would make a WEB2.0 app completely unusable.

      There are a lot of firewall issues you need to take into consideration. A lot of time thin clints solutions are defaultly locked by firewalls, HTTP and HTTPS are usually open. It is not about performance it is about less IT Infrastructure reorginization.

      Well, sorry but this is bull. It takes well trained people to write web apps, especially AJAX web apps. And don't get me started on fancy Model-View-Controller/component and Object-Relational mapping frameworks, these are not easy to learn and they are pretty much required if you make a larger/more complex application
      Check out this link when I say "trained" with the quotes I use the term loosly. In a management perspective they incorectly figure that anyone who knows html can do it. But in reality they probably can't do it well. But they may be able to get some snipit examples and modify the output slightly without knowing what they are doing and unable to fix it in the future. But as far as management is conserned it is the same.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    5. Re:Agreed by jellomizer · · Score: 1

      Opps my Bad. It was before coffee. After I write HTTP^H^H I always tend to write TP by reflex. then I need to correct every time I do ML when I write HTTP^H^HML I am usually fine if I put a . in it and use lower case so I reflexivly can do .html but using caps and HTTP^H^HML is tough to do without thinking about it.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    6. Re:Agreed by coder111 · · Score: 1

      Well with Java Applets and with Java not comming with Windows or some of the more Anal GNU Linux Distributions by default it is up the IT staff or the User to install Java on their system, plus you get some nasty compatibility issues across different java versions. At lest with Web Apps the browsers are usualy part of the normal updates.

      Hell, I know that. I know perfectly well that AJAX/webapps will be made and used in the Real World. I was just thinking how should things work if they were made The Right Way. I think some application client could be distributed with OS just as easy as a web browser. Too bad this won't happen as long as MS controls 90% of desktops. And I don't think that application client must necessarily be java, but java is the closest thing we have right now.

      There are a lot of firewall issues you need to take into consideration. A lot of time thin clints solutions are defaultly locked by firewalls, HTTP and HTTPS are usually open. It is not about performance it is about less IT Infrastructure reorginization.

      Dumb firewall admins are just another thing that annoys me to no end. Internet was designed with multiple applications in mind, using different ports. Now stupid administrators block everything that is not port 80 or HTTP. And then application vendors make ALL applications tunel all data over HTTP/port 80. Now you have video streaming over HTTP, applications over HTTP, instant messenging over HTTP, email over HTTP (webmail), viruses over HTTP, malware over HTTP, exploits over HTTP, EVERYTHING over HTTP. And this makes blocking other ports/protocols completely useless from security standpoint. Too bad it is not possible to change this in Real World. And one more thing i noticed- bigger corporations have more brain damaged firewall configurations, and it is less possible to change anything there...

      Oh, and I agree about "trained" people. It's a good thing I can interview people myself before they get hired in this company.

      P.S. I don't like slashdot <blockquote> tags anymore :)

      --Coder

  33. Crud 2.0 by scdeimos · · Score: 1

    As soon as someone (except me, right here, right now) mentions "Web 2.0" you can pretty well write-off the rest of the conversation as marketing crud. That page mentioned "Web 2.0" twenty one times.

  34. Your local cache 10-20 years from now by wombatmobile · · Score: 1

    I need to have data cached locally - but if I'm going to have a local solution set up anyways I might as well go with that and avoid the hassle.

    In less than 20 years the standard PC hard drive will hold 100 terabytes - as much as the whole internet today.

    The drive will cost about $100 in today's money. A different type of client will be possible and routine by then.

  35. If these are the "future".. by Anonymous Coward · · Score: 0
    We are totaly screwed....

    By the way... 1999 called, they want their ideas back!

  36. The JavaScript operating system? by cardpuncher · · Score: 1

    Perhaps not.

    It could be very useful to have an environment (hardware, or a virtual environment on a PC) which replicated an (encrypted) private data store with a central server and did the same (in the other direction) for a public application repository. Documents available everywhere, continue to work if network down, no software installation (it just arrives as required). However, it would require a *standard* environment which delivered a decent, interactive user experience for all application types. So not AJAX. Or Java (with its current set of UIs).

    Arguably, of course, this is where Microsoft is heading with .NET ... though you'll have to watch your credit card as that software lands in your local cache.

  37. Anyone remember Desktop.com? by _flan · · Score: 3, Interesting

    I think it's interesting to note that AJAX and online desktops were presaged by Desktop.com in 1999-2000. I worked there, so I can say with authority that we did have a full web-based operating system going in Netscape 4 and IE 4. The stuff that's done now isn't as complex as the stuff we had, in general, though recently (GTalk through GMail, for example) it's started coming close. (I admit I haven't been following some of the other sites mentioned, so maybe some other folks are further along.)

    We ran into a couple of killer problems:

    * Browser instability -- we had no control over this. Netscape lasted on average 10-15 minutes and ate tons of memory. IE lasted longer, but also consumed memory until it crashed.

    * Slow connections -- we had a good 500K download at first connection (or empty cache), which was *slow* over dailup, which was the norm.

    * Apps -- nobody is going to come if the apps aren't there. In the day, even making a notepad clone was difficult because native HTML controls were always on top.

    The first two of these problems have been/are being slowly overcome. The third one is still a problem.

    But the problem of privacy has never really been foremost in the minds of users. Maybe it will be, but with everyone using web mail, I'm kinda doubtful.

    Ian

  38. VNC in AJAX please by Gunstick · · Score: 1

    I don't need a web desktop. I just need a VNC client written in AJAX which can display my home PC anywhere on any browser behind ans SSL proxy/firewall.
    Now THAT would be useful.

    Try to VNC home through a proxy where you don't have access to any way of creating a tunnel (e.g. a cybercafe)

    Georges

    --
    Atari rules... ermm... ruled.
    1. Re:VNC in AJAX please by Anonymous Coward · · Score: 0

      VNC can already use Java, all you need is the Java VM and you can load your desktop through a webpage.

    2. Re:VNC in AJAX please by Gunstick · · Score: 1

      no you can't load NVC through java behind a firewall with a web proxy. The VNC port are not allowed through the firewall.

      Have you actually tried this?

      --
      Atari rules... ermm... ruled.
  39. real time data is the key. by recharged95 · · Score: 1
    Until users realize they can multitask on a single webpage (i.e. webapp) and that developers can find real needs for real-time data [streams], AJAX/Web 2.0 will be another useless cool thing--to be surpassed by something simplier, likely UI improvements (and XHTML/CSS has taken care of that angle).

    The browsing paradigm needs to change for this technology to be of any use, we are too stuck on the static webpage. Why? cause 1. users are used to navigating pages and 2. developers are still designing for 'multiple pages' in a website/portal. I think we need to switch from bottom up design to top down (workflow logic) with more focus on the controller layer.

    BTW, as we get more mobile, our attention spans will actually improve and be more focused, since we'll have information we want to review on demand; more time to focus on that information. As for security, the internet as a whole needs to improve it's trust system, not authenication & authorization. Or users just keep their private data private: that is, offline.

    1. Re:real time data is the key. by zenwarrior · · Score: 2, Insightful

      BTW, as we get more mobile, our attention spans will actually improve and be more focused, since we'll have information we want to review on demand; more time to focus on that information.

      I am not certain about that. In fact, all current research points to "information overload" now occurring. There are those who even feel the rise of ADHD is related to more mobility and larger numbers of diversions. Attention spans have gotten much shorter, and we hear that in sound bites on TV and see it in the gloss-over articles of USA TODAY.

      --
      /.'s Psychic-in-Residence: Psychic to the Geeks
  40. Mod -1, Troll by Anonymous Coward · · Score: 0
    be perfectly happy using applets and java web start.

    Bleah. That would truly be the 7th circle of hell......

  41. Operating System?? No... Online Apps, yes. by borgheron · · Score: 1

    While there might be some concerns about privacy, or even confidentiality, given that some people might feel as though they're risking the confidential nature of thier information by putting it on an online word processor, I think that most of these fears will fade. Like email, people will eventually become comfortable with this new way of doing things.

    I certainly think the idea of the online word processors is bound to catch on to some degree.

    Later, GJC

    --
    Gregory Casamento
    ## Chief Maintainer for GNUstep
  42. Missing the point... by qazwart · · Score: 2, Interesting

    We see a few "Web 2.0" apps, and we make our comments based upon those. However, that's like looking at Alexander Graham Bell's demonstration of his first telephone and comment that it would never get anywhere because of its technical limitations.

    * What if instead of your Web 2.0 application using a remote server, it used your own desktop machine as a server. Would you still need your Internet connection?

    * What if businesses ran their own Ajax applications for wordprocessing, spreadsheets, and whatever else they do instead of needing every application loaded on each and every PC?

    * What if you could quickly switch from one HTTP server (running from say Google.com) to another HTTP server (running on your desktop). What if the application could store your data remotely and locally? You could use a remote server when you have good service and switch to your local server when you don't have Internet connectivity.

    * What if you decide not to lug around your desktop machine, but rather work on a PC laptop? Maybe not even a laptop, but a Linux based PDA?

    Do you see where this could be heading?

    With "Web 2.0" applications, you could be running an application from your "desktop server", from your company's server, or even from a public server. It doesn't matter! Your application will still work.

    With "Web 2.0", your data could be stored locally, remotely, or even both. It is even possible for a remote server to "update" your local instance of your application when you decide to work locally. When you switch to your local desktop server, you still have the same up to date application you had on the Web.

    With "Web 2.0", you're not tied down to a particular piece of hardware or even a single platform. You could be using your Windows XP desktop at work, switch to your laptop on the train ride home, switch to your Mac at home, and when you go off on your well deserved ski vacation, switch to your handheld Linux powered PDA. Each and every device would have access to all the applications and data you need. There's no difference between one piece of hardware vs. another.

    Corporations are no longer have to preload their desktop machines with the applications their workers need. They're not tied down to a particular platform. No more waiting for that MSCE to show up in order to install that application you need. Heck, if a meteor came flying through the window and smashed your desktop PC, you could get on another one and not miss a lick of work. You'll still have the same desktop and the same applications. The last time my PC died at work, it took me two weeks to get back up and running.

    When an application is updated, everyone at your company has the latest copy. You don't have to install it on tens of thousands PCs. Desktop support is much simpler. You don't have to worry whether someone has the same version of your appliction (or even if they have your application).

    That's why everyone is so excited by "Web 2.0".

    Unfortunately, I don't believe AJAX is going to be the way to go. (Of course, what do I know? I thought Windows 95 would be a flop.) Ajax is too iffy. JavaScript is not the "universal" language we all think it is. Every browser on every hardware platform implements it a bit differently. Its even worse than Sun's "write once, run everywhere" JVM platform. I'm playing around with Ruby on Rails to see if that feels any better.

    1. Re:Missing the point... by misleb · · Score: 1

      With "Web 2.0" applications, you could be running an application from your "desktop server", from your company's server, or even from a public server. It doesn't matter! Your application will still work.

      Well, any company with decent desktop management already runs the PC desktop and applicaitons off of a server and none would be dumb enough to depend on the internet for application functionality.

      With "Web 2.0", your data could be stored locally, remotely, or even both. It is even possible for a remote server to "update" your local instance of your application when you decide to work locally. When you switch to your local desktop server, you still have the same up to date application you had on the Web.

      Again, done by many larger organizations.

      With "Web 2.0", you're not tied down to a particular piece of hardware or even a single platform. You could be using your Windows XP desktop at work, switch to your laptop on the train ride home, switch to your Mac at home, and when you go off on your well deserved ski vacation, switch to your handheld Linux powered PDA. Each and every device would have access to all the applications and data you need. There's no difference between one piece of hardware vs. another.

      Why are you accessing your "data" on vacation, anyway?

      You really have high hopes for "Web 2.0." As far as I can tell, you're talking about Web 7.0. 2.0 is nowhere near doing anything like you talk about and most of it is already accomplished by real desktop management applications.

      Corporations are no longer have to preload their desktop machines with the applications their workers need.

      It's called Norton Ghost. Keep a standard machine image and you have a working desktop in 5 minutes.

      They're not tied down to a particular platform.

      What company wants to manage more than one platform?

      No more waiting for that MSCE to show up in order to install that application you need.

      A worker's environment is usually more stable than this. New applicaitons don't just pop up out of nowhere.

      Heck, if a meteor came flying through the window and smashed your desktop PC, you could get on another one and not miss a lick of work. You'll still have the same desktop and the same applications.

      Again, Ghost plus server based desktop/home dir.

      The last time my PC died at work, it took me two weeks to get back up and running.

      And you trust incompetent fools like your network admins to implement some Web 7.0 solution that doesn't even exist yet? They apparently haven't even grasped the most basic existing desktop managment techniques/tools. Or do you just plan on outsourcing all of your IT needs to Google?

      When an application is updated, everyone at your company has the latest copy. You don't have to install it on tens of thousands PCs. Desktop support is much simpler. You don't have to worry whether someone has the same version of your appliction (or even if they have your application).

      I agree that this is on advantage of web based applications. But it is much more appropriate for internally developed applications than for general purpose off the shelf applications though. And even then, you have to use the right tool for the job. Some application just don't map well to a web brower... no matter how frieking awesome web 2.0 might be. In other words, the idea of using "web 2.0" for things like word processing is just stupid. Yes, stupid. Not questionable. Not debatable. Just stupid.

      That's why everyone is so excited by "Web 2.0".

      I though it was because everyone is a slave to hype.

      Unfortunately, I don't believe AJAX is going to be the way to go. (Of course, what do I know? I thought Windows 95 would be a flop.) Ajax is too iffy. JavaScript is not the "universal" language we all think it is. Every browser on every hardware platform implements it a bit differently. Its even worse than Sun's "write once, run everywhere" JVM pl

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  43. Re:Your local cache 10-20 years from now by Anonymous Coward · · Score: 0

    Internet != the web

    100 terabytes is only 17000 DVD ISOs. Piratebay alone has several thousand, add in the other P2P services and different warez channels like FTP and it's obvious that file trading alone has more data. Add in the huge amount of legitimate data - the vast scientific datasets (many of which are web accessible, check out e.g HEASARC or simbad), thousands of "web radio" and video streams, thousands of game demos (which are often hundreds of megabytes), there are probably a couple of terabytes of linux install CDs and DVDs alone (1000 distros * 3 versions * 700 meg per version), saying nothing about all the other free software.

    p.s. my PC has 0.6 terabytes. Do I have a copy of the web from 1992 on there? Nope.

  44. Huh! by thomville · · Score: 1

    I don't think we're the core audience for this product (or the article). The major sites I search for info all live on a toolbar - and a folder of shortcuts on a jump drive takes care of portability. For Joe User, this isn't as easy, since it isn't always intuitive. I think education on how to work with existing tools would be at least as useful as trotting out another portal and calling it the newest version of sliced bread.

  45. Open-Source AJAX desktops? by Andy+Dodd · · Score: 1

    The article mentions quite a few corporate-hosted AJAX desktops.

    Are there any similar open-source entries in the market for those of us who might want a "usable from anywhere" solution but which is hosted on a machine we control?

    I currently use Horde IMP for web-based email, and I'm thinking of possibly installing FCKEditor on my home server box, but I'm wondering if there's an "all in one" solution out there.

    --
    retrorocket.o not found, launch anyway?
  46. Glad they decided to catch up .. by Zate · · Score: 0

    anyone not seeing this trend 12 months ago is blind. The desktop OS will be a thing of the past inside 3 years. All you will need is a browser, doesnt matter which one, and an account with Google. All the major things people do with their computers will be online.

    --
    IT is Dead. The industry is Shot Join Others Who Feel Your Pain http://www.internalstrife.com/
    1. Re:Glad they decided to catch up .. by Anonymous Coward · · Score: 0

      The desktop OS will be a thing of the past inside 3 years.

      Mwhahahahahahaha.... thanks for the laugh. It really englightened my day.

  47. The "server" problem won't exist much longer... by nonlnear · · Score: 2, Interesting
    The term "server" will very soon be completely antiquated. As the line blurs between a data request and actual data, (to Google, a data request is data) the legal distinction between uploading and downloading will disappear.

    The legal line will get blurred very soon. (The content companies will make sure of this.) That will make any server clauses completely void. The only meaningful contract language left will be bandwidth limits and volume of data traffic per billing cycle. And if you think about it, that's all the ISPs really care about anyways.

    --
    argumentum ad fallacium: Fallacy of defining a fallacy which allows one to dismiss the argument in question.
    1. Re:The "server" problem won't exist much longer... by Al+Dimond · · Score: 1

      You say "The only meaningful contract language left will be bandwidth limits and volume of data traffic per billing cycle. And if you think about it, that's all the ISPs really care about anyways."?

      I don't buy it.

      I live in an apartment with a central Internet connction. We're all behind NAT. There is a server clause. I've asked if I could have a couple ports forwarded to my machine for SSH/SFTP and been rejected. It's an absolutely piddling amount of bandwidth (I'd use it perhaps a couple times a week to transfer a few LaTeX or C files that I had forgotten to transfer before going to classes). A few things dawned on me:

      If I really want to run a server, and can't under the current agreement, I have to "upgrade" to a "higher" level of service. This "higher" level of service would be more expensive and I would use only a tiny fraction of the bandwidth provided. These companies also tell you that you "can only have one computer connected at a time" (so you don't try to install a router). Of course, it's only physically possible to have one computer connected at a time; in my case, that computer is called a "router". Other computers connect to the router and make requests, which the router fulfills, sometimes my making further requests over the ISP's network. They can't fool me, but they can fool other people, like a poor schmo I talked to that pays for two Internet lines a month so he can run an IP-enabled security camera.

      Bandwidth, latency and supply of IP addresses are the costs for an ISP, and they are also the goods that they deliver to us. People like us realize this and will use them to whatever potential we're technically allowed. But you can bet they'll try to profit on selling "upgraded", "business class" service to anyone they can, or by pushing users wanting to post their own content onto limited ad-supported "portal" servers rather than taking control of their own. And of course, they have every stake in presenting the Internet to future generations in this light of a client-only service for most of its members.

    2. Re:The "server" problem won't exist much longer... by nonlnear · · Score: 1
      I didn't say we are there right now. There are definitely some ISPs that are worse than others. I didn't know there were still some that have one computer policies - that's so 90's.

      Also, I should have said that traffic volume is all that a competitive (in the economic sense) ISP would care about. By lording the server clause over you, they are attempting to price discriminate - i.e. be non-competitive. It will take some legal wrangling to invalidate the server clauses, but I believe it will happen in the next 5-10 years. As your ISP so paleolithically illustrates, we're not there yet.

      On a more general note, situations like this illustrate why I'm wary of judges like Alito who put too much faith in the power of contract law to protect the common good. The problem (especially with utility-type goods liek ISPs and telcos) is the asymmetric market in which the contract is enforced. But that's a bigger discussion...

      --
      argumentum ad fallacium: Fallacy of defining a fallacy which allows one to dismiss the argument in question.
  48. Comcast, Knology... by everphilski · · Score: 1

    I have with Comcast and Knology. It might not be explicity granted but as long as you aren't dominating the bandwith it hasn't been explicitly denied. You can request static IP addresses with either comapny for a marginal fee - I did not, and with Comcast over a 2 year period my IP only changed 4 times! I ran a low-traffic site with a dynamic IP service, no problem.

    I used my home computer to host a few personal web sites, pictures of my son (we live far away from the grandparents and they want pictures) and access to documents from work and grad school (via either FTP or remote desktop)

  49. Dead wrong by everphilski · · Score: 1

    not to mention that imho getting something like Apache to work on Windows is more efford then installing Suse with a webserver for example.

    I've used IIS and Apache on Windows. While both have their perks, Apache is dead easy to install on windows. It has a graphical installer and installs as a service in less than 10 clicks. Way easier than installing Suse.

    (Not to mention that XP Pro comes with IIS...)

    1. Re:Dead wrong by SillyNickName4me · · Score: 1

      I've used IIS and Apache on Windows. While both have their perks, Apache is dead easy to install on windows. It has a graphical installer and installs as a service in less than 10 clicks. Way easier than installing Suse.

      Untill you need something like PHP perl, ssl or such. Yes, all of them can work, but I did not exactly find it easy to get to work. Maybe things got a bit better since 1.3.25...

      (Not to mention that XP Pro comes with IIS...)

      Yes, and that is not exactly what the typical home user has, hence for the typical home/hobby user, this takes buying new software (even if it doesn't have to be Windows 2003 server).

      At any rate, I am sure that many can quite deal with Apache on Windows, but I honestly doubt that was what I was pointing at in my original post.. maybe it was a lot more about how knowledge makes the difference, not the platform you use, and to point out that expensive solutions are not gonna appeal hobbyists if there are at least as good and much cheaper alternatives. Read all the Windows bashing in it you want..

    2. Re:Dead wrong by everphilski · · Score: 1

      I had php working in 20 minutes. (Extract the zip files, copy the DLL's to the c:\windows\system32, update apache configuration file) SSH was easy too. I didn't need perl, so I can't coment.

      Most home users have XP pro, because most vendors ship with XP pro. Believe it or not. Home is such a piece of crap, unless the users upgrade themselves they have XP pro. And if they upgrade themselves they are savvy enough to install apache.

    3. Re:Dead wrong by SillyNickName4me · · Score: 1

      I had php working in 20 minutes. (Extract the zip files, copy the DLL's to the c:\windows\system32, update apache configuration file) SSH was easy too. I didn't need perl, so I can't coment.

      20 minutes is also how long it takes me to get FreeBSD + apache + ssl + php + perl + decent logging + webmail app + content management installed and configured, but ok. Is there a php module for apache on Windows now? because one of my main issue there is actually getting PHP apps to live with cgi based php.

      Most home users have XP pro

      Maybe most people around you do, but overhere you have a hard time as a consumer getting anything other then XP home, and you pay quite a bit for it, regardless of going to a shop or ordering online. XP home is what almost everyone has except for those who know about the difference.

      , because most vendors ship with XP pro.

      In the consumer market? not overhere.

      Believe it or not. Home is such a piece of crap

      There are better systems around, even from the same vendor.

      , unless the users upgrade themselves they have XP pro.

      Uh, shouldn't that read 'unless the users upgrade themselves they have XP home' ?

      And if they upgrade themselves they are savvy enough to install apache.

      Oh, definitely, but if you read back in this thread you may see I was replying to someone saying that IIS on 2003 server and XP (pro) was a decent solution for the idea of home users running their own webservers for their own data. I think it is not. Apache on XP? Oh, can work (eventho I have had my troubles with it, others are happy with it it seems) and could be a good option for such home users. Getting XP pro to begin with would also be an option and would give the choice of running IIS also.

      Claiming that spending money on software is a good idea when there are at least as good alternatives that are free? Sounds silly to me.

      For the rest, I agree with the fact that it is about knowing what you are doing, not about the platform you are using so much.

    4. Re:Dead wrong by Anonymous Coward · · Score: 0

      Most users do NOT have XP Pro, and most vendors ship XP home. Those are facts. I am a Sales Rep for a leading vendor. hp, Sony, etc. hardly ship ANY boxes with XP Pro.
      What the hell are you talking about?

      And, yes, many experienced users still use Windows, but they avoid the typical Windows problems as was actually implied in the original post.

      I'd like to point out I sell Windows boxes, run Fedora Core, and the friend I go to with questions most runs Windows! I deride him constantly for how stupid most Windows users are (mashing keys to "make it work", disabling their firewall to "get online" because they don't know what they're doing and won't put in the effort to learn). He doesn't argue, he laughs. and I don't stop asking his opinion because he's also a Windows user.

      You people are being overly defensive, probably because you're embarrased by 90% of the people who use the same OS as you do. Don't be. Or find a new OS.

      Steve,
      Boston, MA

    5. Re:Dead wrong by Anonymous Coward · · Score: 0

      http://www.wampserver.com/

      apache with php and mysql
      there are also modules to be able to switch from php4 to 5

    6. Re:Dead wrong by everphilski · · Score: 1

      I've been running Apache+PHP+SSL on XP Pro for over a year now without any problems, serving up mostly pictures using dynamic scripts. Granted I'm a bit more compotent than most (I've worked with PHP/Apache off and on for 7 years now... not my day job).

      No there isn't a module for PHP, it is a standalone application. Installation is fairly straightforward. Follow *both* PHP's and Apache's instructions. You need to change httpd.conf to enable PHP (just like linux/unix/bsd)

      Claiming that spending money on software is a good idea when there are at least as good alternatives that are free? Sounds silly to me.

      XP Pro is so much better than home edition, it is worth the $50-$75 upgrade price. Many college campuses won't allow you to run it on their networks due to all of the security holes. Home is a piece of crap. Pro, SP2 is a good piece of software. I'd recommend it without reservation regardless of IIS.

    7. Re:Dead wrong by SillyNickName4me · · Score: 1

      No there isn't a module for PHP, it is a standalone application. Installation is fairly straightforward. Follow *both* PHP's and Apache's instructions. You need to change httpd.conf to enable PHP (just like linux/unix/bsd)

      Yeah, I got it to work (just didn't find it as easy as on the mentioned unix variations), but I was wondering if there was an Apache module by now (doing some stuff that doesn't work very well without the module)

      XP Pro is so much better than home edition, it is worth the $50-$75 upgrade price. Many college campuses won't allow you to run it on their networks due to all of the security holes. Home is a piece of crap. Pro, SP2 is a good piece of software. I'd recommend it without reservation regardless of IIS.

      Definitely, and I do the same for those who want or need Windows.

      But it is still not what most home users are running. College campus networks are not very representative because first of all they are usually administrated by someone who has at least a bit of a clue and second the users there are a bit more likely to have some clue then the average person.

      In the context of the average home user running his/her own webserver at home for his/her own data, I don't see how arguing that IIS comes with XP pro and 2k3 server and would work fine is going to be of much help. I would say that there is no option other then getting a clue about running a webserver securely and then picking whatever platform you are comfortable with and is affordable to you. On the way there, you will find yourself getting rid of most of the problems associated with Windows as well most likely (even when staying on that platform, which was one of the points of my original post, responding to the 'windows bashing' comment in its parent) since most of them are also a consequence of not having a clue.

      The same applies to running Apache on any version of Windows. The same applies to running a webserver on any other platform.

  50. XP Pro ships with IIS. by everphilski · · Score: 1

    http://www.webwizguide.com/asp/tutorials/installin g_iis_winXP_pro.asp

    XP Pro ships with IIS. Unless they are running XP home, they probably have IIS on their CD. Just need to install and patch...

    1. Re:XP Pro ships with IIS. by SillyNickName4me · · Score: 1

      XP Pro ships with IIS. Unless they are running XP home

      And guess what the large majority of home users are running..

    2. Re:XP Pro ships with IIS. by everphilski · · Score: 1

      Very few vendors actually ship home edition... and very few of the people ACTUALLY SAVVY ENOUGH TO RUN A WEB SERVER would purchase home, given the option.

      And there are workaround such as:http://www.iis-resources.com/modules/AMS/articl e.php?storyid=48 to get IIS working on Home.

    3. Re:XP Pro ships with IIS. by SillyNickName4me · · Score: 1

      Very few vendors actually ship home edition... and very few of the people ACTUALLY SAVVY ENOUGH TO RUN A WEB SERVER would purchase home, given the option.

      Well, where I live, and when looking online for what is being offered in other countries, I have a hard time finding any vendor that doesn't preload home edition by default for PCs for the consumer market. I did find some vendors not shipping pro with PCs for the consumer market however.

      This picture is different when looking at the business market, but we were talking about home users running web servers for their own data, not about business users.

      You are right of course that most people who actually know how to run a webserver securely will use something different from home edition, and what is more, for those people it shouldn't matter too much what the underlying platform is as long as it fits the requirements (and that Windows NT and 2000 already do well enough)

      And there are workaround such as:http://www.iis-resources.com/modules/AMS/articl e.php?storyid=48 to get IIS working on Home.

      Cool that it can run... but... where exactly would IIS come from in that case? I mean legally...

      You see, there are a bunch of arguments to be made, but it is pointless if we aren't even talking about the same situation..

      So, lets once more define the situation:

      Typical HOME user wants to run web server for his personal data.

      Choices this person has:
      1. Run a free web server on his current platform (which in the large majority of cases will be XP home edition)
      2. Upgrade to a version of his platform that comes with a webserver
      3. Change to a different platform that comes with a webserver

      Now, option 1 and 3 are free (money wise), option 2 is not.

      The post I replied to was advocating option 2, and in its more expensive variation also (Windows 2003 server) tho it did mention the cheaper alternative (XP pro). Tel me, how is that a usefull advice to a home user wanting this?

      Of course this all doesn't change that the one thing you need in all cases for doing this is knowledge. Choice of platform changes what and how much knowledge you need maybe, but not the fact that you will need it. People who do not have the knowledge and do not want to invest time and efford into getting it, should not want to run their own webserver either, that much I can agree with.

    4. Re:XP Pro ships with IIS. by everphilski · · Score: 1

      Cool that it can run... but... where exactly would IIS come from in that case? I mean legally...
      http://www.microsoft.com/ntserver/nts/downloads/re commended/NT4OptPk/default.asp (that's a link to download 4. You can upgrade to 5. 6+ require server to run on)

      Choices this person has:
      1. Run a free web server on his current platform (which in the large majority of cases will be XP home edition)
      2. Upgrade to a version of his platform that comes with a webserver
      3. Change to a different platform that comes with a webserver

      (1) All of the following are free and usable. I recommend Apache:
      Apache
      OmniHTTPd
      IIS

      (2) ... Sure. Windows XP Professional. You should be using it anyways, home sucks.

      (3) ... yeah, if you are a linux zealot. Properly configured windows box is secure. I see no reason to switch just to serve up web pages as a hobby, and for the target audience (you were talking about people running WINDOWS XP HOME after all) that is a pretty big step.

    5. Re:XP Pro ships with IIS. by SillyNickName4me · · Score: 1

      (2) ... Sure. Windows XP Professional. You should be using it anyways, home sucks.

      Sure, but see your own argument below..

      (3) ... yeah, if you are a linux zealot. Properly configured windows box is secure. I see no reason to switch just to serve up web pages as a hobby, and for the target audience (you were talking about people running WINDOWS XP HOME after all) that is a pretty big step.

      Yes, it is a big step, and I am not suggesting people should make that step by definition, in most cases the platform one uses is pretty much irrelevant as long as it is good enough (and as I wrote in another post, NT and 2K already quakify for that often). The thing is that before you consider running your own publicly accessable webserver you should have a clue about what you are doing. That is for most a much bigger step then changing platforms.

      When looking at a technical solution for running a personal webserver for ones own data (and web applications) it looks pretty much like something you'd want to solve with some appliance, preferably a nice low-power embedded system with some huge amount of disk storage, acting as webserver and for the local network as smb server. Incidentely, such systems exist and usually turn out to run some variation on Unix, usually Linux. Yeah, those definitely still require that you have a clue about what you are doing, and at times leave something to be desired with regards to their vendors and updates, so it doesn't solve the security side of it, nothing beats having a clue..

      It does sound like a better idea then always leaving the home PC turned on however, and likely a bit cheaper as well. Also, it removes the need for installation and a secure default configuration for as far as the user is concerned, they can concentrate on their data and keeping that secure and available at the same time.

    6. Re:XP Pro ships with IIS. by jp10558 · · Score: 1

      Where exactly do you live? In the US, all major vendors sold in retail (Best Buy, Circuit City, etc) ship XP Home on all but their most expensive computers/laptops.

      --
      Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
  51. Ajax App by bri9999 · · Score: 1

    I don't know I'm starting to see some useful applications come from Ajax. Admittedly we only need so many home portals and word processors from ajax but places like Green Village Docs http://www.greenvillagedocs.com/ are taking on Zip Forms and even to a certain degree Adoboe with online document fill out using ajax.

  52. Owning your own data by Gyorg_Lavode · · Score: 1
    I think ajax apps are a good idea, but not hosted by someone else. I see 2 trends in the future, 1 of which is already starting to take place. The first trend is paying someone to administer your computer for you. AOL already does this to a large extent, (something I'll pat myself on the back for predicting they would do though no-one here will remember me saying it =P). They patch their client's machines. They install anti-virus and anti-spyware software. They provide a firewall and they scan email. At some point I assume AOL will offer a "complete protection" package where you are no longer the administrator, only a user.

    The next thing applies to this more directly. Companies like Microsoft are going to move the data center into the home. Probably Microsoft, will offer a software package for windows, (or maybe just a version of Windows), which is a personal server, (much like many linux distributions). When you set it up you will get to choose what servers you want. There will be the traditional servers: email, webpage, share your files anywhere on the internet (ftp). Then there will be the newer types of servers: "Office on-the-go". (An ajax version of office apps), and "your desktop anywhere", (an ajax desktop server). The setup will be MS easy and the semi-computer-literate families will be able to get it going no problem. MS will probably also offer an administration service where they will remote administer your server for you so you don't ever have to worry about it, (see first paragraph), bringing this home server ability to all people. (And earning MS a ton of service-related money in the process.)

    --
    I do security
  53. Better Web Desktop than Ajax by PineHall · · Score: 1

    Any ISP could use NX (from NoMachine [nomachine.com]) to create a "Desktop on the Internet". NX makes X Windows and/or MS Windows fast, so that an ISP could set up servers and serve a remote desktop over the Internet. NX uses ssh so it is secure and the ISP could provide encrypted disk space. All the needed applications would be on the ISP server. The PC would become a thin client. The ISP could provide a way to rsync all the changes back to your PC if a storage medium was available (hard disk, usb flash drive, ...). The only disadvantage of NX is that it does require a client program.

  54. What aspects of the desktop are "aging badly"...? by Richard+Steiner · · Score: 1

    I can run the software I want at home on any given machine, or I can use tools like X or VNC (or ssh) to run/use applications on remote machines. Filesharing means that I can use files regardless of the machine on which they reside.

    I think this is convenient, and it makes my machings extremely useful for me. What's wrong with the existing paradigm?

    --
    Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
    The Theorem Theorem: If If, Then Then.
  55. Re:Operating System?? No... Online Apps, yes. by plague3106 · · Score: 1

    No, apps won't catch on either.

    First, your browser limits you to horrid controls (from a developers standpoint). Check boxes, radio buttons, buttons, text entry anda drop down.. whoopie. Have you found a good tree view that works on almost all browsers? I haven't..

    Second, the responsiveness will NEVER equal that of a desktop. There will always be a noticable delay.

  56. MOD PARENT UP by Anonymous Coward · · Score: 0

    I completely agree. In answering the question of whether AJAX is the wave of the future, its not good enough to only take into account the applications of the present.

  57. confused goals, lousy standards by penguin-collective · · Score: 2, Interesting

    I think a well-designed system for running apps remotely would be great, but all attempts so far have had serious problems. AJAX's problems are that its component technologies were designed for completely different purposes (web document display), that it lacks many UI components, that it lacks a programming model on the display side that supports good GUI development, and that it lacks desktop integration (drag-and-drop, menu bars, window closing, etc.).

    The previous attempts at this haven't been much better; X11 got everything right on the application side but screwed up on security and compression, Display Postscript and NeWS had serious technical problems and never really pushed remote usage, etc.

    The closest to a good web applications delivery language might be XUL or Microsoft's proprietary clone. Or, maybe, just maybe, people will finally clean up the HTML/Javascript mess and fill in the missing bits and pieces; the standards for that are on the drawing board, but whether they get adopted is anybody's guess. Until they are, AJAX applications are going to remain painful to develop and limited in functionality.

  58. AJAX needs XForms by foniksonik · · Score: 1

    This will be a usable technology when the XForms spec has been integrated into browsers.... until then it's just a hack.

    Really when XForms is available all you need is XMLRPC... not Ajax at all. ie: XForms + XMLRPC == AJAX killer.

    So bring on XForms already....

    --
    A fool throws a stone into a well and a thousand sages can not remove it.
  59. desktop wallpaper as ajax-eanbled-web-desktop by Anonymous Coward · · Score: 0

    I think changing the wallpaper of the desktop to an ajax-type-web-desktop will be useful. That way no "browser window" will be required.

  60. still an OS by GmAz · · Score: 1
    You still need an OS to get to these webpages. Sure, you could make a machine to boot straight to the web, but guess what, its still an OS accessing a webpage.

    I personally would hate this too. What if your internet is down. Does that mean you can't use your comptuer at all?

    --
    Click Click Bloody Click PANCAKES!
  61. Home servers by willCode4Beer.com · · Score: 1

    A few years ago, I had a Comcast sales guy show up at my door trying to convince me to switch my (Qwest) DSL to their their cable.
    I told him that I ran both mail and web servers from home and that I would only go with the service if this was permitted. At the time there were stories about port blockage, etc..
    He made a phone call, I talked to a tech to say what I was doing, and it all went ok with no probs. I ran my home server with them for about 2-3 years without incident until I moved.
    I don't know what the current state of things are, that was my experience with a home server.

    --
    ----- If communism is a system where the government owns business, what do you call a system where business owns govern
  62. Welcome to 1996 by DigitlDud · · Score: 1

    I'm pretty sure these things have been around for about 10 years, they were called WEB PORTALS. Except now they AJAXulated all over it and you can drag stuff around with the mouse!

  63. Web desktop by ShecoDu · · Score: 1

    I was unimpressed by those sites, I find http://computadora.de/ interesting, even though it is written in flash and not javascript, it is more of a remote desktop, it has a some useful applications, all of them use the website storage.

    It's in spanish, I don't know if there are similar sites in english.

  64. Only when desktop & intersite integration tigh by lux55 · · Score: 1

    The desktop still outperforms web-based applications in many ways, including providing a seamless user experience (after all, it _is_ the user interface, not confined to a box within the user interface). The desktop is still the most appropriate execution environment for large binary applications (photoshop, for example). A web-based alternative like http://pxn8.com/ is definitely very neat, but it's limited compared to photoshop (for professional use at least).

    What's cool about web-apps is that they're beginning to integrate with one another. That's one of the most exciting things about the "web 2.0" generation of applications, and offers potentially more convenience increases than all the ajax realtime-esqueness that everyone's talking about.

    But the real end I think we're all moving towards is not just limited integration between sites, but also integration with the desktop. Look at Dashboard on Mac OS X and the fact that Vista is going to support RSS like crazy. Other standards like WebDAV and developer APIs on sites extend the possibilities in this way too. Either way, I think this guarantees that the "web 3.0" generation of apps will be just as different from "web 2.0" as the current gen. are from what some would call 1.0 (that's way too many version numbers, ugh!).

    PS. Check out my own "web 2.0" app in my sig -- it's a free file storage service with lots of cool features!

  65. Keep it on the desktop by Arandir · · Score: 1

    Bandwidth is cheap, but so is processing power. My client systems are now more powerful than many servers. For some *types* of applications, client/server still makes sense. But to suggest that the client should only be used for rendering remote apps is stupid.

    I want my data to be local, as well as the software that manipulates it.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  66. how is this different from google/ig? by bill_kress · · Score: 1

    Google/ig has been up for quite a while--I feel like it's been my home page forever. Each of the pages I visited from the article seem like simple copies--nothing new.

    Why aren't they implementing word, excel, photoshop, All my IM clients, a couple solitare & group card games and a music+video player all with remote storage or the ability to fetch data from another computer when you access it remotely.

    THEN you have a "desktop". Until then you just have the same portal you've had since YAHOO went public, but with the ability to drag stuff around.

  67. Maybe people just need to view a new idea by kermada · · Score: 0

    Could be that most people do not need Word. What they really need is an RTF or HTML editor to be able to print a nice looking document. If wordpad had a spell checker, who would by word?

  68. Google more robust than Home LAN by aricusmaximus · · Score: 1

    Google stopped working on your home computer/LAN/ISP, but

    Google still worked

    - at your local coffee shop (Seattle bias here)
    - at your local library
    - at your friend's house
    - at the local printshop
    - even on your cell phone

    In other words, your Home LAN/Computer is hardly the single point of access to Google or any other web-based application.

  69. "Web 2.0" = mainframe, nc, x11 all over again by scosol · · Score: 1

    Thin clients remotely accessing large centralized applications?

    This sounds familiar- and until connectivity is literally constant and ubiquitous, it will fail again, and again, and again, and again.
    The current model of "my access terminal has it's own local storage, and runs apps locally" evolved for a reason.
    People want access to their data.
    For banking information, it's not my data- it's someone else's data that's relevant to me, so the client->server model works fine here.
    But for my documents?
    My own creations?
    I want access to them, whenever I need it.
    Until connectivity is at a point where that need can be fulfilled, this is all just a big load of ajax in your face.

    --
    I browse at +5 Flamebait- moderation for all or moderation for none.
  70. Anyterm - http://anyterm.org/ by Anonymous Coward · · Score: 0

    Prefer a command line to a GUI desktop? You need Anyterm, a VT100 terminal emulator in "AJAX". Run it on your own server (it's GPL) or join my.anyterm.org. Works through firewalls (only standard ports), can be encrypted with HTTPS.

  71. Thursday, when Javascript killed my browser by billstewart · · Score: 1
    No, it wasn't Google's Javascript - but I had to have Javascript turned on to run all this AJAX stuff like Google maps, so my machine was vulnerable, and
    • last Thursday a chunk of Javascript killed Mozilla in ways that freaked out Windows's window manager, probably with wayyyy too many tabs or too much memory consumption or interrupts or something,
    • today I killed Mozilla myself because something, probably Javascript in some ad window, was burning up the entire CPU, an event that's pretty much weekly,
    • two weeks ago I killed Mozilla because some Indian online newspaper was using Javascript to pop up windows in ways Mozilla didn't block.
    Mozilla lets me turn scripts on/off for browser and for mail/news, but doesn't give me a way to enable Javascript only for pages or domains I trust, and that's a major security hole.

    AJAX lets you make really cool programming decisions about what work gets done in the browser vs. the web-server application, letting us take advantage of things we learned in the 70s, 80s, and 90s, and kept forgetting each time. Gosling's NeWS window manager did similar things with Postscript, which let you really get good-looking WYSIWYG displays, but it was a security and reliability mess, and Java was a way to re-invent some of the good parts while providing decent security models. Javascript has some good programming capabilities, but it's simply not a security model that's trustable, and any time somebody whines about how *they* know how to write perfectly safe reliable Javascript, they need to get whacked with a clue-by-four, because even if they write good programs, leaving Javascript enabled exposes their users to all the malware writers and the much bigger crowd of incompetentware writers out there.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  72. *Javascript* Security holes aren't just one update by billstewart · · Score: 1

    Sure, if somebody you trust makes a mistake in the AJAX application, it's easy for them to update it, whether it's a security fix or just a functional bug. But if Javascript itself leaves your machine vulnerable, which it does, then you either need to turn it off and ignore all the cool AJAX sites, or leave it on and risk that if you visit malware.example.com you'll get handed something that rips your browser to shreds (or at least something that pops up annoying popups - Javascript seems to be the popular workaround for Mozilla popup blockers.) It's dangerous, and needs to be killed or replaced.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  73. HAHA NO! by joshjoneswas · · Score: 0


    Since when has "the world" ever been concerned about "privacy"....

    we will adopt those un-private devices and techniques in swarms!

  74. 1st step to real web applications by Spliffster · · Score: 1

    Call it "Ajax", "Web 2" or event "Web 2 enterprise". it is still markup, some javascript and the ability to script http transfers. The full sets of technology was introduced with IE5, then adopetd by mozilla (and since 1.3 the XmlHttpRequest object is compatible with the one of IE) and now opera and safari 2 (khtml) have also a scriptable http client.

    I see the ajax approach as a nice way to get surfers used to the idea that a web application does not have to refresh the whole ui upon any action the user takes. however, html is just not suitable for rich user interfaces, scripting the missing bits will be an effort every implementor has to take.

    IMHO the real future for such applications lies in WHATWG, XUL and maybe XAML if this technology will be available with vista. Lets see if this is going to happen.

    just my 2 swiss cents.

  75. Re:w00t by Anonymous Coward · · Score: 0

    Looks like idiots have got mod points again...

  76. To solve the privacy problem... by halr9000 · · Score: 1

    Someone should come up with a server framework for all of this ajax goodness. Bundle it into a handy newbie-friendly package and voila, live.com killer.