Slashdot Mirror


Where Is Firefox OS?

adeelarshad82 writes "Microsoft's very simple yet graceful concept raises a very big question. The way Microsoft is planning out Windows 8, developers will be able to write one HTML 5 app which will run across every Windows 8 form factor, from desktops to laptops, to ARM netbooks and tablets. Given the concept, if you remove the operating system — or at least make it transparent enough that the browser becomes the platform — then suddenly every piece of software works across every piece of hardware which raises the question that why Mozilla hasn't considered a Firefox OS?"

45 of 288 comments (clear)

  1. Q: Why hasn't Mozilla considered a Firefox OS? by MrEricSir · · Score: 5, Insightful

    A: Because it's a dumb idea.

    --
    There's no -1 for "I don't get it."
    1. Re:Q: Why hasn't Mozilla considered a Firefox OS? by TubeSteak · · Score: 2

      [sarcasm]I can't wait for the day that the OS is a browser and everything runs in either flash, javascript, or some proprietary plugin that is plagued with memory leaks.[/sarcasm]

      --
      [Fuck Beta]
      o0t!
    2. Re:Q: Why hasn't Mozilla considered a Firefox OS? by MoonBuggy · · Score: 2

      I'm torn on that one - on the one hand I want to say that an extra layer of abstraction, wasting memory and cycles itself only to interpret code on the fly rather than taking the time to compile and optimise once per platform and be done with it, is a terrible idea. Particularly when it's designed to help move code to diverse, often lower power devices.

      On the other hand, most high-end phones now have as much processing capability and memory as a decent desktop did a decade ago, yet many of our day-to-day computing tasks haven't changed drastically in ten years - maybe letting the power make up for the bloat isn't such a bad idea, when it's not so useful for anything else. Sure, there'll always be space for highly optimised code that makes use of every cycle, but (as much as I hate to say this) perhaps we're wrong to demand 'elegant' when 'simple' is good enough for a lot of tasks...

    3. Re:Q: Why hasn't Mozilla considered a Firefox OS? by MrEricSir · · Score: 4, Insightful

      It's like using a desktop computer just so you can remotely eject the CD tray and knock over a cup of water to water your plants while you're on vacation.

      Yes, you COULD do that, but it's wasteful and unnecessary. And last I checked, wasteful and unnecessary weren't the hallmarks of a "simple" design.

      --
      There's no -1 for "I don't get it."
    4. Re:Q: Why hasn't Mozilla considered a Firefox OS? by Carnildo · · Score: 3, Funny

      "Firefox would be a great operating system, if only it had a decent web browser"

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
    5. Re:Q: Why hasn't Mozilla considered a Firefox OS? by RobbieThe1st · · Score: 2

      Thanks to bios boot-at-specified-time, and OS shutdown-at-specified-time, this could actually be perfectly plausible. :P

    6. Re:Q: Why hasn't Mozilla considered a Firefox OS? by Oligonicella · · Score: 3, Funny

      No, he's not. I've seen his code.

    7. Re:Q: Why hasn't Mozilla considered a Firefox OS? by n3xg3n · · Score: 3, Funny

      You mean you don't allocate memory to store your comments as strings?

    8. Re:Q: Why hasn't Mozilla considered a Firefox OS? by dudpixel · · Score: 2

      no one seems to be concerned with the Windows 8 part of the story.

      Are Microsoft so directionless these days that they would consider a move that makes the ENTIRE windows stack basically irrelevant?

      If people start coding for HTML5, suddenly windows is out of the picture, because the apps would run just as well on linux or mac.

      I thought the whole reason for Windows' existence was windows-specific software. If we remove that, what does windows have going for it?

      --
      This seemed like a reasonable sig at the time.
    9. Re:Q: Why hasn't Mozilla considered a Firefox OS? by cshark · · Score: 3, Informative

      It has been done. The project is in Freshmeat. It was promptly started in 02 or 03 I believe, and abandoned, like most other somewhat interesting projects there. In fact, if memory serves, there may have actually been two of them around the same era. Both long dead. The reason being (as usual) that people on Freshmeat and similar sites would rather tell you how much of a dick you are for trying something interesting, than paying any attention to how novel your project is. At the time, this was revolutionary stuff. Did anyone care? No, of course not. The only time anyone cares about anything Open Source is when there's a marketing budget behind it.

      Be that as it may, the Mozilla OS project(s) I vaguely remember were true browser as a platform for desktop style gui projects, ala 'let's build a whole desktop environment in XUL' type stuff. What Microsoft is proposing is not a true browser as a platform system. Closest thing to browser as a platform that's in active development now is Chromium, which looks nothing like Windows 8. Sure, it's nice that Microsoft has finally gotten their head out of their ass with hypertext apps. This has been coming since Windows 95, though, and I'm not seeing anything really all that new in it except compatibility. But if you're going to be least bit critical about it, that's something that should have existed all along.

      I remain skeptical.

      --

      This signature has Super Cow Powers

    10. Re:Q: Why hasn't Mozilla considered a Firefox OS? by rtb61 · · Score: 2

      Now all you have to do is solve the screen real estate, colour, resolution, memory abstraction and you home and hosed. Of course you have to forget those pesky mobile phones as well.

      Reality is what you are after is an IDE that you code in one language and architecture and it writes the code for the other architecture and language types that you want to use. So a big bloaty IDE rather than M$ typical solution bloated clunky OS with half arsed solutions and a whole lot of promise with only random temporary delivery.

      When it comes to innovation, the real push is to be able to compile software engineering concepts and terminology, into tweak able code and then into variable architecture machine language. Converting software engineering into executable code is really a job that computers were designed to do, solving that patentable software interface that takes human specific language and terminology and translates that into editable code prior to compilation, is the real trick. Really does require a new coding language that suits that translation and post pass readability and adjustment.

      --
      Chaos - everything, everywhere, everywhen
    11. Re:Q: Why hasn't Mozilla considered a Firefox OS? by tehcyder · · Score: 2

      If you tag it as sarcasm, then it isn't

      [dumbass]
      He did something wrong with the HTML, I could still see the tag names.
      [/dumbass]

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  2. Fine with me. by The+MAZZTer · · Score: 2

    It's fine with me Mozilla isn't doing a "Firefox OS". They can focus more of their efforts on the core Firefox product. Besides, Google is doing a good enough job already with a browser-based OS if you ask me.

    1. Re:Fine with me. by arth1 · · Score: 3, Informative

      Besides, Google is doing a good enough job already with a browser-based OS if you ask me.

      Then they do it in secret labs, cause there's no such thing out in the wild. If you mean ChromeOS, that's not a browser-based OS, but a locked down Gentoo Linux that runs on a locked down file system, running a locked down display manager that runs a locked down Window manager that runs a (you guessed it: locked down) version of the Chrome browser inside it. The browser is four steps away from being an OS -- it's just another app -- the main app, but still just an app.

      Having the browser be the OS is by all means possible - if the browser contains a kernel, file system, drivers and everything else needed. But what would the point be?

  3. Because its a stupid idea by MikeBabcock · · Score: 5, Insightful

    The 'browser as an OS' concept is still stupid.

    I could draw it out and make it sound pretty, but its stupid nonetheless. Once you've made the browser so big that it encompasses all possible generic operating system needs, it is too bloated and someone else makes a smaller faster better browser.

    Operating systems and browsers are two different things.

    Now as a work environment, say a desktop interface, browsers have potential, and that's what most people mean, but even there, the security problems of dividing up what is local data and what is remote, what should be executable and what shouldn't becomes a nightmare that is easier to handle when avoided completely.

    HTML5 isn't the best way to write any application; that's why almost everyone else who's made an HTML based platform has moved to a native one after the fact. Does HTML need the features necessary to write generic applications? Certainly not. The overloading of protocols (everything as HTTP) and formats (everything as HTML/CSS) is just short sighted laziness.

    Please make it stop.

    --
    - Michael T. Babcock (Yes, I blog)
    1. Re:Because its a stupid idea by amicusNYCL · · Score: 4, Funny

      Once you've made the browser so big that it encompasses all possible generic operating system needs, it is too bloated and someone else makes a smaller faster better browser.

      Now there's a thought.. Mozilla can wait until everyone else gets all bloated, then they can launch a new project to create a fast, lightweight standalone browser without all the bloat of their current offering.

      --
      "Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
    2. Re:Because its a stupid idea by MikeBabcock · · Score: 2

      Chrome was the tiny fast lightweight browser yesterday. I wonder who's next.

      --
      - Michael T. Babcock (Yes, I blog)
    3. Re:Because its a stupid idea by AaxelB · · Score: 2

      A bit of a whoosh there: Firefox was the tiny fast lightweight browser last week (that's the joke), before Chrome became the tiny fast lightweight browser browser yesterday. As for tomorrow, well, it'll probably be on a smartphone :)

    4. Re:Because its a stupid idea by rtfa-troll · · Score: 5, Insightful

      The 'browser as an OS' concept is still stupid.

      [...] Once you've made the browser so big that it encompasses all possible generic operating system needs, it is too bloated and someone else makes a smaller faster better browser.

      The whole point of the "browser is an OS" is not to "encompass all possible generic operating system needs". The idea is that most of those needs will be handled by a "the cloud". Most of the time, when Microsoft or an IT manager talks about it, that doesn't mean anything sensible. However, when Google talks about it, it really means

      • You aren't going to have to do file storage because your named objects are going to be stored in the cloud server and just cached locally
      • You aren't going to have to do much computing because most of that will be handled by Google's servers
      • You aren't going to have to think about application security because that will be handled by Google's
      • You aren't going to have to control privacy and data flow because Google will do it for you.
      • You aren't going to have to handle user management because Google will do that for you.
      • You aren't going to have to handle setting up a file server/ file sharing because that will be done already, by Google
      • etc.

      If that list scares you, then it should. Basically what you are saying here is that when you move to a "Browser is the OS set up" what you are actually moving to is a "Google is your administrator and your system and all applications are controlled by them set up". You had better hope they are nice http://www.theregister.co.uk/odds/bofh/>operators

      Operating systems and browsers are two different things.

      You are answering the wrong question here. The question isn't "should I build these things separately". The question is, "should the user have any understanding of the underlying operating system, and if so, do I need any more interface to it than a web browser can provide?" The Google answer is "no". Fundamentally, you as a naive user, surrender everything to Google. Your so the OS is still there, just the user doesn't have to worry about what it does or how it works.

      HTML5 isn't the best way to write any application; that's why almost everyone else who's made an HTML based platform has moved to a native one after the fact.

      Given that nobody has fully implemented it ye very few of the people who used HTML used HTML 5, so that comparison isn't yet made. Probably we should come back to that ten years from now to get the proper empirical data. However, every potential alternative platform has problems:

      Windows binary no simple way to install applications; user need to download, install, approve etc. Many different incompatible versions and bad multi-version support Linux binary not widely enough installed; users are resistant to learning; several different versions OS/X binary both disadvantages of Windows and Linux at once! Java "binary" horribly variable platform versions; users are resistant; inconsistent user interface; ugly Flash "binary" partly incomplete platform access; horrible security model; horribly s.low and unstable; at serious risk of elimination in the next couple of years HTML5 / AJAX incomplete platform access; slow.

      Does HTML need the features necessary to write generic applications? Certainly not.

      Again it's the wrong question. The question is: "does it make sense for the people writing the HTML 5 standard to make generic applications possible". The answer is "unfortunately yes". They see a gap in the market and they are closest to filling it. Let's be clear what the gap is:

      • Cross platform (Windows XP -> Windows 2008 / OS/X / Linux + Mobile )
      • Dynamically installable (you don't need t
      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    5. Re:Because its a stupid idea by SanityInAnarchy · · Score: 2

      Basically what you are saying here is that when you move to a "Browser is the OS set up" what you are actually moving to is a "Google is your administrator and your system and all applications are controlled by them set up".

      I can't imagine Microsoft deliberately walking into that.

      No, it seems much more like, Google and others may provide a software-as-a-service version (pure Web), but it can also run locally. At this point, it's essentially a replacement for the other platforms you mentioned -- Java being the closest, I think.

      I do wish there was more emphasis on local servers, but as a developer and a user, I actually like this trend. As a developer, it means that while my frontend is forced into HTML/CSS/JavaScript, my backend can be anything I want, and I don't need to make my backend code run on everyone and their dog's Windows machine, let alone every OS. I can push a lot of stuff to the backend, and what's left is much easier to make work on all recent browsers than it is to, say, make a portable C++ app that works on all OSes -- and if it was Java, I'd have to either include a JVM or force users to download one.

      And as a user, it means everyone making an actual Web app is actually making a Linux app without realizing it -- and a whatever-OS-I-want app. As a user with some dev skills, I actually get more control over many of these apps, not less -- while I may be surrendering my data (if I had any to begin with; I tend not to put important stuff "in the cloud"), I gain the ability to use userscripts (Greasemonkey), custom CSS, or even my own web scraper to interact with this app in any way I want. (Every webcomic I read now has keyboard shortcuts, whether they wanted to or not (thanks, XKCD!).) Even if I didn't have development tools, I could still download userscripts and extensions which extend the functionality of the app.

      It also means I get features I actually like from the Web. Not installing, or streamlining installation, is nice (thank you, Linux package managers), tabs, bookmarks, back/forward, or sending a link to a friend. These are all things which can be implemented (reinventing the wheel) in native apps, but for a well-designed web app, they just work. It's true that sometimes the developers have to deliberately re-enable these things (hash URLs), but it's common for this to happen, since users expect it.

      My main complaint was being forced into JavaScript/HTML. But now we've got canvas (and even WebGL) and Google's Native Client for things which don't fit well with JavaScript/HTML, though again, most things do -- I used to hate HTML, but more recently, I've come to appreciate its extensibility (microformats and such) and semantic markup. I also used to hate HTTP, but take semantic markup + REST + proper use of hypertext, and you've got an API almost by accident, as an artifact of writing an app correctly.

      Every new protocol seriously adopted in the last years seems to have to have an http tunnelled equivalent. This is insane...

      For every protocol, maybe. But for the vast majority of protocols, HTTP done right (REST or websockets) is actually a good fit.

      Still, I do wish there was some API by which a web app could ask for cross-site, or a generic socket API. That's about the only thing that's missing.

      it's just another binary format equivalent to ELF or COFF.

      Except, unlike those, it's actually standardized to the point where if you get an x86_64 binary and you're running and x86_64 browser, you can execute it, no matter what OS you're running -- whereas ELF (other than within NativeClient, if they're still using ELF) doesn't run on Windows, for example. There's also a "portable native client" which compiles to LLVM bytecode, which can then be compiled on the client's system, so you're not even necessarily locking people to an architecture.

      --
      Don't thank God, thank a doctor!
  4. Linux with Firefox Kiosk by PineHall · · Score: 2

    Does a Linux kiosk OS count? How about Webconverger? It is a Debian derivative kiosk that uses Firefox.

  5. Sigh... by Haedrian · · Score: 4, Insightful

    Just install a very lightweight linux distro. Install firefox on it. Set it to full screen mode.

    Done. No need to reinvent the wheel.

    1. Re:Sigh... by dakameleon · · Score: 2

      Sshhhh.... reinventing the wheel is what we in IT get paid for, half the time!

      --
      Man who leaps off cliff jumps to conclusion.
    2. Re:Sigh... by dudpixel · · Score: 2

      Sshhhh.... reinventing the wheel is what we in IT get paid for, half the time!

      Half?

      yes. We actually re-invent the wheel 100% of the time, but we only get paid for half.

      --
      This seemed like a reasonable sig at the time.
  6. The way forward. by mark_elf · · Score: 2

    Great idea. Then they can make an OS web app that runs on the browser, basically a windows add-on for firefox. That way you can upload your OS in the cloud and just stream it over 3G to all your devices whenever you need it. A side benefit would be that Microsoft would finally get paid for all the pirated software people have stolen from them over the years.

  7. They don't want to? by tverbeek · · Score: 3, Interesting

    Because then they'd have to deal with all the hardware support and driver incompatibility bullshit that Microsoft and Apple and the Linux crew have to deal with. Not everybody wants to code at the metal level.

    --
    http://alternatives.rzero.com/
  8. Re:Why? by dakameleon · · Score: 2

    Name one other open-source browser developed by an open community process not funded by a corporation that doesn't have some sort of lag on fixing some bugs.

    I'm not a FOSS evangelist, but for the resources they have it's not out of the bounds of expectations in my book.

    --
    Man who leaps off cliff jumps to conclusion.
  9. I just want a browser by Windwraith · · Score: 5, Insightful

    Am I the only one who just wants a browser?
    Sure, I like stuff like javascript games (I am a game dev so the topic inherently catches my attention) and some webapps, but I am certainly not willing to give my browser that much importance.
    For me the centerpiece of the OS is the file manager and the tools to do my tasks. I don't want to have to depend on just a browser or webapps that don't have local code to run from your physical computer. We know the cloud is not 100% reliable (sure, it's not 100% unreliable either, but until there's no choice but to use it, I want to use that choice).

    1. Re:I just want a browser by woolpert · · Score: 3, Insightful

      For me the centerpiece of the OS is the file manager and the tools to do my tasks

      This is an argument against the browser as OS and gets +4 insightful? The mind boggles.

      1 - File manager as centerpiece of OS:
      A - A file manager is an app (of my choosing) which runs on top of my OS.
      B - As we have already seen browser (IE / Konqueror) is hard to distinguish from a file manager (Explorer / Konqueror) and so if we accept your argument that the file manager is the centerpiece of an OS there is evidence aplenty that a browser is said centerpiece.

      2 - "The tools to do my tasks" as co-centerpiece of an OS.
      If ever there was a classic definition of "applications" it was "the tools to do my tasks". The OS is the tool to do the application's tasks. If we're going to zoom out and take such a broad view of what an OS is (it sounds to me like you're describing a desktop environment ) how are current browsers not inches away from that already?

      We know the cloud is not 100% reliable

      Where in the concept of "browser as OS" is "no off-line content" made explicit?

  10. Why!? by MrEricSir · · Score: 2

    And you couldn't do the exact same thing with native code because...?

    --
    There's no -1 for "I don't get it."
  11. HTML? Really? by thisnamestoolong · · Score: 3, Insightful

    MS is really talking about using HTML as the best way to port code between the different versions of Windows 8? That is at least 4 different kinds of fail.

    --
    To the haters: You can't win. If you mod me down, I shall become more powerful than you could possibly imagine
    1. Re:HTML? Really? by Mia'cova · · Score: 3, Informative

      No... they're saying "hey all you web developers out there, you can make apps for us now too without having to learn anything new! Now whip together your facebook/amazon/ebay website app ports in 1/10th the time it takes you to do so on iphone/ipad!"

    2. Re:HTML? Really? by shutdown+-p+now · · Score: 2

      The official demos so far have focused on HTML5/JS as a development platform for Windows 8. Nothing has been said about it being "the best way to port code between different versions of Windows". For that matter, nothing has been said about the need to port code at all.

      Until September, anyone who tells you that they know anything other than what's said in that video (like this Slashdot story) is presenting his guesswork as facts.

  12. They already are; Slashdot reported on it... by Mekabyte · · Score: 3, Interesting

    just two weeks ago. Webian Shell on top of Linux sounds a lot like Chrome OS to me...

  13. Mozilla is libre OSS by fermion · · Score: 3, Insightful
    IMHO, Mozilla was created to leverage the assets of Netscape to prevent a world in which proprietary MS protocals controlled the web. There was no business model in which Mozilla had to be the market share leader. There was no need to play games in which users had to be lured to give up personal data. A cross platform browser allowed users freedom to choose a machine that suited them and then run an appropriate Mozilla variant. I myself use Camino.

    MS needs a browser based OS to maintain market share in the world of sub-$500 internet devices. We have seen these fail, and everyone is saying lack of mobile broadband is going to kill them, but these are going to be targeted at home user with WiFi that want inexpensive machines that can move around the house. The benefit is going to be reliability, and MS want to take users away from Apple in this lucrative market and return them to MS.

    Likewise Google has to have a mobile OS to continue to collect information. The mobile OS is prefect for Google because everything a user does is recorded, track, mined, and sold. Google already has significant market share, so, as we see, the internet devices are being sold at a healthy profit, and the benefit to the user are free applications after the fact. This gives MS hope as it can often intimidate manufacturers to sell at a less healthy profit in return for marketing support that will create the volume that MS wants.

    So we have one company that wants a WebOS to keep it office franchise alive, another that wants to keep the advertising money flowing. Where would mozzila be? They have no market share concerns, they have no free apps, and there is no open hardware platform for a table or internet computer. So one can buy an expensive laptop, pay the internet tax, and then install this great Mozilla OS. We have seen how well this works for Linux. Or one can buy the allegedly open Android or Chrome tablet and install Mozilla. What is the point? Chrome is not a bad OS.

    As we have seen on the iPhone, software developers don't want to develop for the web browser. They want native Apps. The machine needs to do both, unless one is in the business of locking in users like MS or Google.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    1. Re:Mozilla is libre OSS by yarnosh · · Score: 2

      MS needs a browser based OS to maintain market share in the world of sub-$500 internet devices.

      That makes no sense at all. Microsoft needs to continue lock people into things like .NET to maintain market share. If everything goes browser based, there's no reason for anyone to pay for Windows... even a WebOS version. The only way it would work is if they make their "web apps" incompatible with other browser. But then, what's the point? You might as well just invent a better technology besides HTTP/HTML that will give you good thin client functinality without all the drawbacks of the browser.

      Likewise Google has to have a mobile OS to continue to collect information.

      This much is true.

      Chrome is not a bad OS.

      It isn't really "good" either.

  14. silly assumptions. by asa · · Score: 2

    "which raises the question that why Mozilla hasn't considered a Firefox OS?"

    Mozilla has considered a Firefox OS and decided against it.

  15. huh? by Charliemopps · · Score: 2

    Can someone summarize this article for me? I can't open the link because firefox has been constantly locking up on me since the last release.

  16. Re:Easy. by icannotthinkofaname · · Score: 2

    slow pieces of shit.

    Well, that's no excuse. That didn't stop Windows Vista from being considered and released.

    --
    Let q be a radix > 1. I am in ur base-q, killing 10 d00ds.
  17. Re:Because firefox is shit? by RoFLKOPTr · · Score: 2

    MS's beatdown of little-guy Netscape doesn't really say anything about behemoth Google's chances of success, and there's room for Mozilla (and anyone else) to survive with some coat-tail surfing.

    Except Google isn't gunning for market share, and I believe they're still one of the larger sources of direct funding for the Mozilla Foundation. Google just wants advancement. Before Chrome came along, every browser's javascript engine was absolute shit. Slow and crappy and slow and slow. V8 kickstarted everybody's interest in Javascript (as Javascript is what really makes Google run) and now everybody is much faster than the first release of Chrome, which gives Google plenty of room to make bigger, better browser applications. They didn't want to beat everybody, they just wanted to scare everybody and say "Look, speed is important to people. Do you see how fast our market share is growing? You had better pick up the pace or you will become irrelevant as quickly as our new browser renders Google Maps Satellite View."

    It worked.

    And today Microsoft still holds the majority of the browser market share, but most of that comes from enterprise and people who either prefer IE (those people DO exist, believe it or not) or people who just don't care to deviate from the default (which is also just fine).

  18. Re:Because firefox is shit? by RoFLKOPTr · · Score: 2

    January in Canada is fairly different depending which side of the country you're on.

    Seasons are opposite across the equator, sir. When it's Winter on one side of Canada, it's Winter on the other. The only difference is that Southern Canada might be i-cant-feel-my-face cold while Northern Canada is holy-shit-i-think-my-balls-just-froze-off cold.

  19. What's the difference? by yarnosh · · Score: 2

    What would a "Firefox OS" do that running FIrefox fullscreen won't? If you want to make your web browser your only application, DON'T RUN ANY OTHER PROGRAMS. Jesus Christ people, there's nothing innovative or novel about a system that will only run a web browser. It is a crippled system and a stupid idea.

  20. Java? by Loosifur · · Score: 3, Interesting

    I remember back in the day, when I actually wanted to major in CS, Java came out. Yes, that long ago. And the big thing about Java was that you would be able to write code that was platform-independent, and just rely on a Java interpreter that would be released on any necessary platforms. Which is why everything is written in Java now...

    I'm just saying, using a browser as a conveyance for some sort of universal HTML-based software market just seems like a new version of an old idea that didn't pan out in the first place.

    Also, not to nitpick (well, yes to nitpick), but I think that part that says "suddenly every piece of software works..." needs a bit of filling out. Especially at the "suddenly" part.

    Also also, Mozilla would be better off not trying to be the Gobot to Google's Transformer, if you see what I mean. That niche is already being filled by Google. Mozilla should focus on making a niche for Firefox, not making it an also-ran to Chrome OS. Full disclosure, I'm not a fan of Firefox since Chrome came out, and since I put Opera on my Droid. But, there must be some area where Firefox excels, because it has a solid base of users. They should exploit and enhance that area.

    --
    This unbiased moderation brought to you by the Porcine Aviation Group!
    1. Re:Java? by SanityInAnarchy · · Score: 2

      And the big thing about Java was that you would be able to write code that was platform-independent, and just rely on a Java interpreter that would be released on any necessary platforms. Which is why everything is written in Java now...

      I don't think that's the biggest reason. I think the biggest reason is that it was reasonably similar to other 800-lb gorillas, like C++, but included things like garbage collection.

      I'm just saying, using a browser as a conveyance for some sort of universal HTML-based software market just seems like a new version of an old idea that didn't pan out in the first place.

      Maybe so, but here are some things that help:

      First, there are multiple implementations with significant marketshare. If your app didn't run on things like kaffe or gcj, no big loss -- if one of Oracle's flagship JDeveloper-based frameworks doesn't work on OpenJDK today, they don't care -- hell, one of the bigger reasons Java failed is Microsoft delivered a broken JVM, and if you only care about supporting Windows, you code to Microsoft's broken JVM and you don't need to run anywhere else. Even ignoring that, I've taken recent code written for Java6 and had it fail to run on Linux because the code was littered with hardcoded backslashes, and had never had to run on an OS which used a different path separator. But if you want your HTML to work, you need to at least support the latest Firefox, Safari, Chrome, and maybe IE and Opera.

      If you've done that, there's a good chance you've coded more or less to the standards, with a minimum of per-browser hacks, because to do otherwise would be insane -- which means there's a good chance that if I'm using a browser you didn't test, but my browser implements the specs reasonably, your code probably works. If Java developers had been forced to test their code on Windows, Linux, and OS X, there's a good chance it wouldn't break on, say, Solaris -- in the example above, they'd at least be forced to hardcode a forward slash instead (which works on all of the above platforms) or use the system path separator.

      Second, because of this actual competition, all browsers, proprietary or not, aren't just competing to add crazy new non-standard features, they're also competing to implement the standard the best. The ACID tests helped a lot here -- no one (not even Microsoft, anymore) wants to be known as the browser that universally scores dead last here, and is therefore causing developers the most headaches when porting their code. By contrast, the only reason Java can maintain anything approaching a standard is because there is exactly one implementation, which is also a terrible thing for an open standard. Look how much uncertainty there was when Oracle started suing people (like Google) over making something similar to Java, but not quite. If Java was more like HTML, then Dalvik would've been pressured to become more and more standard, and where it got the standard and OpenJDK didn't, OpenJDK would be fixed -- but instead, Oracle sued.

      Third, there's the part where you don't need to install anything. Everyone already has a browser, and most people have a fairly decent browser, other than, maybe, office drones stuck with IE6 -- but then, they'd also be stuck without Java or with the wrong version of Java.

      Fourth, people already have to target the Web anyway. It's no longer acceptable to force people to load a Java applet, and even Flash is getting unfashionable. You need a Web presence, at the very least, and the more stuff that works from the Web, the better off you are -- after all, if you're forcing people to download something, and your competitors "just work", you lose. And once you've got something on the Web anyway, especially if it's something at all interactive, the transition to using it as an application platform isn't that big.

      It also helps that JavaScript doesn't suck nearly as much as Java, as a language.

      But whatever the reason, it also looks like this s

      --
      Don't thank God, thank a doctor!
  21. Re:Netscape had this plan at the beginning by SanityInAnarchy · · Score: 2

    Not enough people, anyway, for it to be really successful. I think part of the problem is that it took them ages to actually create a separate "XULrunner" package, so that you could install XUL once and then install Firefox, Thunderbird, Sunbird, Songbird, etc. When it was just the Mozilla Suite (Seamonkey, now), it might have made sense to bundle XUL with that, but if I ship a XUL app, it shouldn't be tied to Firefox itself.

    But people did write apps using XUL -- Songbird wasn't even affiliated with Mozilla, if I recall. And people wrote tons of Firefox extensions that are almost standalone apps in their own right -- Zotero, for instance. (I think Zotero would make more sense as a standalone XUL app and a "send to Zotero" Firefox extension, but whatever.)

    There's another reason XUL never caught on, though: It seemed pointlessly different than HTML. That is, they created their own separate markup language, rather than extend HTML. At the same time, you couldn't really write websites in XUL -- if I recall, it would at least ask for some sort of permissions -- that, and it wouldn't run on any other browser. So, despite the fact that so much of the Firefox UI (or, I'd guess, most of Firefox that isn't Gecko) is written in XML+JavaScript, it was still very different than the Web itself.

    Compare this to their new invention, Jetpack, which is really taking the main idea behind the Chrome extension API and applying it to Firefox -- Chrome extensions almost entirely use HTML+JavaScript. They add some custom JavaScript APIs, but other than that, if there's a way to do what you want to do in HTML+JavaScript, they won't duplicate it for Chrome -- for example, if you absolutely need to run native code with full OS access, you use NPAPI and write a plugin, and restrict it to your extension.

    I think this might be why HTML5 is taking off as an actual generic application platform -- people need web apps anyway, so it's already a cool idea to take your web app offline and integrate it into the desktop. Or, if you're writing a new app, you already have a bunch of web developers that you needed for your web app, so you don't need to hire or train experts in Win32 or .NET -- you just write another web app.

    --
    Don't thank God, thank a doctor!