Slashdot Mirror


Firefox OS Will Win Big With Developers - Mozilla

judgecorp writes "Mozilla's mobile operating system Firefox OS will win overwhelming support from developers because it dropped XUL in favour of HTML5, says the head of Mozilla Europe in an interview. Firefox OS is more open than iOS and Android, and 75 percent of apps are already written in HTML5."

229 comments

  1. Uh huh... by Anonymous Coward · · Score: 4, Insightful

    This just in: Mozilla employee tells us that Mozilla product will be a huge hit!

    Why don't we wait until it comes out before making such claims?

    1. Re:Uh huh... by Anonymous Coward · · Score: 0

      My question is can they afford the litigation costs of producing a mobile OS in the current legal landscape (er minefield as the case may be)?

    2. Re:Uh huh... by sonicmerlin · · Score: 1

      Has anyone seen this in demonstration on video? It's so laggy it makes Android seem iOS-like. Even if it's "popular" with developers, it won't be with consumers and thus will be dead on arrival.

    3. Re:Uh huh... by cripkd · · Score: 1

      Huh, it didn't seem that laggy plus it's pre-alpha and we have no hints on the hardware specs, so don't be hatin' !

      --
      Curiously yours, crip.
    4. Re:Uh huh... by justforgetme · · Score: 1

      Well, the demos that are roaming the net these days still are pre alpha so tactile performance probably is not the main development area at the moment. That's probably still very wise since afaik the graphics pipeline is still being heavily developed.

      --
      -- no sig today
    5. Re:Uh huh... by tripleevenfall · · Score: 1

      Mine too.

      The closed or "open" (with sarcastic quotes) mobile OS vendors now have probably gobbled up all the obvious stuff that is patentable.

      Sadly the more open an OS is, the less likely it is to be backed by an organization capable of defending it legally.

  2. This sounds awfully familiar. by dosius · · Score: 1

    Firefox OS? Didn't Netscape try to do that with Communicator 4 and fail horribly?

    -uso.

    --
    What you hear in the ear, preach from the rooftop Matthew 10.27b
    1. Re:This sounds awfully familiar. by PopeRatzo · · Score: 4, Funny

      Firefox OS? Didn't Netscape try to do that with Communicator 4 and fail horribly?

      No and yes.

      --
      You are welcome on my lawn.
    2. Re:This sounds awfully familiar. by cpu6502 · · Score: 1

      No. The point of Firefox "OS" is to use the web browser to run software out of the cloud (the internet). Netscape Communicator didn't do anything like that.

      Also I wouldn't call Netscape's integration of email, web, groups, composer into one package a failure. It still lives on as Mozilla seaMonkey. The browser from Opera also offers the all-in-one experience. Both have been successful over the last 10+ years.

      --
      My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
    3. Re:This sounds awfully familiar. by Anonymous Coward · · Score: 2, Funny

      Firefox OS? Didn't Netscape try to do that with Communicator 4 and fail horribly?

      No and yes.

      Ah, thanks. That clears things up.

    4. Re:This sounds awfully familiar. by dzfoo · · Score: 1

      That's not what he meant. He was talking of Mozilla's integration of Java, JavaScript, and XUL to create a platform for executing applications, that are not dependent on the underlying OS.

      --
      Carol vs. Ghost
      ...Can you save Christmas?
    5. Re:This sounds awfully familiar. by dzfoo · · Score: 1

      And by Mozilla, I meant Netscape. DOH!

      --
      Carol vs. Ghost
      ...Can you save Christmas?
    6. Re:This sounds awfully familiar. by shitzu · · Score: 2

      Firefox os they are talking about here will run on mobile devices. It is not meant to run specifically software out of the cloud. The HTML5 apps might be local and probably many (if not most) of them are. After all, there are plenty of situations where you want to use your mobile device in a disconnected environment. For example listening to music in an airplane. Or taking notes in a forest. Etc.

    7. Re:This sounds awfully familiar. by justforgetme · · Score: 1

      Can we agree to just call it "The Internet" again?
      Please?

      --
      -- no sig today
    8. Re:This sounds awfully familiar. by shitzu · · Score: 1

      Erm... no. Firefox Mobile OS is not what you think it is. It is not a "web browser IS an OS" thing. It is an operating system for mobile devices that runs all its userspace programs in HTML5. It is scheduled to launch nex year with several phone manufacturers already promising devices with it. When you buy a phone with it, you are not going to say "my phone runs The Internet", you are going to say it runs "Firefox Mobile OS" (unless they change the name).

    9. Re:This sounds awfully familiar. by justforgetme · · Score: 1

      I was referring to the abuse of the term "cloud".

      --
      -- no sig today
    10. Re:This sounds awfully familiar. by Hognoxious · · Score: 3, Funny

      The point of Firefox "OS" is to use the web browser to display a popup saying:

      A script on this page is running slowly.

            [stop] [continue]

      FTFY.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  3. No, it won't by Anonymous Coward · · Score: 3, Interesting

    Actually it won't.

    Developers will look towards the jobs which earn money, meaning the popular platforms like iOS and Android. To even think Firefox OS will in any way take a reasonable portion of the marketshare is a complete and utter joke.

    Mozilla missed the mobile boat 2 years ago. Hear that mozilla? It's the sound of a fog horn in the distance, get swimming(which is what they're doing right now).

    They should refocus their efforts or they're going to drown.

    1. Re:No, it won't by Anonymous Coward · · Score: 3, Interesting

      I think they were told the same thing about developing a browser when internet explorer owned the market.

    2. Re:No, it won't by cpu6502 · · Score: 1

      Firefox isn't meant to replace iOS or Android (as you would know if you read mozilla's website). It's simply an option for users to run their software *inside* the browser using HTML5, rather than a separate app.

      --
      My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
    3. Re:No, it won't by Anonymous Coward · · Score: 3, Interesting

      Developers will look towards the jobs which earn money, meaning the popular platforms like iOS and Android. To even think Firefox OS will in any way take a reasonable portion of the marketshare is a complete and utter joke.

      A lot of apps are written in HTML5 and then converted - using tools like PhoneGap - to apps for iOS and Android, so there's already a huge developer base writing apps with these tools.

      I can definitely imagine devs writing an Open Web App and then using one of these native wrappers to package it up for the other operating systems.

    4. Re:No, it won't by Anonymous Coward · · Score: 0

      Firefox isn't meant to replace iOS or Android (as you would know if you read mozilla's website). It's simply an option for users to run their software *inside* the browser using HTML5, rather than a separate app.

      Actually, it is. Firefox OS (neé Boot2Gecko) is a complete operating system, running on the Linux kernel and using device drivers written for android (and others written in Javascript).

      *All* apps, even the dailer and SMS apps, are written in HTML5.

    5. Re:No, it won't by cpu6502 · · Score: 2

      >>>Firefox OS (neé Boot2Gecko) is a complete operating system

      I have an anonymous coward saying one thing, and Mozilla saying something else. I think I'll side with Mozilla and ignore the Asshole Coward: "Q: Will this be yet another platform for developers to code for?

      "A: No; the project is extending what developers can do with the Web, especially in the context of mobile devices, and to do so in a way that leads to interoperable standards. Just as with HTML5, ES5, CSS3 and other Web technology it will reach different browsers and operating systems at different times, but the pace of Web platform development gives us confidence that good Web technology can reach a lot of people pretty quickly.

      "We don't want this work to lead to applications that only run atop one platform, or only run in Firefox. That's an important difference between what we're doing and proprietary mobile stacks today: we don't seek a competitive advantage for Mozilla, we seek a competitive advantage for the Web." http://www.mozilla.org/en-US/b2g/

      --
      My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
    6. Re:No, it won't by multipartmixed · · Score: 1

      Google "boot to gecko"

      --

      Do daemons dream of electric sleep()?
    7. Re:No, it won't by Darkness404 · · Score: 2

      Mozilla will keep on staying afloat so long as its competitors suck, which, at the time being, they do.

      Their main competition right now is Chrome which offers users next to no customization. Opera is still... Opera. And IE, well, is getting better but isn't anywhere near as functional as Firefox/Chrome/Opera.

      --
      Taxation is legalized theft, no more, no less.
    8. Re:No, it won't by Anonymous Coward · · Score: 0

      Well, you're not quite reading carefully enough.

      Firefox OS *is* an operating system: "What is Boot to Gecko? Boot to Gecko (B2G) is a project with the goal of building a complete, standalone *operating system* for the Web" - https://wiki.mozilla.org/B2G/FAQ

      Firefox OS is the operating system, the Web is the *platform*. i.e. Open Wab Apps (hopefully) won't just run on Firefox OS, they'll run anywhere.

      So, yes, Firefox OS replaces Android and iOS on the phone. But OWAs won't only run on FirefoxOS (if the other vendors implement the WebAPIs).

      Happy?

    9. Re:No, it won't by Lennie · · Score: 1

      A lot of apps on iOS and Android are already built with HTML5. Making them available on Firefox OS should their for be easy.

      I think that is what Mozilla is saying.

      --
      New things are always on the horizon
    10. Re:No, it won't by Anonymous Coward · · Score: 0

      There's a difference between swimming to catch up with a moving boat and swimming to meet a boat under anchor.

    11. Re:No, it won't by curunir · · Score: 2

      Sounds like WebOS...developers wrote WebOS apps in HTML/JavaScript too. By all accounts I've heard, the software was excellent and peopled loved the OS. Yet it didn't exactly take over the mobile market or even "win big." I wish Mozilla the best of luck with trying the same play ~3 years later, but I'm not betting one red cent on them (or wasting any of my time developing apps for their OS.)

      --
      "Don't blame me, I voted for Kodos!"
    12. Re:No, it won't by LiENUS · · Score: 1
      You should try the wiki's FAQ https://wiki.mozilla.org/B2G/FAQ

      What is Boot to Gecko? Boot to Gecko (B2G) is a project with the goal of building a complete, standalone operating system for the Web. It is not a product offering yet, but we are working on transforming it into one.

      Mozilla is explicitly saying the same thing the anonymous coward is saying.

    13. Re:No, it won't by DuckDodgers · · Score: 2

      A few counters to that:

      1. When WebOS launched it was proprietary, so despite the HTML5 and Javascript support it grabbed none of the geek market that went to Android because of its open source roots. Firefox OS is, of course open source.
      2. WebOS was only available on HP products. Anyone can sell Firefox OS devices.
      3. HP dropped WebOS before it had a chance to establish itself. In the US market, WebOS phones were only available on Sprint, a second-tier wireless carrier in much of the country. It remains to be seen what carriers, if any, offer Firefox OS phones in the US.
      4. The WebOS phones in 2009 had acceptable hardware for the time, but with 256 MB of RAM and a single 600 MHz ARM chip browser performance was noticeably worse than on a half decent laptop. By the time Firefox OS devices are in stores, they'll probably be on phones with dual core 1.0 GHz processors or better, with 1 GB of RAM, and between that and the performance improvements in Firefox (check the Browser Grand Prix comparison's at Tom's Hardware - Firefox has gone from awful to awesome over the last year and a half), the browsing experience should be great.
      5. Mobile websites have increased in number tremendously since 2009, and there are a lot more iOS and Android apps that are partly or totally written in HTML5. That's something WebOS could not use, and Firefox OS can.

      Last but not least, Android may start losing support from some manufacturers. Samsung and Motorola own most of the Android market and most of the Android profits, at least in the US. This may be a way for HTC, LG, Huawei, etc... to differentiate themselves from Apple, Samsung, and Motorola without paying any licensing fees in the process.


      Frankly I still think it's doomed to putter and fail, but I'm still foolishly optimistic.

    14. Re:No, it won't by Anonymous Coward · · Score: 0

      personally, i'm not going to learn a programming language like java or objective c just because android or IOS are popular. Maybe i'm a voice out of the chore but when i choose the platform to develop i look for flexibility and openness, not popularity, otherwise platforms like linux would not even exist...

    15. Re:No, it won't by hairyfeet · · Score: 1

      That is the ironic thing about how it and WebOS and even WinPhone aren't going anywhere, because for all his talk of "developers developers' MSFT missed the boat and they all went to iOS and Android and Moz is even later than both MSFT and HP to the party but with even less money to throw at marketing and R&D.

      We've seen time and time again the masses don't care about "free as in freedom' all they care about is the apps and the buzz, and that's all Android and iOS. Finally without the carriers offering cheap phones Moz won't go anywhere as most won't pay $600+ for a smartphone when they can get the phone for $99 on a contract, yet i just don't see the carriers getting all warm and fuzzy for a hacker friendly phone.

      Yeah...not gonna happen. I have a feeling if they get any phones they'll end up with the touchpads and winPhones on Woot! or some other wholesaler site for 95% off, its just not gonna be able to build any steam.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    16. Re:No, it won't by hairyfeet · · Score: 1

      Here is some points for you. 1.-Openmoko. geeks may talk a good game, but spending $600+ on unsubsidized smartphones? Not happening. 2.-The carriers sure as hell ain't gonna go "What? A GPL phone where we can't cripple it, lock it down, and then sell features the phone already has at higher prices? Where do we sign up?" so you can give up having these phones offered for anything less than full price. 3.-If they simply wanted to be different they could simply slap WebOS on, but its not the OS, its the apps. 4.-So far what I've seen of HTML V5 sucks the big wet titty. for every one site you seen done right you get 50 done wrong, with video that skips like mad and "apps' that are glitchy messes. i don't see this making anyone want to give up their Android market or Apple appstore, finally 5.- MSFT is spending $450 to sell a $50 phone and still can't catch a break, you think Moz is gonna do better in an already crowded and saturated market?

      If this would have came out 5 years ago maybe, but now? Its gonna take Apple or Google doing something seriously stupid to create an opening and with Google sinking a billion a year in Android development and who knows what Apple is sinking into R&D and marketing the odds of this working is about the same as me winning the powerball. Every major shift we've seen in mobile has been because someone seriously fucked up, Palm sat on ass and let their OS and hardware get creaky and by the time they saw the train coming it ran them over, RIM sat on ass and let their designs stagnate and refused to look at other markets until the bus that was consumer markets ran them over, HP as you pointed out didn't know WTF it was doing and after spending a shitload on WebOS had no damned clue what to do with it, and MSFT treated phones as itty bitty desktops for a decade and by the time they realized that UI didn't work on a 3 inch screen they were fucked.

      Moz simply doesn't have the luxury of retarded competition, in fact just the opposite because while you can say a lot of things about Apple and Google stupid and lazy they are not. They have carved the market nicely, with Apple taking all the high margin high end while Google takes the low and both have devs lined up to write apps for them. A glorified web page simply isn't gonna replace native apps and certainly isn't gonna net devs the kind of money they are making from the market and the appstores and surprise surprise but devs actually want to get paid. The devs and the apps will stay where they are, a few CCC Chinamart devices may carry this but I doubt you'll see any big names, and it'll go the way of WebOS and OpenMoko.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    17. Re:No, it won't by Anonymous Coward · · Score: 0

      The reason I wont consider it is because the browser has long had issues with memory leaks and bloat, despite the developers repeatedly putting their hands over their ears, closing their eyes and screaming "there are no memory leaks!". I'll admit it's definitely better now than say a year ago, but it's still got some way to go.

      If they can't even get a browser right, why would I trust them with an OS?

      I think Mozilla need to go back to basics and sort out their fundamentally poor development strategy before they start embarking on projects like this.

      I'm sure people will tell me I'm wrong, and that Firefox is awesome, but there is a reason why Firefox has been losing marketshare to Chrome, and it's not simply because I as an individual am unhappy with Firefox nowadays - it's because most people who used it are.

    18. Re:No, it won't by MachineShedFred · · Score: 1

      Making a browser for existing content has a much smaller barrier to adoption than making an OS which has exactly zero applications, when the two prime competitors have hundreds of thousands available, and more being added every day.

      Ask RIM how it worked out for them, and they already had a user base. Ask Microsoft how Phone 7 is doing as a development ecosystem.

      Firefox OS will have to bring something spectacularly compelling to the market, or it won't even see 1% adoption.

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    19. Re:No, it won't by DuckDodgers · · Score: 1

      I think your arguments carry more weight than mine and Firefox OS will occupy a very tiny niche. But I have a few admittedly weak responses.

      1. Hardware is better now and continues to improve. I wasn't a fan of OpenMoko's hardware specs, so I'm not one of the ones that failed to match talk with cash. I wasn't interested in any smart phone until they reached dual core and 1 GB of RAM, and I probably won't replace my junky bottom tier LG Android phone until a generation or two past the Galaxy Nexus 3. Maybe OpenMoko's biggest problem was being before its time.

      2. The Linux kernel in Firefox OS is GPL, but Firefox itself is under the Mozilla Public License, which is kind of like a weak GPL because it protects the openness of its own code but makes no restrictions on intermingled proprietary code. The carriers can add their own proprietary features to the phone and remove features from the operating system so they can screw the customers with value add junk. They are legally required to give the customers copies of the Firefox OS source that they did not modify, but not their own code.

      3. (Re WebOS instead) good point.

      4. HTML5 app selections are improving all of the time, because you can run apps in it on Windows, on Mac OS X, on iOS, on Android, etc... and part of the Firefox OS project is releasing new HTML APIs for accelerometers, VOIP, etc... if they can get the major players to adapt those APIs, HTML5 will be even more cross-platform compatible.

      5. Microsoft charges licensing fees, they have a relatively poor reputation with many consumers, and they screwed themselves by burning all of their early adopters by making Windows Mobile apps incompatible with Windows Phone 7 apps.


      5 years ago no mobile phone had the memory and processing power to make HTML5 websites run well and the HTML5 app selection sucked hugely. This could have never worked then. It probably won't work now, but this is the best window of opportunity Mozilla will get.

    20. Re:No, it won't by hairyfeet · · Score: 1

      The only things I would counter with is 1.-I wasn't bringing up OpenMoko to talk about the device specifically, but to point out that while geeks TALK a good game, when it comes to investing hundreds of their own money they quietly walk away. Look up the buzz around OpenMoko before release and it was HUGE, geeks talking it up like it was an iJesus but when it came out and they saw the price it was "Where did everyone go?" and that was that. 2.-And while the carriers MAY be able to do that there is also the possibility of both they and Moz getting sued if so much as a single line of code in MozOS can be traced back to GPL V3. Why would any carrier take the risk and possible bad publicity when Android is free and already has the devs? And finally 4.-I'm sorry but so far I haven't seen many HTML V5 apps that haven't sucked balls. the toolset simply isn't mature and its more of a PITA. I have noticed that while even an 8 year old desktop can run native apps well that same machine will struggle with HTML V5 and that's plugged into a main, the mobile suck even more. Native apps use less battery and when you are talking about iSliver designs being the hip thing that matters. Oh and 5.-MSFT had a mature toolset and was practically the only game in town around 04-07 and nobody bought them because the UI sucked. There is nothing wrong with the UI on iOS and Android and on both they have a mature toolset and easy to use dev tools which just don't exist for HTML V5.

      So while I can see where you are coming from, and I apologize about never figuring out how to make a straight list here, i just don't see it happening. Humans are basically lazy creatures and devs are humans and it'll simply be easier to stick with what they already know and more importantly where they already have an easy way to make native apps. being able to run on different platforms doesn't really matter if the money isn't there and the only markets we see making any money are Android market and the Appstore. You certainly aren't seeing anyone push HTML V5 apps on the desktops, and in fact both Google and Apple have downplayed HTML V5 since setting up their appstores. Again when you have network effects in play the other guy has to do something stupid, like MSFT did when it disbanded the IE team and left IE 6 to rot thus giving Moz a free shot at the desktop but I just don't see that happening here, neither Apple nor Google are gonna make any blatant mistakes any time soon.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    21. Re:No, it won't by DuckDodgers · · Score: 1

      With the lists you have to use the HTML formatting, so it's "less than" "br" "forward slash(optional)" "greater than" (all without the double quotes) . The br is literal, the rest are their respective characters on the key board. But don't sweat it, your stuff is easy to read.

      Apple and Google are caught in a tug of war over HTML5 - if they support it well, it makes it easier for customers to move to the other guy. But if they support it too poorly, they miss out on developers and they miss out on the good apps for HTML5 that do exists. But at the end of the day I suspect you're right, Apple and Google are going to pour all their money into making the native apps better because locking the customers in gets them more money.

      I'm just hoping something disrupts the situation. Competition is good for everyone, and while I'm thrilled that Android is mostly open and we're not stuck choosing between two completely proprietary options, I would still like to see three major players or four major players, and ideally everyone but Apple would be mostly or fully based on free software.

    22. Re:No, it won't by Anonymous Coward · · Score: 0

      I have an anonymous coward saying one thing, and Mozilla saying the exact same thing.

      FTFY

      I think I'll side with Mozilla and ignore the Asshole Coward

      I don't think you actually know what the word "asshole" means. If you did, you wouldn't have called the above AC an asshole. They were not rude to you in any way, they were simply politely correcting a misunderstanding that you had. If anyone is the asshole here, it's you.

    23. Re:No, it won't by Anonymous Coward · · Score: 1

      "I think they were told the same thing about developing a browser when internet explorer owned the market."

      Exactly!

      For the record, I'm the person who answered the questions from the reporter. I am not (anymore) the "head of Mozilla Europe", even if I founded Mozilla Europe back in 2003. I'm replying here as an individual, not pretending to represent Mozilla in any way.

      Anyway... Yes, Firefox OS is audacious. We know that. We're known for doing crazy things. We're a not-for-profit.

      The thing is that when I look at iOS, I see a great product which is closed, with a monopolistic AppStore that enables censorship (see http://en.wikipedia.org/wiki/Approval_of_iOS_apps#Notable_rejected_apps ). When I look at Android, I see a product which is half-way open, developed by Google Engineers, and which apps are closed source. In both cases, you have to develop your mobile app for each stack (unless you write it in HTML5 and use a wrapper to make it look like an app, which more and more people do nowadays).

      I'm a citizen of the Internet. I want things to be Open. I want kids to be able to develop Mobile apps. I want to be able to views source and understand how things work under the hood. I'm OK paying for an app, because I prefer that to paying a developer with priceless personal data.

      So I'm very excited by Firefox OS' approach of having every app running on my mobile to be a HTML5 app. Including the Home Screen, the Dialer, and the Text message app.

      See? http://www.flickr.com/photos/nitot/6935638349/ This is a Web App. You can view the source: http://www.flickr.com/photos/nitot/6789526956/

      I'm excited by this approach. You may want to know why I think Mozilla has a chance to succeed where some big players have failed? We're leveraging the Web, which has a huge number of developers. We're not trying to build our own proprietary platform, and I think this is game changing.

      And I suspect many Slashdot readers are going to be excited when they understand the goal and the approach. It may take some time :-)

      --Tristan Nitot
      Personal blog: http://standblog.org/
      Mozilla blog: http://blog.mozilla.org/beyond-the-code/

    24. Re:No, it won't by nitot · · Score: 1

      Ah! Next time, I'll log in before posting :-/

      --Tristan Nitot

    25. Re:No, it won't by hairyfeet · · Score: 1

      While I agree that I'd LIKE to see something else, hell I'd like it if you had WinPhone AND Android AND iPhone AND WebOS Phone AND MozOS Phone what we end up talking about is a classic variation of the centuries old "is ought problem" where you and I end up talking about what OUGHT to be instead of what IS

      Believe me I know all about the is ought problem because as a PC retailer I've stressed for years that what people OUGHT to do is buy or have me build them a nice desktop and then buy a much lower end mobile like a netbook because frankly mobiles will ALWAYS be slower, easier to break and wear out, and you'll always pay more and get less because its designed with batteries instead of mains in mind. What IS reality is people end up having me find them a laptop that then spends a good 90%+ of its life sitting on a desk plugged into mains so that when they DO ever go out the battery has worn down from constant trickle charging. why do they do it? because people like the IDEA of being "always on the go" even when they aren't, no different than how I bet 75%+ of exercise gear sold ends up in a garage never being used.

      And while Google and Apple are indeed in a war over HTML V5 it isn't about apps, its about controlling the web. Google wants to make sure HTML V5 does what Google wants it to do, so that Google docs and GMail run fast, whereas Apple wants it to cut out flash which competed with the appstore. In the end I doubt seriously that either will do much as far as HTML V5 apps, especially when it comes to mobile, because they are making a killing on their appstores. It would be like Valve promoting GoG over Steam, they are simply not gonna give up their cut even though it would make things more open and even easier for the buyers.

      I've been here since the days of win 3.x friend and i know the desire, I've been waiting for damned near 20 fricking years for a true "write once, run everywhere" format but it won't be HTML V5 because the companies in control of it make more money if HTML V5 isn't as good as native. In the end the companies will do what makes them the most money and gives them the most lock in, and that's native apps. While this sucks for the devs and the users the big two make out like Gods by having centralized control of their markets, and frankly they have the money and the pull to make sure HTML V5 is always an also ran.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    26. Re:No, it won't by DuckDodgers · · Score: 1

      Google has slightly more interest in promoting HTML5 than Apple - the Chrome browser has its own app store, and Google has Chrome OS. But of course in terms of engineering investment neither the browser nor the operating system receive anywhere near the attention or promotion that is given to Android.

    27. Re:No, it won't by hairyfeet · · Score: 1

      I know all about it, comodo dragon is a spinoff of Chrome and has access to the appstore, but what are the numbers? I've looked and not been able to find any, which tells me the amount they are making off the Chrome Store is probably piddling.

      And let us not forget the word of the day is lock in, both Apple and Google have been making out like bandits on their appstores and when it comes right down to it they are certainly not gonna create the tech that is gonna take those markets away. In the end I think both are gonna make HTML V5 just powerful enough to accomplish their goals, killing flash for Apple and speeding up Google docs and Gmail for Google, while making sure that any app that has both HTML V5 and native will always run better native.

      Frankly I don't see how HTML anything could compete with native anyway, lets face it JavaScript was never designed to be power conscience and in mobile battery is king. With native they can design the APIs with power usage in mind whereas it really doesn't take much for JavaScript to pound a CPU, not to mention the toolsets for HTML V5 simply aren't very mature and from what I've seen none of them are really designed for creating lightweight mobile friendly code so much as pouring on the bling.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    28. Re:No, it won't by DuckDodgers · · Score: 1

      I'll give you the fact that toolset maturity is a big problem.

      But even with tons of native apps, mobile operating systems are still going to have a huge web browser focus. So Microsoft, Mozilla, Google, Apple, Opera, and dozens of other minor players will continue to invest resources well into the tens of millions of dollars per year range into making Javascript and HTML more resource efficient, and the browser itself more power efficient. Between that kind of optimization on the software side and the march of technological innovation on the device side, I really suspect you'll be able to run the graphical equivalent of Unreal 4 using WebGL on your smart phone in ten or fifteen years.

  4. Xul was fun but yeah its dead by detain · · Score: 1

    XUL was lots of fun to work with. There was some pretty easy to develop with tools out there for quickly designing interfaces, but then the javascript still took forever and was a pain to work with. Things like Jquery have made pretty HTML interfaces easy to produce and its definitly going to be the way to go over XUL. RIP XUL

    --
    http://interserver.net/
    1. Re:Xul was fun but yeah its dead by Anonymous Coward · · Score: 0

      XUL = AOL's answer to VisualBasic

    2. Re:Xul was fun but yeah its dead by Anonymous Coward · · Score: 0

      What on earth does XUL have to do with FirefoxOS?

    3. Re:Xul was fun but yeah its dead by Tarlus · · Score: 1

      RTFA

      --
      /* No Comment */
    4. Re:Xul was fun but yeah its dead by msclrhd · · Score: 1

      Or even RTF summary,

  5. phones? idk...but a cheap tablet for schools... by malelder · · Score: 4, Interesting

    while I'm not sold on the idea that we need another phone OS, I would think the combination of a cheap tablet with an HTML5 based OS on it is a decent alternative to laptops and netbooks for elementary education purposes. Books, interactive exercises, and word-processing abilities all in one. Allow a school to run their own Google Office-style server to keep things local...could be neat (:

    --


    Yuma, AZ...You will never find a more wretched hive of scum and villainy. We must be cautious.
    1. Re:phones? idk...but a cheap tablet for schools... by Anonymous Coward · · Score: 1

      You might be right about the need for a cheap computing device for education. Although I think it's more in the applications being written from the ground up on a modern device moreso than anything else. Not so much the implimentation (except where it applies to making the technology underneath less relevent and HTML5 does that).

      What this potential does though is give us a more usable freedom friendly phone. The problem is the phones themselves will probably not be all that truly freedom friendly. Thye need manufacturers to design phones using chipsets that have free software driverss/specifications/firmware available. This isn't possible to the fullest extent. The modem won't be freedom friendly with the current rules governing GSM. Although there may be a way to abstract it and still make it freedom friendly to a degree.

      There is also the fact phones today are spying on us. This is partially due to the modems although a proper design can fix this to a degree.

      What we need is a reciever-only chip that does not require the modem to be on. All this chip would do is listen for incoming calls. When a call was detected for the phone it would turn the modem on (upon the user accepting the call). The phone thus could not be used as a tracking device anymore than a payphone could be that was combined with voice detection (to identify callers) technology. Taking this a step further you would integrate VoIP (SIP) and set the modem to be data only. Thus calls going out wouldn't be attached to the provider. You could then pass the SIP through something like Tor. Tor itself would probably not work except that any phone company which sold enough units could probably fund such a project with sufficent dollars that enough servers were setup to handle the call volume (and therefore the idea could work).

    2. Re:phones? idk...but a cheap tablet for schools... by Anonymous Coward · · Score: 0

      We dont need another smartphone OS, we need only one.

      Why?

      Because Steve Said So.

    3. Re:phones? idk...but a cheap tablet for schools... by cpu6502 · · Score: 2, Informative

      >>>while I'm not sold on the idea that we need another phone OS

      A lot of people seem to think Mozilla is trying to replace or compete with iOS and Android. Not the case. QUOTE: "The Firefox OS for mobile devices is built on Mozillaâ(TM)s 'Boot to Gecko project' which unlocks many of the current limitations of web development on mobile, allowing HTML5 applications to access the underlying capabilities of a phone, previously only available to native applications..... Due to the optimization of the platform for entry-level smartphones and the removal of unnecessary middleware layers, mobile operators will have the ability to offer richer experiences at a range of price points including at the low end of the smartphone price range, helping to drive adoption across developing markets."

      "We believe the Web is the platform. Ideally, the technology pioneered or refined in the Boot to Gecko project will make its way into all mobile browsers, so that enhanced Web applications can be great regardless of operating system or device...... This is not going to be yet another platform for developers to code for. The project is extending what developers can do with the Web, especially in the context of mobile devices, and to do so in a way that leads to interoperable standards.

      "Just as with HTML5, ES5, CSS3 and other Web technology it will reach different browsers and operating systems at different times, but the pace of Web platform development gives us confidence that good Web technology can reach a lot of people pretty quickly. We donâ(TM)t want this work to lead to applications that only run atop one platform, or only run in Firefox. Thatâ(TM)s an important difference between what weâ(TM)re doing and proprietary mobile stacks today: we donâ(TM)t seek a competitive advantage for Mozilla, we seek a competitive advantage for the Web."

      http://www.mozilla.org/en-US/b2g/

      --
      My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
    4. Re:phones? idk...but a cheap tablet for schools... by westlake · · Score: 1

      I would think the combination of a cheap tablet with an HTML5 based OS on it is a decent alternative to laptops and netbooks for elementary education purposes.

      How many times have we been down this road only to see it dead-end?

      Grading the Digital School ---- In Classroom of Future, Stagnant Scores

    5. Re:phones? idk...but a cheap tablet for schools... by Randle_Revar · · Score: 1

      Wow, really? Then they shouldn't have called it "Boot to Gecko" or "Firefox OS", then.

    6. Re:phones? idk...but a cheap tablet for schools... by LiENUS · · Score: 2
      Try the FAQ https://wiki.mozilla.org/B2G/FAQ

      What is Boot to Gecko? Boot to Gecko (B2G) is a project with the goal of building a complete, standalone operating system for the Web. It is not a product offering yet, but we are working on transforming it into one.

    7. Re:phones? idk...but a cheap tablet for schools... by antifoidulus · · Score: 2

      "We believe the Web is the platform. Ideally, the technology pioneered or refined in the Boot to Gecko project will make its way into all mobile browsers, so that enhanced Web applications can be great regardless of operating system or device...... This is not going to be yet another platform for developers to code for. The project is extending what developers can do with the Web, especially in the context of mobile devices, and to do so in a way that leads to interoperable standards.

      The web may be the standard, but the "web" does not necessarily imply HTML(5). HTML5 is merely the V part of the MVC model, many applications that run on iOS, Android, and the web use "the web" on all those devices(basically using JSON over HTTP as the controller) even if they don't use a single line of HTML. What the mobile HTML5 evangelists have yet to prove is that writing HTML 5 for every device out there is easier, faster, and better than writing a native view for the two main platforms. They keep on saying that HTML5 can be "universal", but really have yet to prove it in any non-trivial sense.

    8. Re:phones? idk...but a cheap tablet for schools... by Anonymous Coward · · Score: 0

      What the mobile HTML5 evangelists have yet to prove is that writing HTML 5 for every device out there is easier, faster, and better than writing a native view for the two main platforms.

      So basically, you're waiting for mobile HTML5 evangelists to prove that supporting all mobile devices with a HTML5-compliant web browser is easier/faster/better than supporting only two mobile devices. I wouldn't hold your breath if I were you.

    9. Re:phones? idk...but a cheap tablet for schools... by justforgetme · · Score: 1

      Yep! Plus the infinite opennes of HTML based tech means that every kid that wants to find out how it works will be able to mess with the source ind instantly get feedback on what it does.

      Like everybody does with the gnome3 notification system!

      I just hope they also provide decent reflashability for the OS files...

      --
      -- no sig today
  6. Best of luck (seriously) by Qwavel · · Score: 4, Interesting

    It is going to be really tough for Mozilla to make headway with their own mobile OS. Palm, Nokia, RIM, etc. have all failed in spite of enormous efforts, and the only ones that have succeeded now have complete ecosystems built around their devices.

    So, I believe that the chances of Firefox OS succeeding are really slim.

    And this is coming from someone who believes that Mozilla saved the Web, and who runs firefox on their phone (which is part of the problem - I already have mobile firefox).

    1. Re:Best of luck (seriously) by Microlith · · Score: 4, Interesting

      Palm

      Carrier manhandling (never trust those bastards) and getting snapped up by HP were the biggest contributors to their fall.

      Nokia, RIM

      Unrepentant managerial incompetence. Hell, Nokia had a winner in the N9 but their internal practices kept it from seeing the light of day early enough to actually be of use.

      the only ones that have succeeded now have complete ecosystems built around their devices.

      But the presence of those "ecosystems" does not preclude competitors. Nor do they mean that no one else should try. This is probably the worst argument I've seen, if anything it gives even more reason to hate ecosystems as they seem more adept at inhibiting competition and user choice than anything else.

      I believe that the chances of Firefox OS succeeding are really slim.

      Depends on the market they go into. Success doesn't mean that they drastically displace iOS or Android, only that sales of devices running the platform are profitable. Profitability means that there's opportunity to grow.

      On top of that, if you focus on regions using GSM that don't have their handset choices constrained by the regional carriers you have a far better chance than in backwards markets like the US.

    2. Re:Best of luck (seriously) by Karlt1 · · Score: 1

      Handset sales are already unprofitable for anyone but Apple and Samsung. What does Fitefix bring to the table?

    3. Re:Best of luck (seriously) by Anonymous Coward · · Score: 0

      People said this about Google when they launched their mobile platform, but it has survived.

    4. Re:Best of luck (seriously) by Anonymous Coward · · Score: 0

      You blasphemer! Don't you know that they are the one true? They annointed? The Blessed? Damn be to the heathens who like complacent conformity to stability and usability!

    5. Re:Best of luck (seriously) by Anonymous Coward · · Score: 0

      That's because it had big players backing it whereas FirefoxOS has a couple of small regional telecoms.

    6. Re:Best of luck (seriously) by anon+mouse-cow-aard · · Score: 1

      uh... not caring if it is profitable? Support from all the carriers who feel that the use of their network entitles them to a share of the app store pie, after seeing their potted plants (weren't big enough to get to walled garden status) wre not compelling, they can see that if they work together, perhaps they will share more of the pie than Apple or Google do.

    7. Re:Best of luck (seriously) by Anonymous Coward · · Score: 0

      Telephonica is not a "small regional telecom", they're huge.

    8. Re:Best of luck (seriously) by Patch86 · · Score: 1

      They're also backed by phone maker Alcatel- who are bigger in terms of Revenue than either HTC or Motorola Mobility.

    9. Re:Best of luck (seriously) by unixisc · · Score: 1

      What OS is this Mozilla OS? Yet another Linux distro? Or something else altogether? And if it is based on something in th cloud, or web browser, or vm, why should I care?

    10. Re:Best of luck (seriously) by Anonymous Coward · · Score: 0

      It's based on the Linux kernel + drivers from the Android open-source project. On top of that they have Gecko, the rendering engine in Firefox. Everything else is written in HTML5, and runs on the device (offline storage)

    11. Re:Best of luck (seriously) by Anonymous Coward · · Score: 0

      This is a little mysterious. It sounds very much like Firefox's answer to ChromeOS. But really, who's asking that question? Particularly on the phone.

      As for HTML5, I'm sure that's an increasingly viable target for many simpler mobile apps. But that's supposed to be based on HTML5, standard everywhere (well, when they finally finish it and all mobile browsers conform -- that usual bit of reality that gets in the way of our fun). So it's not clear what they're bringing to the party with this "spreading across all browsers", that isn't already spreading across all browsers thanks to so many folks already pushing HTML5 (though, I think, mostly because they're angry about Adobe Flash for various reasons: the FOSS community because it's closed source, Apple because it enables paid, DRMed content they can't charge for, etc).

    12. Re:Best of luck (seriously) by Karlt1 · · Score: 1

      Okay,

      So the carriers start "supporting" Firefox. The carriers don't make phones. So....

      1. How do you make it profitable for the phone manufacturers to manufacturer phone using it? They can already get Android for free, so what is it in for them?

      2. If none of the phone manufacturers (besides Samsung) can profitably sale Android phones, how does Firefox change the equation?

      3. Haven't we been down the road with "just create HTML apps" before with Apple, Palm, Microsoft, and Rim (BB OS 10 on the playbook). Developers always complain. Heck, developers who want performance complained about being forced to run under VM (Android/Dalvik, Microsoft/CLR)

      And finally......

      4. If Mozilla doesn't allow native apps, how will other browser makers be able to port their browsers? Isn't that what Mozilla was complaining about with Windows 8 RT?

    13. Re:Best of luck (seriously) by anon+mouse-cow-aard · · Score: 1
      bellcos can load custom firmware on the phones. The customization can be very slight, as in.. use the bellco's app shop for firefoxOS apps. Bellco takes a cut of each purchase, and provides ''support'' for the devices. if the firmware is modified, they don't support. so you have to use their app store. If they are smart, they hook it up so that it recurses to app vendor storelets, or a clearinghouse run by mozilla. App vendors only make their apps for one store and bellco's import from there and agree to pay charge a percentage on top of a wholesale price. Everybody happy. Bellco much happier than with Android & iPhone... whose stores they get 0 revenue for.

      So bellco's just use contract manufacturers and make vanity models. the contract manufacturer neither knows nor cares about the software, QA is by the bellcos. Bellcos support their own widgets. If bellcos want to keep costs down, or there are smart widget makers, they all agree on models and buy the same model in higher volume... and have the branding stay with the manufacturer so that commercials work in any country... but the model is that the bell cos do very light branding/app store redirecting to the firmware, so that the phone stays "theirs." Rather than google using phones as a loss leader for ad revenue, the bellcos adopt the apple model and use phones as a loss leader for the app stores. It will only work if they keep the OS compatible so that there a many vendors out there and critical mass for app developers to target. Otherwise, it will be just like the walled gardens of smart phones of yesteryear...

  7. And WebOS failed because? by mystikkman · · Score: 3, Informative

    WebOS also promised that you can write apps in HTML/JS and look at what happened to the Touchpad when it took on the iPad.

    Developers flock to the platforms with most users, ease of development is only a small factor because the alternatives like iOS, Android and WP have reasonable dev environments. If the market was owned by Blackberry, he would have a point, since it's just TERRIBLE for development.

  8. There's room for a #3 mobile OS by GodfatherofSoul · · Score: 2

    iOS and Android have big enough flaws that if another group finds that magic bullet, they can win big. The design problem is they have to come at from the approach of competing against and with the big boys and not just making a mobile OS that works. There are plenty of failed OS projects out already that "work."

    --
    I swear to God...I swear to God! That is NOT how you treat your human!
    1. Re:There's room for a #3 mobile OS by erroneus · · Score: 2

      I'm not so sure about that.

      The market is more or less settled. The things that have won the users over are positives and there's not so many negatives that users will want to change. Even if developers absolutely love developing for FirefoxOS, there won't likely be a market for it. FirefoxOS is about 4 years late to the party.

      On the other hand, if FirefoxOS can be a replacement for Android while using all of the same hardware drivers of Android, there might be a chance it could exist as a geek-elite/hacker's OS which might find its way into devices which phone makers might experiment with.

      And it won't matter how good it is or will be. That's not how the market works.

    2. Re:There's room for a #3 mobile OS by ChunderDownunder · · Score: 1

      Even if developers absolutely love developing for FirefoxOS, there won't likely be a market for it.

      There's very little 'developing for' going on here. These are standard web pages. Written in HTML and JS. The same web page that will run on your desktop browser. All that changes is skinning for a smaller screen.

      Any 'native' functionality is called by invoking a library built into the JavaScript engine. All of these libraries are slated for submission to the web standards authority, W3C.

      I think it's important to recognise the goals of the Mozilla project and hence the overall goals of Firefox OS. Mozilla isn't a commercial venture in the traditional sense. Netscape crashed and burnt. What remains is one of the larger open source hacker cultures whose mission is to advance the web.

      Firefox OS exists because the existing developers of Firefox decided it would be fun. Any 'market' gained by this venture will see revenue channeled back into development. The coders keep receiving paychecks for writing open source.

      When these WebAPI modules trickle into webkit and Android, mission accomplished. Developers will then be able to target mobile devices with full functionality using standard web technologies.

      Any commercial risk of establishing a market to compete with Android and iPhone is outside the Mozilla organisation. A telco is putting up the cash.

  9. Personally I see that as a step backwards. by Anonymous Coward · · Score: 0

    XUL is actually really nicely done. Much better than that mess HTML5, that is for sure.
    XUL is one of the better things Mozilla have made. This saddens me more.

    I was hoping it would get adopted as menu interfaces for web apps in the now-future, but it never did.
    If only they pushed it a little harder.

    RIP XUL. RIP.

  10. Hope they enjoy shitty performance by Anonymous Coward · · Score: 4, Insightful

    HTML5, while faster than previous incarnations of HTML+JS, is still massively slower than native applications. I predict a very sluggish experience.

    1. Re:Hope they enjoy shitty performance by Anonymous Coward · · Score: 0

      When web workers are sorted out, things will surely get better.
      Those things are pretty damn nice and allow for such a massive performance increase instead of the main thread getting clogged up.
      And in particular, this is going to be brilliant for games. I've already tested it out on even a small thing and it goes stupidly faster.

      The main problem right now is child and shared workers. They are a little dodgy at the moment.
      But the current bog standard one works right now.

      The annoying part about workers, however, is you can't send DOM data. The moment you do, 10 kinds of heart attack.
      Of course, with a well structured system, you wouldn't end up with this annoyance.
      I think there was some thing recently going on about testing out a new feature for making the moving of data between worker and main trivial, so cannot wait for that.

      I still think we need some compiled support, though.
      Something similar to Native Client but it allows direct communication with the page. So sort of like a sandboxed plugin system that is pretty seamless.
      If that can happen, things will really get better. That is the best of both worlds, the ultimate goal.
      Unless some major breakthrough happens that allows near-native speeds in interpreters, this would need to happen for ultimate efficiency.

    2. Re:Hope they enjoy shitty performance by Anonymous Coward · · Score: 0

      And yet your web workers go stupidly slower than my native application using threading and native vector OPs of the CPU.

    3. Re:Hope they enjoy shitty performance by Just+Some+Guy · · Score: 1

      HTML5, while faster than previous incarnations of HTML+JS

      That makes no sense whatsoever, and is analogous to saying that .docx is faster than RTF.

      --
      Dewey, what part of this looks like authorities should be involved?
  11. 75 Percent by Fallingcow · · Score: 3, Insightful

    75 percent of apps are already written in HTML5

    OK, maybe. But what percentage of good apps are written in HTML5?

    1. Re:75 Percent by goruka · · Score: 3, Insightful

      Exactly my thoughts. To be more specific, writing non-retardedly simple games is a feat with html5 due to slow performance and huge memory consumption.
      Even in Android Java is often bypassed in favor of NDK for complex projects and portability reasons, where you want to use C/C++ or your own, more fittin, scripting language such as Lua or Python.
      Mozilla developers seem to have very strong ideals of a world where the only programming language is HTML5 and the only platform is the web, and I remember there was a lot of hype about that philosophy a few years ago, but app stores with native apps have clearly shown the future is somewhere else. Even Google has aknolwedged that in Chrome by allowing Native Client..

    2. Re:75 Percent by Anonymous Coward · · Score: 1

      Mozilla developers seem to have very strong ideals of a world where the only programming language is HTML5 and the only platform is the web

      When all you have is a hammer, your ideal world tends to include a lot of nails.

    3. Re:75 Percent by oakgrove · · Score: 1

      My take on it is pretty similar. Right tool for the right job and all. It's pretty easy to write HTML5 apps for Android and iOS there are even pretty good frameworks for it like Titanium and Phonegap. The fact remains that most apps you find in either of those app stores that are written with a webview tend to get the lowest ratings. Scrolling doesn't work as well, they lack depth and complexity, etc. Unless Mozilla can fix these issues on their platform they are going to be in for some disappointment I'm afraid. I still wish them the best of luck in their endeavor.

      --
      The soylentnews experiment has been a dismal failure.
    4. Re:75 Percent by Ash-Fox · · Score: 1

      It's pretty easy to write HTML5 apps for Android and iOS there are even pretty good frameworks for it like Titanium and Phonegap.

      Phonegap is in my opinion horrible. It doesn't even have socket APIs and the HTML5 socket support doesn't work. It does less than Borland's Pascal does - To have a new dev framework/environment capable of doing less that Borland Pascal is pretty bad.

      Titanium on the other hand has socket support, but it's fairly heavy on mobile devices for some absurd reason and I have found it better where Android is concerned to write these applications using the standard Android SDK from scratch instead.

      --
      Change is certain; progress is not obligatory.
    5. Re:75 Percent by Anonymous Coward · · Score: 0

      I'm typing this in the webview of one of my phone's browsers and scrolling is Buttery-Smooth and one line of CSS achieves the same effect in Cordova et al:

      -webkit-overflow-scrolling: touch;

      Unless a relatively low entry-level is something negative about a language, I'd say it's to do with the developer.

  12. Go for it by DJ+Jones · · Score: 3, Funny

    Firefox already uses more memory than any OS I own so what the hell, go for it. Maybe Windows 8 can become a light-weight browser that runs on top of it.

    1. Re:Go for it by asa · · Score: 4, Interesting

      Firefox has better memory management than any other popular browser. If you aren't seeing that, then you aren't on the latest Firefox version or you've got some horribly leaky add-ons installed. (The add-on problem is fixed in Firefox 15 Beta and will be available in 6 weeks.)

    2. Re:Go for it by Anonymous Coward · · Score: 0

      Firefox's memory usage has been reduced dramatically, it's no longer the memory hog it once was.

    3. Re:Go for it by Raistlin77 · · Score: 0

      Firefox has better memory management than any other popular browser. If you aren't seeing that, then you aren't on the latest Firefox version or you've got some horribly leaky add-ons installed. (The add-on problem is fixed in Firefox 15 Beta and will be available in 6 weeks.)

      Considering Firefox is one of the most horribly leaky add-ons anyone could install into Windows, I guess you're right.

      I only keep Firefox installed anymore to remind me of why I'm using Chrome. When Chrome starts acting up, I fire up Firefox and visit a couple websites just to refresh my memory.

    4. Re:Go for it by erroneus · · Score: 1

      I'm running 13.0.1 with a limited amount of addons... mostly adblock and noscript, but also RIP and firebug... right now, Firefox is using 2.6GB.... which is a huge improvement over previous versions. But then again, I have over 200 tabs open... :) I know... it's obscene. But I prefer tabs to bookmarks. Sometimes I close tabs after I save them to bookmarks and some things live exclusively in bookmarks like my banking and stuff. But for basic digging around and searching topics, multiple tabs rule my world. Information is simply more available that way.

      And the more Firefox improves, the easier it is to behave the way I do. :) Thanks, Firefox, for being an enabler of my bad habits.

      Also, thanks for being a project not motivated by commercial interests which would seek to exploit my behavior and other data.

    5. Re:Go for it by 93+Escort+Wagon · · Score: 1

      Firefox's memory usage has been reduced dramatically, it's no longer the memory hog it once was.

      I'm pretty sure the first time I heard someone make that claim was with Firefox 3.x

      --
      #DeleteChrome
    6. Re:Go for it by Anonymous Coward · · Score: 0

      Read up on Mozilla's "MemShrink" project.

      A bad experience is hard to shake, but Firefox *really* isn't the memory hog it used to be, and the next couple of releases will also kill off a lot of problems with addone leaking memory.

    7. Re:Go for it by Anonymous Coward · · Score: 0

      But it really hasn't. Really. Used memory isn't all there is to good memory management.

      In my case, I use both Chrome and FF regularly.
      I will ignore Opera and IE since I haven't bothered using either of those in a long time. (But Opera is already godlike in memory efficiency, everyone knows this, IE is better these days)
      I typically keep these browsers open for stupid amounts of time, months, sometimes around 2 and even 3.
      I regularly need to restart FF, however, because it gets stupidly sluggish after a while. Things locking up, activity tickers all over, the usual.
      Starting at around 300-400k, it ends up hitting 2gigs after about 2 weeks and sticks around that until I restart it or it crashes. (which also happens quite often)
      In the case of Chrome, it stays stable because it regularly cleans up memory. And by that I mean within the same processes, not separate ones. (and sometimes it will even kill a tab outright if it feels there is something not right with its memory)
      My extensions in both are mainly tab management, scripting, styling and downloading.
      I also visit flash-heavy sites on both of them fairly frequently. In fact, at the moment I have 7 and 8 flash tabs open in Chrome and FF resp.

      If I can't keep a system suspended / hibernated over time, that is going to annoy the hell out of me.
      But THAT as an OS?? These are worrying numbers already.
      Not going to deny that FF is massively better than it was in earlier versions, but it has a very long way to go until I'd even classify it as an efficient memory manager.
      There is some massive problem somewhere in it.
      It was also there when I had no extensions on both of them. (in fact, I had 2 on Chrome, both tab-accessors, so they added stuff to each tab too)

    8. Re:Go for it by Anonymous Coward · · Score: 0

      Try out the TabGroups Manager plug-in. It lets you create tabs of your tabs. You can have all your tabs opened and categorized within a parent tab (only one level of nesting). You can suspend (stays on the tab bar) or hibernate (moved off-screen into a drop-down menu) your high-level tab groups. Doing so 'closes' those tabs and takes them out of active memory.

      I've never understood bookmarking. Managing bookmarks is a completely different interface compared to tabs. If I want to manage my tabs, I use tabs. It's simple and doesn't require a mental context change.

      As for Firefox having better memory management than other browsers, I disagree. Firefox hides it's memory issues by unloading and reloading content as you move between tabs. That's getting around the issues not solving them. Say I want to open 50 articles (in addition to whatever else I had open) to read on a long trip without net access (yeah, not all of us use data plans - way too expensive and the companies suck). I can read around 10-15 of the articles, but by the time I try to access the other articles/tabs Firefox has forgotten their data and can't reload it due to no internet connection. It's a real headache.

    9. Re:Go for it by Rufty · · Score: 1

      A bad experience coupled with heaps of denial is hard to forgive.

      --
      Red to red, black to black. Switch it on, but stand well back.
    10. Re:Go for it by erroneus · · Score: 1

      I never said better than other browsers. I said better than previous versions. I only use firefox because:
      1. MSIE is Microsoft and "broken" and also it's Windows... I run Linux
      2. Chrome is supported by commercial interests. I do not trust. I know there is Chromium projects but I already have a home and I don't need to leave it.

    11. Re:Go for it by Anonymous Coward · · Score: 0

      Sorry, I should have made it clear that the memory issue section was directed at asa's post.

      I use Firefox too and also have hundreds of tabs, hence the TabGroup Manager (addon not plug-in) suggestion.

    12. Re:Go for it by Anonymous Coward · · Score: 0

      oh hey Asa Dotzler, what's up?

      yeah "the firefox memory leak is fixed in the latest version this time for for sure we really mean it", huh? you know, we might believe you if you hadn't been saying this every single release since the beginning of time.

      seriously, the "firefox leaks memory like a sieve" is beyond a running joke at this point, it's up there in duke nukem forever territory. we know it, you know it. the sooner you can get your head out of the clouds the sooner you'll stop hemorrhaging users to chrome.

    13. Re:Go for it by HarrySquatter · · Score: 2

      2. Chrome is supported by commercial interests. I do not trust.

      You mean the same "commercial interests" that make up 90% of Mozilla's revenue?

    14. Re:Go for it by Waccoon · · Score: 1

      I've been suffering from those terrible pauses for years, now. Since version 3.0, in fact. When the browser pauses, it only peaks on one core. In fact, anything Firefox does peaks only one core.

      I can't take an web browser seriously as an "OS" until they can do fucking thread management properly.

    15. Re:Go for it by hkmwbz · · Score: 1

      Firefox has better memory management than any other popular browser.

      Correction: That's Opera. Firefox's memory handling is apparently quite primitive compared to Opera's. While Opera dynamically adapts all the time, Firefox seems to just dump stuff from memory when it thinks it's using too much. Artificial "memory tests" do not show the full picture (such as what happens when you're surfing for a long time).

      --
      Clever signature text goes here.
    16. Re:Go for it by Anonymous Coward · · Score: 0

      I gave up arguing with turds like you and simply moved to Chrome (along with everyone else). Enjoy your irrelevance.

  13. We can be like Google, too! by Anonymous Coward · · Score: 0

    Good fucking God, Mozillia is nothing but a bunch of copycat Google fanbois now.

    They even copycatted Google's release numbering scheme.

    Yeah, that'll fool 'em all.

  14. Firefo 14 will encrypt searches by SternisheFan · · Score: 4, Informative

    "With Firefox 14, Mozilla will automatically encrypt searches conducted via Google's search engine in the browser's location bar, search box, or the right-click menu. The idea is to "protect your data from potentially prying eyes, like network administrators when you use public or shared WiFi networks," Mozilla said in a blog post. At this point, Google is the only search engine that will support encrypted searches, "but we look forward to supporting additional search engines with this feature in the future," Mozilla said." (From the PC Mag article) http://www.pcmag.com/article2/0,2817,2407263,00.asp

    1. Re:Firefo 14 will encrypt searches by Anonymous Coward · · Score: 0

      And how, exactly, do they propose protecting against man-in-the-middle attacks? My employer is currently reading all gmail I access from work, even when accessed via https.

    2. Re:Firefo 14 will encrypt searches by lederhosen · · Score: 1

      certificates I guess, my employer does not read my gmail by redirecting https.

    3. Re:Firefo 14 will encrypt searches by Luckyo · · Score: 1

      They don't. They just do what they did since FF4 - pose for spotlight and pretend to be doing something novel when they blatantly copy yet another add-on functionality, and do it horribly.

      If you are using the last firefox that actually was decent and want a much better version of this functionality, search for "https everywhere" addon.

    4. Re:Firefo 14 will encrypt searches by Gumbercules!! · · Score: 1

      But no one checks the certificate (well few people anyway), unless the browser flags them to.

      What a lot of employers are doing is redirecting all https traffic to an internal proxy which uses the domain's (active directory domain that is) trusted certificate - so all domain clients automatically trust the certificate. So when you go to https://my.bank.com/ or whatever, you're actually going to your internal proxy, which is decrypting the traffic, inspecting it and then re-encrypting it with my.bank's certificate and sending it on.

      You'd never know unless you clicked on the certificate in your browser and read the details. As the browser will leave the certificate "green" or whatever (trusted), 99.999999% of people would never think to check.

      Microsoft's ISA has been offering this functionality since 2003 and in the latest versions, it's downright trivial to set this functionality up (I have done it for clients).

      I always thought it was a bit evil and highly questionable to do this when staff are not aware, as it means the IT team can easily steal banking details, etc. It also puts a larger onus on the company to ensure their servers are not pwn3d by someone else. I get that it's all "company time and company equipment" - but when staff are not aware this is happening and exposing person information and banking details, etc, I think it's wrong.

    5. Re:Firefo 14 will encrypt searches by Anonymous Coward · · Score: 0

      At this point, Google is the only search engine that will support encrypted searches

      What about DuckDuckGo?

    6. Re:Firefo 14 will encrypt searches by CodeBuster · · Score: 1

      You'd never know unless you clicked on the certificate in your browser and read the details.

      Won't most browsers still complain, whether or not the certificate is trusted, if the domain on the certificate doesn't match the one in the address bar? This condition should be a HUGE security warning flag when detected by the browser, resulting in a modal "are you sure?" dialog explaining the problem and asking the user for confirmation to proceed or cancel the request.

    7. Re:Firefo 14 will encrypt searches by Gumbercules!! · · Score: 2

      Not if you're using IEx in an Active Directory domain. They won't flag the domain controller or the ISA/ForeFront server in this exact scenario, because they're explicitly told not to. Chrome or FF probably do but IE plays by the domain controller's rules.

      See http://www.isaserver.org/tutorials/Configuring-HTTPS-Inspection-Forefront-Threat-Management-Gateway-TMG-2010.html for how to.

      As you can see, if the unsuspecting IE user doesn't investigate, they'd never know what's going on.

    8. Re:Firefo 14 will encrypt searches by Anonymous Coward · · Score: 0

      If the company created the corresponding root certificate (installed in ever company browser, so you can access the company intranet sites) then creating "site" certificates on the proxy with arbitrary domain names shouldn't be hard, should it?

    9. Re:Firefo 14 will encrypt searches by CodeBuster · · Score: 1

      creating "site" certificates on the proxy with arbitrary domain names shouldn't be hard, should it?

      Probably not. However, they wouldn't be able to fake the SHA-1 fingerprint of the signing certificate, so you would still know that www.yourbank.com was signed by the company cert and not directly by VeriSign. That should be a dead giveaway that interception of SSL is underway, although it wouldn't generate a browser warning because the company signing cert is still "trusted". If anyone else is reading this and wants to be sure, view the certificate details and make sure that the cert that signed the site certificate wasn't the company cert. If it wasn't signed directly by VeriSign or one of the other public majors, then it's a safe bet that your SSL session is being snooped, whether the browser says it's "trusted" or not.

  15. Innovation by Anonymous Coward · · Score: 0

    Finally! Something new in the world of mobile operating systems.

    http://www.techweekeurope.co.uk/wp-content/gallery/firefox-os-phone/07-firefox-os-mobile-icones.jpg

    And I'm hearing that it will win overwhelming developer support (among users of desktop Linux)!

    1. Re:Innovation by Anonymous Coward · · Score: 0

      It's javascript. Good luck, but I'll take my strongly typed code.

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

      Hey... at least it isn't PHP. They even managed to misunderstand weakly-typed.

  16. Re:And WebOS failed because? by terbeaux · · Score: 1

    The source for WebOS is available under an open source license: http://opensource.palm.com/packages.html WebOS did not fail. Palm failed to successfully market its products for 20 years. Mozilla can make a lot of headway quickly by using WebOS as a base. With Mozilla's community clout and business position I would not be surprised to see devices running Firefox OS in a year or two.

  17. Saturated market by BumpyCarrot · · Score: 1

    Because playing for third place is really working out for MS. I honestly don't see what's going to attract users to Yet Another Mobile Platform.

    --
    Do you see what I did there?
  18. Web apps are so old school by Anonymous Coward · · Score: 0

    Why would I develop for a browser when I can produce an app for Android or iOS instead which will meet all requirements? A single codebase (more or less) catering to each of the platforms strengths that doesn't need to worry about browser inconsistencies and/or HTML5 implementations (esp. with video/audio) - or, should I say, less cost than having to support HTML5. Perhaps if Flash had remained a viable alternative, then that may have been a possible argument in its favour, but with HTML5, I'm quite unimpressed - slow animations, browser extensions, limited scripting language - and the fact that web apps seem to be trying to be native apps anyway (jQuery mobile) doesn't help. Might as well go native.

  19. *facepalm* by girlintraining · · Score: 3, Insightful

    Assuming your platform will "win big with programmers" is silly. Programmers will work with whatever you give them, and combine it with whatever they know. And no two programmers will have the same approach. Thinking you know what programmers want is like believing you know what women want. As if every woman (like every programmer) would be a cookie cutter copy of the other.

    There are only a select few things I've found that programmers esteem and have in common, and it all has very little to do with programming per-se. They are patient. They often have the ability to hyper-focus for hours or (in extreme cases) days on a specific problem, going without food, water, sleep, social contact... in fact, interrupting them may get something chucked at your head. Prolonged and intense programming over a period of days or weeks can result in epic logic failures in their daily life -- "Hey hun, can you go to the store and if they have bread, pick up some eggs?" Programmer comes home with just eggs. They can and sometimes do become obsessed with details of a project (not just computer projects... ANY kind of project) and totally lose track of everything else; time, space, the fact that the house around them is on fire, that the girlfriend (cough, hi) is threatening to bean them if they don't come to bed and cuddle them, etc. Programmers are also endlessly fascinated with a difficult to define quality I call "Niftiness". If something is nifty, they will be drawn to it like a moth to fire. However, what is nifty to one is completely mundane to another... and "Niftiness" is a time-sensitive thing... it degrades rapidly with time.

    You'll note that nowhere in there did I mention anything resembling a computer, or anything about programming itself. Programming attracts a particular kind of person; It is not the result of a particular way of doing something.

    --
    #fuckbeta #iamslashdot #dicemustdie
    1. Re:*facepalm* by Moridineas · · Score: 1

      ... Prolonged and intense programming over a period of days or weeks can result in epic logic failures in their daily life -- "Hey hun, can you go to the store and if they have bread, pick up some eggs?" Programmer comes home with just eggs. ...

      This sounds like a loose paraphrase of a passage from Hackers: Heroes of the Computer Revolution. I can't remember the exact passage but it was about some early hackers who got so into "computer mode" that they interpreted English literally. IIRC the example give was (roughly):

      Wife: "Would you like to help me unload the groceries?"
      Man: "No"
      Wife: "JERK!"
      Man: "What? You asked if I wanted to, and I don't. I will help unload the groceries."

    2. Re:*facepalm* by CrashNBrn · · Score: 1

      My wife is laughing her ass off, saying over and over, that is so you that is so you.

    3. Re:*facepalm* by Anonymous Coward · · Score: 0

      Who would get anything but eggs?

    4. Re:*facepalm* by Anonymous Coward · · Score: 0

      you've been talking to my girlfriend, I see.

  20. Re:Article Summary... by game+kid · · Score: 4, Funny

    Or, "Everyone uses HTML5, right? So if we just gut our UI code and write it in HTML5 and tout its HTML5 use enough times on HTML5 news sites and our HTML5 wiki-thing, then we'll get lots of HTML5 fans to use our HTML5 OS. HTML5 HTML5!!!!! *continues to yell 'HTML5' and 'Beefcake' with decreasing coherence*"

    --
    You can hold down the "B" button for continuous firing.
  21. *yawn* by JustAnotherIdiot · · Score: 1

    Developers go to where the customers are, no matter how good an OS may be.
    Just look how long it's taken for them to start taking Android seriously.

    --
    What do I know, I'm just an idiot, right?
  22. Re:Article Summary... by aix+tom · · Score: 3, Funny

    They are still on HTML5? Shouldn't they by now be on at least HTML23 to get ahead of Google?

  23. Re:Article Summary... by Anonymous Coward · · Score: 5, Funny

    HTML23 was soooo 30 minutes ago. Firefox 143 has HTML25.

    Oops writing this post took long enough that we are now on Firefox 150.

  24. HTML5 sucks by Anonymous Coward · · Score: 1

    too processor and ram heavy
    good luck trying to toss that at people

  25. Hmm, good luck by cant_get_a_good_nick · · Score: 1

    WebOS was HTML5, that didn't light a fire with developers. I don't see any tablet maker outside of maybe Samsung with more pull than HP, so the issues with hardware will be even worse.

    iOS used to be webapps only, until people realized that touchscreens and HTML weren't a good match. I'm not sure if HTML5 is so much of a leap to make them that much better. I still prefer Mail.app to GMail and GMail uses some of the cleverest HTML ive seen. Even on a phone which guarantees a network card, you can't guarantee a network presence 100% of the time. Local storage will be interesting.

    Good luck.

    1. Re:Hmm, good luck by tepples · · Score: 1

      iOS used to be webapps only, until people realized that touchscreens and HTML weren't a good match.

      Cameras and HTML still aren't a good match even in iOS 5. If you're making a web application, as I understand it, you still need to use PhoneGap (which involves a $300/yr overhead payable to Apple) in order to use the camera API.

  26. I Welcome FirefoxOS by corychristison · · Score: 3, Interesting

    I think Mozilla is absolutely insane coming in to the market so late, but I welcome the competition. As others have pointed out, I am not sure how well it will go over as a Phone OS, but I can absolutely see it as a hobbyist OS. It would be great on tablets, set top boxes (or flash the firmware on your Smart TV), Raspberry Pi.

    I already have a few idea's I could use it for. Small personal projects, mostly based around a Raspberry Pi. I use and like Android but FirefoxOS would be better suited from what I have read so far.

    I do web development for a living. The idea of HTML5 apps excites me as it is a system I know very well.

    Huge win if they come out with an easy to install distro for Raspberry Pi.

  27. Haven't they learned anything? by Dynamoo · · Score: 1

    Haven't they learned anything? You shouldn't be able to control device fundamentals from the browser, it's a complete security nightmare. Modern OS and browser designs try to sandbox the browser from the underlying architecture with good reason. Remember ActiveX? That was a security disaster. Java is the modern equivalent, I probably patch it more often that I use it. If the Firefox OS ever takes off then the weak security model will probably ensure that it crashes down to earth.

    --
    Never email donotemail@WeAreSpammers.com
    1. Re:Haven't they learned anything? by msclrhd · · Score: 1

      What it likely means is things like providing JavaScript APIs for multi-touch, orientation and accelerometer queries, audio reading/writing, etc.

    2. Re:Haven't they learned anything? by Anonymous Coward · · Score: 0

      Well, the interface isn't actually running in a browser, but it is using the gecko rendering engine. Your concern doesn't really make sense if you stop and think about it.

  28. Jumping into the same abyss by Hentes · · Score: 2

    as ChromeOS did. People still aren't interested in dumbing down their devices to a mere terminal.

    1. Re:Jumping into the same abyss by Lennie · · Score: 1

      Firefox OS is still more open than anything Apple releases.

      --
      New things are always on the horizon
    2. Re:Jumping into the same abyss by aardvarkjoe · · Score: 2

      Firefox OS is still more open than anything Apple releases.

      So is the Hurd.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
  29. Re:And WebOS failed because? by shutdown+-p+now · · Score: 1

    This.

    Besides, they're not the only ones pitching HTML5 as a dev platform for mobile. Win8 also does that, and it has far more mature development tools to back that.

  30. Re:And WebOS failed because? by Anonymous Coward · · Score: 0

    The Touchpad failed because it was too expensive. It is/was an awesome device and OS but if you're plunking down an iPad amount of cash, which do you think people are going to go for? I mean the choice is between something awesome but new, which might be better and something crappy but already established and ingrained in popular culture. People take the path of least resistance. Only money would have changed their mind. The fire sale proved it had a nearly limitless market for the right price (yeah, they could not have sold it for those prices but they could have sold it closer to their actual cost instead of artificially jacking it up to meet the other players in the market).

  31. Security and Efficiency by DrJimbo · · Score: 2

    This sounds like a fantastic project. I really hope they succeed. My two main concerns are security and efficiency. Firefox really seems to be a resource hog on my desktop system. They need to make drastic improvements in efficiency in order to compete in the mobile market. Sure, I have a lot of FF windows and tabs open but sometimes I have to nuke FF because it is consuming a lot of CPU while it seems to be doing nothing.

    My other concern is security. FTFA:

    Applications can for example, be installed directly from a website, without going through the Marketplace. There will be several application stores and applications can be submitted for free.

    I sure hope they put a lot of thought and effort into security otherwise it is going to be malware central. I think they are going to need to provide the option of only running digitally signed apps. As long as the user/owner has control of which keys they are going to trust then this won't impinge on the end-user/owner's freedom.

    It would also be really good if there was some way for trusted key-holder to disable apps remotely for cases where an app that contains malware gets accidentally accepted. Again, user/owners would have to be able to opt-in to this feature. There also needs to be a way to lock the phones down so a business can have control over what apps are allowed on the phones they give out to their employees. IOW, control should be in the hands of the owner, not the user. If I lend my phone to someone, I don't want them to be able to install apps.

    Just because the OS is Free as in Freedom should not mean that all contributors are automatically trusted. ISTM it is important to give user/owners the option of using a web of trust from the get-go. As long as the end user/owner has control over which keys are trusted and whether keys are used at all will keep this security feature from impinging on the Freedom of the device.

    --
    We don't see the world as it is, we see it as we are.
    -- Anais Nin
    1. Re:Security and Efficiency by Lennie · · Score: 2

      Well, instead of wondering and fantasizing about it, maybe you should take a look on this page:

      https://wiki.mozilla.org/WebAPI

      Specifically one of the Security pages:

      https://wiki.mozilla.org/WebAPI/Security/WebTelephony

      --
      New things are always on the horizon
  32. Firefox OS Is Just What I Need by l0ungeb0y · · Score: 3, Funny

    Finally -- an OS that CAN'T PLAY MP3's. I'm sure it will be very popular.
    Mozilla is floundering hard -- maybe they should just go away.

    1. Re:Firefox OS Is Just What I Need by msclrhd · · Score: 1

      Actually, it will (https://bugzilla.mozilla.org/show_bug.cgi?id=759945) along with AAC and H.264 via libstagefright.

  33. This could be the exact opposite of Android by Anonymous Coward · · Score: 0

    Most Android users complain about not getting major OS upgrades for their existing hardware.

    With Firefox OS, every user will have 37 major OS upgrades forced on them every month!

  34. So they fixed FireFox then? by JohnFen · · Score: 0

    I guess that they made FireFox stop sucking? Then please stop keeping the good desktop version a secret and let me use that instead of the ever-increasingly-crappy versions they've been giving us. I won't bother installing it on my phone until they can at least do that.

    1. Re:So they fixed FireFox then? by JonySuede · · Score: 1

      nightly 64bit but recently they haven chosen to make the download dialog useless, I can live with that...

      --
      Jehovah be praised, Oracle was not selected
  35. YAMP has auto-attract mode enabled. by Anonymous Coward · · Score: 0

    Mark my words, YAMP will blitz the mobile device market!

  36. FirefoxOS won't run on Raspberry Pi. by Anonymous Coward · · Score: 0

    What on earth made you think anything with "Firefox" in the name would run on a device with only 256MB of RAM?

    1. Re:FirefoxOS won't run on Raspberry Pi. by dveditz · · Score: 1

      "According to Mozilla, the B2G platform can run acceptably well in an environment with as little as 256MB of RAM." from http://arstechnica.com/gadgets/2012/07/mozillas-b2g-to-be-called-firefox-os-will-ship-in-2013/

  37. Re:Article Summary... by Anonymous Coward · · Score: 1

    HTML5 is the last HTML. From here on, all changes will be integrated into HTML5. HTML5 is a process, not a fixed set of specifications. I don't think I'm kidding.

  38. Big LOL by Dracos · · Score: 1

    Until Firefox OS gets installed at the factory by handset makers, no one will care. It'll enjoy the same dead-cat thump that Meebo/Maebo did.

    Now we have another organization betting the (a) farm on HTML5, which in and of itself if flawed/broken. Even worse is that Mozilla dumped their better and richer XUL for it.

    I'd rather see Gecko+XUL turned into a desktop environment to compete with GTK+, KDE, and the like. But that's the smart thing to do, which means Mozilla will never do it.

    1. Re:Big LOL by Lennie · · Score: 1

      That is exactly what they are doing, with support from a large number of operaters:

      http://blog.mozilla.org/blog/2012/07/02/firefox-mobile-os/

      --
      New things are always on the horizon
  39. Um... what? by MrEricSir · · Score: 2

    How is your employer able to do that, exactly? Doesn't your browser give you a big "OMG DONT DO THIS" warning every time you try to connect due to the certificate error?

    --
    There's no -1 for "I don't get it."
    1. Re:Um... what? by Anonymous Coward · · Score: 4, Informative

      By installing the certificate for their proxy on all their desktops, so it's seen as a certificate to trust.

    2. Re:Um... what? by Anonymous Coward · · Score: 1

      Different AC here, but that is actually not that uncommon. There are a ton of gateways that decrypt TLS, scan it and then encrypt it with their own certificate. And there are no warnings because the employer's IT people trust that certificate on all computers.

    3. Re:Um... what? by JonySuede · · Score: 2

      not they create a certification authority and push it to the workstation using AD or puppet. Then they decrypt the traffic, log it, they generate a certificate signed by the trusted local authority if it do not exist and then they crypt they data with that trusted certificate. Your browser cannot help you unless you use it to track the sha-1 fingerprint of the certs.

      --
      Jehovah be praised, Oracle was not selected
    4. Re:Um... what? by CodeBuster · · Score: 1

      Yes, but even then the domain of the certificate wouldn't match the domain of the external site, so shouldn't the browser still complain?

    5. Re:Um... what? by Anonymous Coward · · Score: 1

      Yes, but even then the domain of the certificate wouldn't match the domain of the external site, so shouldn't the browser still complain?

      No. Certificates can be generated on the fly. If you have a private key signed by the company private key then you can use that key to generate new certs and sign them. The generated certs chain of trust up to the company cert so are fully trusted.

    6. Re:Um... what? by CodeBuster · · Score: 1

      I suppose that the only way to tell would be to look at the certificate authority that signed the cert. If the cert for www.yourbank.com wasn't signed directly by VeriSign or one of the other public majors, it's a good bet that you're being intercepted ala MITM, whether the cert is "trusted" or not.

  40. Driver and firmware blobs? by andrew3 · · Score: 1

    Will Firefox OS have driver and firmware blobs like almost every other smartphone? If so, I won't be buying.

  41. difference to tizen? by Anonymous Coward · · Score: 0

    So tizen is also focusing on HTML5. Wheres the difference?

  42. look at firefox by JustNiz · · Score: 0

    Seriously, how can I take their OS seriously when they cant even write an browser that doesn't keep locking up/crashing.

    1. Re:look at firefox by Ash-Fox · · Score: 1

      How can I take you seriously when I don't experience this?

      --
      Change is certain; progress is not obligatory.
  43. Re:And WebOS failed because? by Anonymous Coward · · Score: 0

    I bought 3 TouchPads during the fire sale. Having them for almost a year now, I can tell you from experience that anyone who paid an iPad amount of cash for it is probably kicking themselves in the head right now. As is typical with of everything with the HP logo, quality control was likely non-existent. Anyone that follows the progress of Android on the TouchPad is likely also aware of the ridiculous number of TouchPad owners that have had to send their TouchPad back to HP for repair due to hardware and manufacturing defects.

  44. Re:And WebOS failed because? by cheesybagel · · Score: 1

    Mozilla using WebKit? It will be a cold day in hell when that happens.

  45. Re:Article Summary... by Anonymous Coward · · Score: 2, Funny

    "I don't think I'm kidding."

    So... who would know for sure?

  46. GUI Widgets by Anonymous Coward · · Score: 0

    It is nice to have a good variety of quality pre-built widgets when building a user interface. HTML doesn't really provide this. You could conceivably design your own widgets with Javascript and the Canvas or Javascript and SVG, or use a library built on top of Canvas or SVG. The problem here is that there are hundreds of projects trying to do this and nothing at all resembling a standard set of widgets. Also has WebSockets been standardized yet or is there still the open security bug holding it back? Long polling seems like such a hack.

    1. Re:GUI Widgets by Anonymous Coward · · Score: 0

      I guess you can also try to build Widgets with DOM. Ultimately, you run into a problem though where the DOM doesn't provide everything you want, and the Canvas doesn't provide the text layout power of HTML.

    2. Re:GUI Widgets by Lennie · · Score: 1

      Yes, the WebSocket protocol and implementation have been fixed more than a year ago.

      Although using TLS/SSL, like HTTPS, might sometimes be needed as a workaround when you encounter buggy (usually transparant) proxy-servers.

      --
      New things are always on the horizon
    3. Re:GUI Widgets by Anonymous Coward · · Score: 0

      Yeah, the text layout power is huge. My boss is trying to repurpose me to iPhone development, but I've worked through tutorials and sat through videos and I still haven't got a clue how to deal with text that doesn't fit on a line other than "never use labels unless you can guarantee your app will never be used by someone who doesn't have a traditionally short Anglican name to refer to places that don't have traditionally short Anglican names". Maybe web development has spoiled me from ever being a "real" developer, or maybe "real" UI toolkits are shit. The only thing that looks shittier than text wrapping is text being truncated. You have no idea how many times I've had to reassure people that even though they can't see all the text they typed into an input field, it's all being saved (and noted to change that field to a textbox where appropriate, and when to laugh at the user behind their backs when not).

  47. Re:Article Summary... by Anonymous Coward · · Score: 0

    You tell me.

  48. Specially Android by DrYak · · Score: 2

    the only ones that have succeeded now have complete ecosystems built around their devices.

    But the presence of those "ecosystems" does not preclude competitors. Nor do they mean that no one else should try.

    Specially given that one of the two ecosystem - Android's/Google's - is rather open (due to that phone aren't Google core business - keyword searching is their core technology and they monetize it by leveraging it to serves ads. Anything else they produce is ancillary to that. Developing phone OS and corresponding ecosystem is not a main busness target for Google. It's only a side activity which has the advantage of bringing more people online and thus expanding the number of people they can serve ads to).
    Android Apps have been already running on other systems (on the QNX powering some blackberry, on the standard GNU/Linux at some canonical experiences, etc.) and Firefox has been running on Android phones too.

    That could also be the point of entry, an overlapping echo system. (Initially, people running Firefox App on Android, and having both access to android apps and newly developped HTML5/Javascript apps. Once the second ecosystem is big enough, non geeks could be interested in a boot-to-gecko phone).

    On top of that, if you focus on regions using GSM that don't have their handset choices constrained by the regional carriers you have a far better chance than in backwards markets like the US.

    Welcome in Europe.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Specially Android by Lennie · · Score: 1

      Why a newly developed HTML5/Javascript app ?

      A lot of apps on iOS and Android are already build with HTML5. Usually with a native wrapper, which you obviously wouldn't need with Firefox OS.

      --
      New things are always on the horizon
  49. Implement WebAPIs and lose native app revenue by tepples · · Score: 1

    But OWAs won't only run on FirefoxOS (if the other vendors implement the WebAPIs).

    I don't see Apple fully implementing the WebAPIs and losing the $300* per developer per year revenue stream plus 30% take from App Store sales. It's in Apple's rent-seeking interest to require use of a native app (even if made with PhoneGap) in order to access an iDevice's microphone or camera.

    * Breakdown available on request, based on this article.

  50. imagine the pain by Anonymous Coward · · Score: 0

    Just think about this for a minute. You actually by some odd set of circumstances come to depend on Firefox OS. And then they pull the same release strategy on you that they did with Firefox. Then the project fails and you go on unemployment.

  51. Re:And WebOS failed because? by Lennie · · Score: 2

    Most be cold in hell, because Mozilla has had iOS apps for years which use webkit, like:

    http://www.mozilla.org/en-US/mobile/home/

    Because Apple doesn't allow Opera, Google Chrome or Mozilla to port their engine to iOS and "sell" it on in the Apple App Store.

    --
    New things are always on the horizon
  52. Re:And WebOS failed because? by Anonymous Coward · · Score: 0

    The source for WebOS is available under an open source license: http://opensource.palm.com/packages.html
    WebOS did not fail. Palm failed to successfully market its products for 20 years. Mozilla can make a lot of headway quickly by using WebOS as a base. With Mozilla's community clout and business position I would not be surprised to see devices running Firefox OS in a year or two.

    You seem to fail at understanding fail.

  53. There is no Mozilla... by Anonymous Coward · · Score: 0

    There is only XUL.

    1. Re:There is no Mozilla... by ChrisMaple · · Score: 1

      XUL is the minion of Gozer. Gozer will be pissed if Mozilla drops XUL. They're taking a big risk here. Is their supernatural insurance paid up?

      --
      Contribute to civilization: ari.aynrand.org/donate
  54. Re:Article Summary... by Anonymous Coward · · Score: 1

    You tell me.

    The degree to which the GGGP is kidding about the state of HTML5 is itself a continually-evolving standard. It's Agile, Agile, Agile, all the way up!

  55. Re:Article Summary... by Anonymous Coward · · Score: 0

    Accepted answer.

  56. Ironic scenario by k(wi)r(kipedia) · · Score: 1

    That would be the irony of it, that Mozilla, whose browser succeeded because of users opting to "Get Firefox", would succeed in its phone OS venture only through the support of monopolies. Carriers already selling cheap or prepaid plans could offer Firefox OS as an alternative to plain dumb phones.

  57. Curation delay by tepples · · Score: 1

    And watch your native application take two weeks to deploy through the platform's approved app store, while web workers are running on users' devices the next day.

    1. Re:Curation delay by Anonymous Coward · · Score: 0

      Yeah and the app on iOS will make 10 times the revenue.

  58. Who pays the royalties? by tepples · · Score: 1

    Who pays the MPEG-4 system, AAC, AVC, and MP3 patent royalties for a Firefox OS device?

    1. Re:Who pays the royalties? by ChunderDownunder · · Score: 1

      Does AOSP ship on Android phones? Not generally. Carriers and vendors tailor the Android source code to their specific requirements.

      Same thing applies here. If Telefonica want to supply additional functionality to their target Brazilian market, they have the option of taking the source and augmenting it with proprietary codecs.

  59. Doubtful. by sootman · · Score: 1

    We also believe that developers will overwhelmingly support our approach, because 75 percent of applications are already designed in HTML5...

    Wrong. The ability to make money by writing for a platform generally determines if developers will flock to that platform. Even if the apps are already in HTML5, if it's not worth a developer's time to spend 5 minutes making an app bundle and uploading it, they won't bother, no matter how simple you make it. And platforms aren't free. Even if you could snap your fingers and make a version for Mozilla, that's still yet another platform and yet another group of users you have to support.

    Also:

    By... adopting standards such as HTML5, CSS3 and JavaScript, we want to attract hundreds of thousands of web developers on OS Firefox. No need to learn the development languages of Apple or Google.

    One word (ok, sorta two): PhoneGap

    And finally: how did "ZOMG apps can be written in HTML5!!!!!11" work out for Palm?

    --
    Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
    1. Re:Doubtful. by Ash-Fox · · Score: 1

      I never heard of Palm offering HTML5 development, but I heard about this with Firefox OS. Have you considered the issue palm had may have been for different reasons?

      --
      Change is certain; progress is not obligatory.
  60. Thanks! by DrJimbo · · Score: 1

    I figured someone on Slashdot might direct me to the info. Thank you very much.

    --
    We don't see the world as it is, we see it as we are.
    -- Anais Nin
  61. Re:And WebOS failed because? by sp332 · · Score: 1

    You know Firefox Home is not a web browser right? What makes you think it uses Webkit?

  62. Re:Article Summary... by davester666 · · Score: 1

    Whoever's on the process standards committee.

    --
    Sleep your way to a whiter smile...date a dentist!
  63. Re:And WebOS failed because? by Anonymous Coward · · Score: 0

    Windows 8 allows users to do HTML5/Javascript as one OPTION. It also supports .NET (C# or VB, maybe more?) or native C/C++ code for the language, and XAML or DirectX for the UI layer. Or many combinations of all of the above within one app. In other words, use the right tool for the right job. Most developers I know would much rather avoid large-scale Javascript work if other options are available.

  64. Android over Linux by Moridineas · · Score: 1

    Am I the only one who thinks that Android is going to basically overtake the traditional Linux distros as the most popular face of Linux not only on the Phone and Tablets but eventually on laptops and desktops?

    There are a lot of advantages to Android over basic Linux. Easy to install apps. Commercially supported apps -- like Netflix. Easy market for businesses to monetize with software sales, etc. Games. Commercial backing by one entity.

    Seems to me Mozilla is rather missing the point, or perhaps, is struggling against a perceived future of irrelevance.

  65. Re:And WebOS failed because? by shutdown+-p+now · · Score: 1

    My point was that if Mozilla thinks that HTML5 as app framework gives them dome unique technical advantage that would entice developers to write for them, they are mistaken.

  66. HTML is XML. XUL was XML so how is this a change? by sgt+scrub · · Score: 1

    OK. Mozilla no longer has to keep XUL up to date which means those awesome listboxen with sortable columns, and various other cool things I loved so much, are back to being a complete and total PITA to write. Outside of that, what has changed? XUL was XML and it required Javascript to do its client side interactivity. HTML5 is a sub of XML and it requires Javascript to do its client side interactivity.

    As far as it being an OS that developers like, the Mozilla guys seem to like it. Maybe they will write some really cool stuff with it.

    --
    Having to work for a living is the root of all evil.
  67. does it do anything? by Osgeld · · Score: 1

    I can run firefox on a toaster, can firefox run outlook? Fallout 3? visual studio? virtual box running debian? GCC toolchains? chrome when firefox fucks up?

    I dont need a shitty computer that uses a browser as its "os", I have plenty of shitty computers that already do more

  68. Re:Article Summary... by qu33ksilver · · Score: 1

    Media right ?? Thats what usually happens. Personally, I don't think the UI elements introduced in HTML 5 like drag-drop, placeholder, content-editable etc. etc.. won't be much of a use because there are already super stable javascript libraries for that. I am not at all willing to rewrite the existing code just to make my site HTML5 compliant. Other than that, the backend stuff like client side storage, websocket protocol, geolocation APIs are the cool stuff I am looking forward to using.

  69. Re:Article Summary... by multicoregeneral · · Score: 2

    Personally, I prefer gecko to webkit. So if it's adopted by anyone, and I have a use for it, you'll probably see me writing code for it... provided that they DON'T FUCKING DISABLE SQLITE BY DEFAULT. I mean, seriously. It's like having the best platform in the world, and handing it to the majority of people who use it with the balls cut off. Makes no freaking sense. Hopefully, they've learned from past mistakes.

    --
    This signature intentionally left blank.
  70. Re:And WebOS failed because? by Anonymous Coward · · Score: 0

    More importantly, if you can write a mobile app in HTML5, you've already got an iOS and Android app.
    What does Firefox bring to the market? Other than being an also-ran?

  71. Re:Article Summary... by Anonymous Coward · · Score: 0

    Only WHATWG are declaring that. W3C are still publishing versioned snapshots based on the work done by WHATWG.

  72. OS market is far too saturated by eWarz · · Score: 1

    The mobile OS market is far too saturated for yet another entry. They should stick to what they are good at and leave the OS market to everyone else.

  73. Re:And WebOS failed because? by Patch86 · · Score: 3, Insightful

    The fact that apps can be written in the exact same programming language for Win Phone 8 and Firefox OS is a point in Mozilla's favour, not against them.

    They're banking on cross-compatibility between the other platforms to ensure that they get a decent ecosystem very quickly. That's presumably what both Mozilla and MS picked HTML5- maximum cross-platform capabilities.

  74. Re:And WebOS failed because? by Lennie · · Score: 1

    (I've never used it)

    Well, then I guess it links to Mobile Safari a webkit browser.

    And their was this other recent project that I can't remember right now...

    --
    New things are always on the horizon
  75. Re:Article Summary... by Anonymous Coward · · Score: 0

    This is supposed to be funny ?

    Everyone wants to be standards compliant, right? So if we just gut our UI code and write it in standards compliant ways and tout its standards compliance enough times on standards compliance news sites and our oh so standards compliant wiki-thing, then we'll get lots of standards compliance fans to use our standards compliant OS. Standards compliance Standards compliance !!!!! *continues to yell 'Standards compliance' and 'Beefcake' with decreasing coherence*"

    HTML5 a mess you say ? But it is Standards compliant ! Still a mess you say ? But it is Standards compliant !

  76. XHTML by unixisc · · Score: 1

    I have a question. Ever since HTML5 came out, I've been looking to see whether there's also been an accompanying XHTML5 standard. Is there? One thing I've been curious about - while going from HTML4 to HTML5, it would have been a good opportunity to merge both HTML and XHTML, and make the latter the standard, and then build in all the new tags.

    1. Re:XHTML by RaceProUK · · Score: 3, Informative

      There is an XHTML5 standard - it's the HTML5 standard, but using strict XML syntax.

      --
      No colour or religion ever stopped the bullet from a gun
  77. Solution in search of a problem by Anonymous Coward · · Score: 0

    A web browser for an OS is a horrible idea. Web is layers upon layers of turds. Anyone wanting more performance or not wanting to deal with the layers of crap would stay away from something like this. Anyone not interested in fiddling with hardware and software and more interested in playing games will again not bother with this. Where does that leave a browser based OS? Can it do anything that a less retarded OS can't? Can it do anything better?

    Why anyone would want to use something like this, and why anyone would think this is a good idea in first place is beyond me.

  78. HTML5 apps? by Grizzley9 · · Score: 1

    Isn't Facebook going back to a more closed language build b/c HTLM5 just didn't work very smoothly for more complex apps? Course WebOS was supposed to take off as well because anyone could write an HTML5 app.

  79. Re:Article Summary... by komrix · · Score: 1

    Yeah everyone is so impressed by HTML5...it really isn't that revolutionary I don't think at least. It has been around for a while, but does bring some interesting things to the table. I love that it makes rounded corners so easy, back in IE days you used to have to use a script that made your page slower than a pentium 2 i swear.

  80. Can you spot the problem?? lol by Anonymous Coward · · Score: 0

    Anyone else notice the problem on picture 4 within the article?

  81. why even FireFoxOS? by SuperDre · · Score: 1

    With the decline of firefox and the rise of chrome, they should really be worried..
    The problem for them is, the ammount of Android/iOS devices out there, people already invested a lot of money in those OSses and aren't willing to part with those apps and games they already paid for.
    Also there aren't any real devices yet which support FirefoxOS and I don't really think the major companies will support it, too much fragmentation.
    I just hope (as an Android user) Google is going to optimize the dalvic much MUCH better, as de mono/moonlight devs proved that porting Android to C# improves the speed by almost 80%, that tells me as a developer that the dalvic is really a slow piece of crap.

  82. Re:Article Summary... by MrHanky · · Score: 1

    HTML6 will include sarcasm detection for the ironically impaired.

  83. attention to mods: please mod up the parent by JigJag · · Score: 1

    DuckDuckGo integrate nicely into Firefox and it defaults to encrypted search. Been using it for at least a year and it's par (sometimes worse, sometimes better) with Google.

    JigJag

    --
    "The hallmark of humanity is the ability to move beyond sensory inputs" - Mary Helen Immordino-Yang
  84. Party Like its 1985 by Anonymous Coward · · Score: 0

    Wasn't the last "specified by comittee" Operating System a big success?

    Let's see WebOS.. no ADA

    Can't wait for ADA on my Newton.

  85. Always was the best by Anonymous Coward · · Score: 0

    Always will be the best, Just not for retards, come on all the plugins how can you surf with out them.

  86. Re:And WebOS failed because? by Anonymous Coward · · Score: 0

    WebOS was largely HTML/JS/CSS... that whole "web" thing. The problem wasn't so much that idea, but the simple fact that Javascript performance SUCKED on the Touchpad, at least at that stage. One would kind of think that, given their decent hardware and total dependence on Javascript for performance, they would have had a decent JIT and all. But the Touchpad trailed pretty much all the other tablets and phones of the day. Heck, Apple usually had the best Javascript performance out-of-the-box, and they were so protective of allowing non-vetted (and taxed) apps on the iOS devices, they didn't even allow a full Commodore 64 emulator in the iTunes store. Android performance was decent, and once you installed Opera or Firefox, it takes the lead (assuming decent hardware). Apple didn't allow anyone else's JS on the iOS devices, of course.

  87. It will be the best OS... by Anonymous Coward · · Score: 0

    It will be the best OS nobody every uses.

    Face facts- if major product creators aren't shipping it, it's not going to be successful.

    I'm always amazing how rather than learn from Linux's mistakes, development groups choose to repeat them.

  88. Re:Article Summary... by allo · · Score: 1

    the libraries (next versions) will use the native controls, when your browser supports it.

  89. Re:Article Summary... by Aighearach · · Score: 2

    Online sarcasm was deprecated in 1986. Look it up.

  90. Raison d'etre by Anonymous Coward · · Score: 0

    STORY:
    http://productforums.google.com/forum/#!topic/youtube/KdoffDJdSXU

    Btw situations like these arise constantly with Firefox.
    Slow and unstable JS engine to run an HTML5/JS based pseudo-operating system. Sounds about as horrible as Microsoft's MetroUI.
    All WebOS type systems have the potential to create a technically inferior, buggy rapid development platform for dummies, which is used by the bottom feeders in Open Source ecosystem to create cheap implementations (imitations).

    QUESTION?
    Why does Firefox OS need to exist? The reason to exist, raison d'etre being?

  91. Still requires porting by DrYak · · Score: 1

    A lot of apps on iOS and Android are already build with HTML5. Usually with a native wrapper, which you obviously wouldn't need with Firefox OS.

    Even then, the company which ordered the app still needs to "go through the hassle to port" it to Firefox OS. If the company was too cheap to actually hire the necessary work force to make full blown app, chances are that "porting the app to Firefox OS" (even if in practice it boils down to ripping out the wrapper and making sure the HTML5 works as well on Firefox OS's Gecko engin, as on iOS' and Android's Webkit engines) specially for an OS with such a small market share.

    It has been seen before: HTML/Javascript was one of the possible solutions on Palm's/HP's webOS and still, not everyone re-published their "webapp-with-a-wrapper as a glorified app" on Palm Pre.

    My logic is that, for that to happen, you need a sufficient market share, and for sufficient market share you need to attract users. /.ers, other geeks, etc. *could* be attracted by the shear technical merit of a platform device.
    normal users tend to either buy what everything else has, or to buy at least smartphones with a big enough choice of app (no matter if 99% of said apps are just fart sound boards and other useless crap).
    So I think that we end-up with a sort of loop. One way of breaking free out of the loop would be the ability to run more types of application. Hence the idea of Android apps and pure HTML/Javascrip apps on the same device.

    Once there are enough of them, the situation reverse:
    HTML/javascript becomes interesting become its cross-platform (Android, Firefox OS, iOS, webOS, blackberry, etc... all have rendering enginges which are HTML5 capable. In adition Android can also run the exact same browser. And HTML/Javascript are already first class citizens on webOS [and recent blackberries, I think]), and because it can also nicely integrate with existing web infrastructure, also it leverages the existing know-how (Javascript, etc.) that a lot of developpers already have.
    And suddenly, developping HTML5 applications becomes much more interesting for application which are rather simple in design and doesn't require complex interraction with the hardware.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]