Slashdot Mirror


A Free XML-Based Operating System

Dotnaught writes "For the past five years, Xcerion has been working on an XML-based Internet operating system (XIOS) that runs inside a Web browser and promises radically reduced development time. To provide developers with an incentive to write for the platform, Xcerion's back-end system is designed to route revenue, either from subscription fees or from ads served to users of free programs, to application authors. Think of it as Google AdSense, except for programmers rather than publishers. Is it absurd to think this poses a threat to Google and Microsoft?"

20 of 175 comments (clear)

  1. Stupid by Anonymous Coward · · Score: 4, Insightful

    I don't know if it's absurd or not because there is absolutely nothing to look at on that web site whatsoever. What is an XML-based operating system? XML is a container format.

    Let this be the thread for all "So what?" posts, please.

    1. Re:Stupid by BruceCage · · Score: 5, Insightful

      Repeat after me "this is not stuff that matters, this is not news for nerds". I honestly can't decide between tagging it 'slashvertisment', 'vaporware' or plain simply 'bullshit'.

      Just stop posting stories like this damnit, I'm looking at you Zonk!

      --
      Perfect is the enemy of done.
    2. Re:Stupid by Speed+Pour · · Score: 4, Insightful

      The sheer concept that this is an OS is out and out wrong. It is nothing more than a UI/Shell that links to an environment on the back end. This doesn't even constitute any loose idea of virtualization or emulation because everything still falls under the sandbox/api realm. The idea of the project might not suck (once/if it's ever working), but it sure won't get very far if everybody keeps using the wrong terminology to describe it.

      --
      - Nobody would know what RTFA meant if it didn't need to be said all the time
    3. Re:Stupid by koreaman · · Score: 4, Insightful

      This is the way of thinking of people who were using Eunuchs for too long.

      UNIX shell = OS.

      Seriously though, UIs are not OSs. The UNIX text-based command interpreters are not operating systems any more than this is, so I don't really see your point. UNIX is an OS. "M$ windoze", or as I prefer to call it, Microsoft Windows, is an OS. I really don't see how using one over the other will magically educate users about computer science vocabulary.

  2. Not an 'Operating System' by iBod · · Score: 4, Insightful

    By TA's own admission, it's not an OS, just an abstraction layer on top of a real OS.

    1. Re:Not an 'Operating System' by dosius · · Score: 2, Insightful

      Not to mention XIOS is already a term in CP/M for "Extended I/O System" (comparable with the DOS BIOS in io.sys/ibmbio.com).

      If it NEEDS AN OS TO RUN, it is not an OS!

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    2. Re:Not an 'Operating System' by Lorkki · · Score: 3, Insightful

      The Xcerion web site nevertheless refers to it as an "Internet OS". I suppose "application framework" is passé as a buzzword now.

    3. Re:Not an 'Operating System' by Jerf · · Score: 2, Insightful

      "OS" is a term that passed into meaninglessness for the IBM world when Windows was released, and somewhat earlier for Big Iron.

      When you have a DOS machine (or even a Commodore 64), there was a clear distinction between the OS (what was resident in memory before the program you really want to use was even loaded), and everything else.

      As you start layering things on top of that, and also building programs that critically depend on those higher layers, it becomes impossible to draw a binary line between "OS" and "Not OS".

      Is KDE my OS? By almost any standard definition, no. On the other hand, the services provided by KDE look an awful lot like OS services to KDE-based programs, like knotify and the unification of remote and local file access that the program doesn't have to implement.

      You can't even get away with claiming everything in the kernel is an "OS". There's a webserver that goes in the Linux kernel itself. Some versions of Windows had a disturbing amount of graphics handling in the inner kernel running in the most privileged processor mode (another possible OS definition which doesn't really work out).

      There's almost, but not quite, no meaningful line to be drawn between "OS" and "programming framework" anymore. Probably the best definition of "OS" is "the set of frameworks that you can not bypass for some task", which in passing encompasses everything traditionally considered an OS. If you want to write a Windows program, you pretty much have to use the Windows Messaging framework. If you want to write a Linux program that uses the network as a normal user, you'll be using the socket framework the kernel provides. You can layer things on top of that, but you can't bypass it, and often there's no way around fundamental limitations in the OS.

      (Note that Linux the OS is therefore much smaller than Windows the OS, because many more pieces of the Linux stack can be ripped out and replaced, like the Windowing system, than you can in Windows.)

      The advantage of this definition is that it's actually somewhat usable and concrete. The disadvantage is, I don't know of anyone else who uses it; most people are still trying to jam the 1970s definition somehow onto our 2007 stack of technology.

  3. Short answer by zmotula · · Score: 5, Insightful

    "Is it absurd to think this poses a threat to Google and Microsoft?"

    Yes.

  4. Well... by Anonymous Coward · · Score: 5, Insightful

    Considering they use javascript for the basic hyperlinks on their website, it seems they lack technical knowledge. That doesn't bode well for a company doing a web OS and if they're doing it using XML why does the W3C validator throw 103 errors on their (non-XML) home page?

    Personally, I don't see these guys as a threat to anyone except themselves and their investors.

    1. Re:Well... by Anonymous Coward · · Score: 2, Insightful

      Google's main page doesn't validate, and we all know how simple it is:
      http://validator.w3.org/check?uri=http%3A%2F%2Fwww .google.com

      Yahoo!'s main page doesn't validate, either:
      http://validator.w3.org/check?uri=http%3A%2F%2Fwww .yahoo.com

      Unexpectedly, MSN's front page is valid XHTML 1.0 Strict:
      http://validator.w3.org/check?uri=http%3A%2F%2Fwww .msn.com

  5. Would rock if it didn't need a full OS and browser by NekoXP · · Score: 5, Insightful

    As subject. How is this meant to change the world or "threaten" Google or Microsoft when you need an OS (probably from Microsoft) and a browser (probably with Google as the homepage, both if we take the most popular)?

    Once you wanna do something in this "internet OS" you'll fullscreen your $179 copy of Internet Explorer on Windows Vista, and fire up an app which probably uses some Google API internally. World changing? Or just another layer between you and them that serves yet more adverts?

  6. Re:Would rock if it didn't need a full OS and brow by jez9999 · · Score: 3, Insightful

    How is this meant to change the world or "threaten" Google or Microsoft when you need an OS (probably from Microsoft) and a browser

    Presumably becuase that OS could be Ubuntu, and that browser could be Firefox. Or OSX/Safari, or Suse/Konqueror, or.....

  7. Re:Why require a browser by jez9999 · · Score: 5, Insightful

    Because a web browser is the only piece of software that fulfills the following criteria:

    - Installed on most machines by default (many policies prohibit the installation of new s/w)
    - Has the capability to be extended to provided an OS-like environment.

  8. Au Contraire -- Sort of by vtcodger · · Score: 5, Insightful
    Does this represent a threat to Google or Microsoft? Not any time Soon

    But then, it's not that long ago that Google was just two guys doodling on scrap paper.

    A few problems have to be overcome including internet latency and the tendancy of everyone to cache stuff they should not be putting in caches (If your PC's memory cache worked like Internet caches do, you'd be lucky to get a Solitaire hand dealt before the PC crashed.)

    And I doubt this is a threat to Google because they will do the same thing it if it works out.

    My impression is that what's good about this specific scheme is that only data is sent over the network, so the annoying latency issues many of us have with Google spreadsheets and Writely should be less of a problem.

    What's bad is that the data is stored on someone's servers. Security will be an issue. So will availability. And loss of data. And ...

    Another problem is that networked "OS"es may not be acceptable for a lot of users because they are just plain too damn slow. A few years ago I slapped together a networked application running on a server here at home for keeping notes together. Worked, sorta. But even though I owned the network and the application was built into server code, not run via CGI, it was too slow to be usable. The problem looked to be latency, not slow processing.

    The few serious attempts I've seen at using HTTP/browsers to do real jobs varied from awful to marginal. IMHO even things like SAIL suck. I'd rather update the /etc files directly. Hell, even ed/EDLINE would be faster and more satisfactory.

    Maybe the problems can be overcome with brains, technology, and money. Maybe they can't.

    Back on topic. Is this stuff a threat to Microsoft? You just bet it is. MS makes most of its money off OK, but overpriced, products that do way more than most customers need (Exception--Xbox which may eventually be a real, money making operation with a bright future). Furthermore, adding more features and charging more for new versions of Windows/Office is probably an unsustainable strategy. We're already seeing geeks and a few organizations walking away from Microsoft. I think that is only going to become more common and some of them may well go to schemes like this.

    --
    You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
  9. Re:Validation for the website by vtcodger · · Score: 3, Insightful
    ***Those guys can't even put down proper HTML, I'm not sure i'd trust them to write a whole web-based "OS" in XML***

    In their defense:

    • The guy doing their web page is probably not one of the folks doing the applications.

    • It appears that a LOT of Web Page developers are totally unaware of standards -- or don't care. My guess is that seriously non-compliant web pages probably outnumber those that are valid on major web sites. Hell, many of them don't even have a DOCTYPE spec and can't be validated.

    • Last time I looked, the Google home page threw about 50 HTML errors when fed to the W3C validator.

    That said, if I were these guys, I'd fix the HTML.

    --
    You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
  10. Balls! by Anonymous Coward · · Score: 1, Insightful

    Users can run software from their local account without installation and more OS installs have a telnet client than web browser.

    What a web browser provides is a convenient way to do a GUI. We could hook common layout engines to different software entirely - and this would make more sense than current hacks atop HTTP **cough** AJAX **cough**

  11. Sorry to be rude - but dictionary time by dbIII · · Score: 5, Insightful

    This is supposed to be the site where we laugh smugly at people who use the word "internets" or who call an application in user space an operating system. What happened?

  12. Not even worth mentioning by Qbertino · · Score: 3, Insightful

    I've been doing professional active content web developement since the late dot-bomb days. Looking at the site for 15 seconds tells me this is probably nothing other than a scheme to fool investors. The things people put out for 'the next big thing' when they discover that JavaScript is a PL and runs in every browser amazes me time and time again.

    There are some points about RIAs one should learn as fast as possible to avoid wasting everybodys time:

    1) JavaScript is nothing new. It's been around for something like 10 years. DTML/Push-Pull JavaScript/Ajax/[Fill in own buzzword of choice] is nothing new. Many people have tried it, many have given up and even the best in 'Ajax' have stepped down again from using it in anything but the most tried and true situations and use cases.

    2) RIA is nothing new. Plugins are nothing new. There are entire landfills full of potential competitors to Flash and Java. Most of them failed. A few remain in niches where others can't reach. The only one I would care to mention is curl, and they are having a hard time and only manage by patiently working away at their tool for x-plattform RIAs.

    3) The big boys Adobemedia / Sun / IBM and some promising others are currently involved in a giant hack & slay fest over the best and most prevailent rich client / server integration. Joining them with some obscure cross-funded project with bad buzzwords, a crappy website and nothing to deliver than something worse than the most half-assed Ajax kit is like showing up on a Knights tournament riding an aged donkey, armed with a cardboard kiddie helmet, a broomstick and a toothpick.

    4) 'We will revolutionize ... blahblah ... the way people/the world thinks about computers/the web/whatever' is allway a dead giveaway that they don't know the troubles involved in building a good web product. There is no free lunch. Even with technologies around or around the corner like Laszlo, Adobes Flex (a Laszlo rippoff), Curl, Eclipse RIA, AMF, JSON/JDON, XUL/XUL Runner - all of which are basically free (all beer and mostly speech) and cream of the crop, building a working RIA that runs on every OS and doesn't bring your new 2 GB RAM Dual Core Turbo PC to a grinding halt is extremly hard work and a very tricky task with bucketloads of tradeoffs to evaluate. I do this every day, the possiblities are growing but the task itself isn't getting any easyer. And the pipedream of emulating a desktop in a browser has been implemented by many, and the best at it admit it's turned out more like a kind of experiment than anything usefull.

    Bottom line:
    This isn't news and it's not the bits worth it takes to transmit it. Move on. No one needs yet another bunch of silly goofs who try and tell the users/clients that they've discovered something new and everything will change if only you run with their buzzword ridden half-assed vision of an untested product that apes things others have finished years ago - and people don't know about for a reason.

    --
    We suffer more in our imagination than in reality. - Seneca
  13. Stupid, but not entirely useless. by tinkertim · · Score: 2, Insightful

    don't know if it's absurd or not because there is absolutely nothing to look at on that web site whatsoever. What is an XML-based operating system? XML is a container format.

    Let this be the thread for all "So what?" posts, please.


    There's a 'trend' running amock that inflicts people with this odd kind of insanity. Apparently they want a Visio like UI to build networks and virtual farms with.

    Anything that gets released that helps keep track of containers with meaningful text descriptors in containers that have very complex parent / child / dependent relationships, I'm all for. That's just less boring stuff one has to muck with to satisfy a client's web 2.0 fetish.

    I don't see this as very novel at all, nor really useful as a whole as its intended. What I do see is a bunch of possible cool parts I can throw in something else. Will withold official judgement until they actually release something.

    Could just be vaporware too.