Mozilla has stopped all commercial development on Firefox OS
groups.google.com
groups.google.com
Is it practically impossible? Are we stuck with Android and iOS forever? This tiny selection of options worries me.
There should be a sticker "Don't blame me, I supported Firefox OS"
1. Purchase non-Apple, and non-Android devices (e.g. Jolla/SailfishOS, Ubuntu Touch devices)
2. Develop software for the alternative platforms -- that's what I do. It's a lot of fun programming on a GNU/Linux mobile. I write software in Python with 3rd party modules from pypi, and Qt/QML.
3. Spread the word. Tell other like-minded developers about how fun it is to work on your alternative platform of choice. Plus since there's only 10s of thousands of users, your software actual gets used (and people appreciate it!).
>> I develop software for SailfishOS. It's like the Linux desktop. I SSH into my phone. zypper/pkcon install some dev tools (e.g. gcc, make, git). I initialise a Python virtualenv, pull down some libraries (e.g. Flask). I want to query SMS messages? I open an sqlite database on the filesystem. I can define services using systemd files. It really is "just Linux" underneath.
In any case, thank you for your efforts. I've been waiting for UbuntuOS for all the features I didn't know Sailfish has already.
Even Google's direct competitors require Google to use an Android. Skype and Outlook are great examples of apps you'd be amazed to discover will not run at all without Play Services.
It's going to take a plateau of performance coupled with a commoditization of mobile hardware for open source to move in.
Without a viable business model and with the rapid rate of change it's impossible for open source to even try and play in this arena.
https://www.bloomberg.com/news/articles/2016-01-21/google-s-... $22 billion profit.
iOS is a bit more complicated to value, but they've made more than $10 billion just in app store commissions (even not counting increased sales of hardware due to iOS). So if you consider the cost of iOS development as weighed against their hardware sales, and book the software as profit, you'd get more than $10 billion. The real profit numbers are probably higher.
Anyway, the point is that there's no reasonable way to assert that either one of them isn't profitable.
Samsung is pulling in about $4B profit per quarter from their smartphones. "Marginal"? In what universe is $16B per year "marginal"? Certainly not this universe.
Just as a point of reference, Samsung's smartphone profits are greater than Walmart's profits. It's greater than the overwhelming bulk of world corporations.
It's Galaxy, not universe!
At the scale of investment required to run a mobile business, Android is generally a bad thing, it's commodifying them in the way that Intel did to the desktop PC market.
But this is the kind of thing that requires citizen action. Also, expecting the EU commission to be the only political consumer protection for multinational corporations is not ideal, there ought to be more actions on the American side as well.
Until then, I highly doubt that there will be any hope of breaking the duopoly, at least until Google's or Apple's core business model starts failing them, which is unlikely to occur within twenty years.
From an economical perspective, monopolies are great for companies and for the country's GDP, but they tend to cause lower standards of living, because of the loss of competition.
Why? In the 5 largest European markets, Android has 3/4th marketshare [1]. How can Apple be targeted for monopolistic behavior?
[1] http://venturebeat.com/2016/05/11/android-is-eating-apples-i...
Because they don't even allow other browser engines on their iOS platform, which is explicitly what was the subject of the "ballot box" ruling.
Monopolies are per-product class. Apple is responsible for both the hardware and the software. All it takes is having one of their products own half of its market.
… which, of course, could take a long time. It did happen for tablets circa 2011, I believe.
Android's market share in Europe is 75%. Google's search market share is over 90%. Any action against Apple would be completely counter productive when it comes to fighting monopolies.
Also, you need to take into account that the Web is a third mobile platform for all intents and purposes, and Windows still dominates the desktop.
So the case for any anti-trust action is extremely weak.
I think that the conditions that Google impose on handset manufacturers are something that probably should be investigated by the Commission. The travel search thing, not so much.
That makes no sense whatsoever. MS was hit because they were leveraging their OS monopoly into driving out and destroying competitors in other categories, such as browsers. Apple is so far from a monopolistic position in the EU they have a minority marketshare.
I never understood that people keep saying that. It's not because you make a lot of money that you will get under investigation for being a monopoly.
Microsoft was fined because it used it's marketshare to bulldoze into other markets. Apple marketshare is so small in comparison that it can do all the same stuff without disturbing anything.
The best now is Jolla, which I don't think has failed at all yet (I have a Jolla C, I wrote about it shortly here: https://blog.separateconcerns.com/2016-09-16-thoughts-1.html).
https://github.com/webos-ports
Open WebOS became LG WebOS and is still around on their TVs...
Google and Apple both rely on ecosystems to attract and retain users, and Samsung doesn't have a competitive (or compelling) ecosystem. <end north american centric summary of problem>
I don't know if Samsung has the same problem in other markets, but I know that Firefox Marketplace does/did.
Firefox OS promised to make app creation easier through web technologies, but "not enough apps" isn't the problem with Android or iOS, quite the contrary, so for an end user, that's pretty irrelevant.
I don't care if Jolla or Ubuntu don't ever make it as "major" players in the mobile OS world.
I'd be perfectly happy with GNU/Linux mobile software that's as good as the Linux desktop.
I run Linux on my desktop (and laptop), and we're 1% of desktop users. I'd be satisfied with 1% mobile market share. We don't need a billion users, all I want is a hacker-friendly platform, with a good developer community around it (which I think both GNU/Linux on the desktop, and IMO SailfishOS [Jolla] provide).
Otherwise, there's the possibility that the Fairphone 2 will receive official SailfishOS support. Finally, there's a number of yet unreleased devices with official SailfishOS support[2]
[1] https://wiki.merproject.org/wiki/Adaptations/libhybris
[2] https://together.jolla.com/question/136143/wiki-available-de...
Here's a comment I wrote about the situation on reddit:
---
Yes, I'd prefer SailfishOS to be 100% FOSS, but Jolla is helping GNU/Linux establish its roots on the mobile.
How is it doing this?
* libhybris has opened up a whole new world for GNU/Linux, by allowing programs developed against glibc (i.e. GNU/Linux) to run on top of proprietary Android drivers (i.e. phones).
* Jolla puts a lot of development into lipstick, which makes it easier to develop UXs for phones/tablets/other form factors [This involved developing Wayland support]
* Jolla have opensourced their browser (Qt5 + Gecko engine) and their office suite (Nokia's Calligra Office work, with a QML interface)
* Jolla develops a sychronisation framework (buteo-sync) that can be used for syncing emails, Twitter, CalDav/CardDav, etc (I think Ubuntu Touch might adopt it in the future)
* Want to see how much manpower Jolla dedicates to developing FOSS? Look at the number of @jollamobile.com emails here: https://git.merproject.org/groups/mer-core/activity
* The SailfishOS community has been developing sfdroid. A FOSS application for running Android apps on your GNU/Linux mobile.
So while SailfishOS isn't 100% open source, it's doing a lot of good for the GNU/Linux community on the mobile.
* approx. the same as OnePlus One, which partially[3] supports sailfish as well
[1] - https://shop.fairphone.com/en/ [2] - https://wiki.merproject.org/wiki/Adaptations/libhybris/Insta... [3] - https://wiki.merproject.org/wiki/Adaptations/libhybris
I develop software for SailfishOS. It's like the Linux desktop. I SSH into my phone. zypper/pkcon install some dev tools (e.g. gcc, make, git). I initialise a Python virtualenv, pull down some libraries (e.g. Flask). I want to query SMS messages? I open an sqlite database on the filesystem. I can define services using systemd files. It really is "just Linux" underneath.
The paid ecosystem around SailfishOS is non-existent, having said that Jolla are looking to hire: http://jolla.com/jobs
BTW, it was actually in the Sailfish IRC dev chat that the whole "hire an assassin to take out Poettering" thing was uttered as a late night, off color, joke...
I work on Android daily on hardware that is as "hacker friendly" as it comes besides the driver issue, and it fights you tooth and nail.
In reality though, it doesn't really work on most of modern phones, and on the ones it works on, there is no WiFi support. And the latest commit on the Replicant git (excluding website changes) is 8 months ago. And it has just one guy committing.
So it didn't catch world's attention, apparently.
http://blog.replicant.us/2016/08/replicant-6-early-work-upst...
My phone (Galaxy S3) uses Replicant, and I'm quite excited for the upgrade, which will fix a number of rather unfortunate issues. I'm more than willing to make such sacrifices, but it'd be nice (for example) to be able to take videos of my children, which the current version cannot do.
It's not a shortcoming of Replicant---the fact that these issues exist at all demonstrate how much value is placed on user freedom.
Most unfortunate is that few users will be willing to make these sacrifices.
(It's possible I just don't understand the websites; looking at their GitLab and Redmine, I start to understand why is Github so popular; I cannot find anything there :(( )
It seems to have already happened[1].
[1] - https://wiki.merproject.org/wiki/Adaptations/libhybris/Insta...
Moreover, it's not Linux if you have to use a Java API to do anything useful.
And everything to do regarding being a fork on the Java ecosystem, and I side with Oracle.
It remains to be seen if Brillo or Fuchsia will have any relevance on the market, even when coming from Google.
Android is just the Linux kernel on the phone -- that's the issue I have with it. It comes with none of the other stuff that makes GNU/Linux great: philosophically/socially it's different, but on a technical level it's missing rest of the GNU/Linux stack (e.g. package management, and the plethora of developer tools -- including languages and libraries). The GNU/Linux stack is developed by a diverse ecosystem of contractors, big and small business, and non-for-profits (e.g. Red Hat, Intel, Mozilla, Samsung, Canonical, Document Foundation, Fujitsu, Google, etc). Android is largely controlled by one company.
https://www.youtube.com/watch?v=ig9GKAFzDxQ
https://www.youtube.com/channel/UCthvmTSlmIcMH93LIJNe-2w/sea...
http://penguindreams.org/blog/android-fragmentation/
The TL;DR, Android needs to be fixed so ASOP can be installed on any phone, just like Linux/Windows. The current state is bizarre for what's essentially now a general purpose operating system.
If anything, Android is a fork of Linux.
This behavior is the default because it prevents developers from needing to think about their UI changing dimensions (including runtime screen size/density changes!)... but it's certainly not required by the framework.
If you set android:configChanges="orientation" in your application manifest, your app won't be automatically restarted. However, you'll become responsible for swapping out any UI resources at that point.
(Keep in mind that Android lets you declare completely different UI layouts and drawables for different device configurations, so depending on how you wrote your app, you may need to re-inflate part of your UI.)
Or just implement onSaveInstanceState() and let the OS do everything for you.
No, the framework uses it to let you automatically handle those changes, the reason it's there is because early Android devices were weak (obviously) and the pipe dream was that we'd write apps that didn't mind randomly getting their processes killed as long as we used onSaveInstanceState... man-centuries later and it's clear the dream didn't pan out. I wonder how many billions of NPEs it was worth to be able to say Android does what iOS don't (multitasking) back then.
And that android:configChanges line misses out on many other triggers that cause you to need to handle onSaveInstanceState (like someone plugging in a keyboard). Even with every flag set for configChanges you still need to implement onSaveInstanceState for process death to work as intended.
The Android framework really is garbage. I might be biased though, I spent the day trying to trick it into not going to 7(!) FPS because our designers had the audacity to request we translate a video in an animation (and don't get me started on the insanity that is animations on Android [the X ways we've now gotten to do it which all have their own limitations]).
Really, all I care about is receiving SMS.
Also, does this thing even receive SMS? The page makes no mention of phone support.
To your question regarding SMS, there are already people working on it. A Vim plugin sounds especially delicious.
https://pyra-handheld.com/boards/threads/how-to-send-receive...
I'm preparing him for Minetest, though, if that makes you feel better!
"A 6000mAh battery means you have a companion that will be there for you, through use and at times other devices have given up long ago."
But if you look deeper you find on their wiki:
https://pyra-handheld.com/wiki/index.php?title=Battery
"Everyday work load: 8 hours (without any power management features, tested on prototype April 2016)"
8 hours? This is a toy. Why is their headline figure "6000mAh" instead of "8 hours"? Because they know it's shit.
I've been on projects where the dev builds would last 30 minutes on battery right up to days before initial factory run
Please tell us more about the LTE capabilities. Is it provided by a removable board? Which bands are supported??
Based on https://www.dragonbox.de/en/45-pyra it only supports B17 and AWS, which makes it mostly a AT&T compatible device
I wish it would support other bands, B25 for sprint (which has cheaper LTE plans)
Also, the wifi chipset is known. Can you run a hostapd?
Here's what I could find on the wiki.
https://www.pyra-handheld.com/wiki/index.php?title=Modem
and
Also they seem to at least cater to those not caring about apps, not able to pay for iPhone and dislike for Android.
Overall Market share in Europe around 5-10% was around a few months ago, but they have money to spare, and might keep selling Windows Mobile devices just not to loose face.
You cannot sell mobile OS based on FOSS religion, normal people want the apps everyone has and convenience, while most developers care about tooling.
So whatever alternative comes, must have a very good selling point to consumers and developers currently targeting the established platforms.
However I do think it's something that isn't yet ready for primetime, and it's going to be more a year or more before it is.
In the meantime they are trying to iron out bugs, improve features and get more developer attention for it. Recently they've added support for React Native: https://github.com/CanonicalLtd/react-native
HN readers might like to check out the Ubuntu Developer blog: https://developer.ubuntu.com/en/
Ok well I guess I'll stick to android then...
There was a brief flurry of activity around it, including getting it run on older Nexus devices, then it petered out.
I submit that a big part of the problem is fragmentation of effort. There was no reason for Ubuntu, Mozilla, and WebOS all to be aiming at the same target at the same time in very similar ways but by different people.
Open WebOS is a different beast (much like how Mozilla wasn't Netscape Navigator), based on the open sourced components of WebOS.
I could also say the same about people upset with Facebook-2009-2010 people!
The problem with that, from my perspective as a developer, is that I don't want to develop apps for low-end devices because it's an enormous pain in the ass. The lack of horsepower and features means you're pretty much required to compromise your vision, unless you really are developing something very simple, or with minimal finessing.
On top of this, and this was even more so 3 years ago, today's high end devices are 2 years' time's low-to-mid-range devices. If it takes you 6-12 months to develop your app (again, depends on complexity) on today's high end hardware you'll be targeting the mid-range when you release. Of course, there's a bit more nuance to this because single core performance isn't really increasing that much, but you get the point.
Short version: targeting high end devices means you're developing for the future and not incurring the compromises (and, in fact, support overhead) of dealing with low-end kit.
It's a real shame and it wasn't something that was immediately obvious to me at the time because I was very new to mobile development. Now of course I've experienced the same frustrations as every other mobile dev and realised that it's just not worth targeting anything but the top quartile. That is, unless it's a corporate app and you have a large number of lower end devices in the field that you don't plan on replacing before your app is deployed.
Hey, at least it isn't a monopoly and one of the OSes is freeish. Freedom wise, hardware is behind, but the software is ahead (of the desktop market).
The issue is where the money is coming from.
Also, to move on an entrenched market you need to do a lot of things upfront. Android in, let's say, 2011 was much worse than iOS, today the gap has closed.
I think what Microsoft wasted on Nokia's phone business was something in the magnitude of >$8 billion, so money was not really the problem at least in their case.
Offer something people want that the others don't. It's not enough to just not be iOS or not Android, that only appeals to the small segment of people that HN appeals to.
The selling point for Ubuntu, Mozilla and Microsoft's phone was just 'it's not them.' They didn't provide any value. Microsoft had apparently forgotten what they had to do to make the xBox viable against Sony and Nintendo when it first launched, because they didn't just launch it with 'Hey, at least we're not Sony, the developers will show up eventually.'
At any rate, it seems like two major brands is all the tech world can handle.
So, something like Cyanogenmod but with more drastic changes. It's Linux under the hood after all. It's already compatible with GNU coreutils and a whole bunch of other free software. No need to start again from zero.
For the same reason DOS/Windows reigned on the desktop for decades, with Mac having a few percents and Linux repeatedly failing to grab any significant market share.
For this reason, Android is a good middle-ground. It's well-sandboxed by default and if you need more power you can root it. Nothing is stopping anyone from releasing "free software" open source android apps published outside of the play store. As is, they would get more adoption than any app on the Ubuntu/Firefox/etc store.
As long as Android exists and is easily rootable, and preferably as long as the iOS jailbreak community keeps up with major versions, I'm happy with the state of "linux" on mobile.
Additionally, even if you trust Google today, they can turn evil tomorrow and then we'd have >75% of people who are using android without any options. Diversifying the available options in the market market is good for everyone except Google.
Windows and OSX rule on the desktop/laptop with Linux a bit player.
Intel and AMD on x86 with Via, IBM, and Cyrix and the rest either no longer being able to compete.
ATI and Nvidia on the gaming GPU end, and even then ATI had to be swallowed up by AMD to remain competitive. Intel still a bit player for budget graphics and with no product that remotely compares with the GPU heft of even a many years old Nvidia card.
We'll probably see iOS and Android be the default mobile OS's for a while with MS's Windows as a third player. Surface tablets and Windows phones still sell. If anything, the Surface Pro might be the best mobile Windows device out there and one of the nicer mobile devices for sale anywhere.
That said, mobile is probably resistant to a foss solution as people expect all sorts of cloud and managed experiences. Maps, siri/googlenow, cloud storage of photos, ease of buying, sharing, casting, media, etc. Most people won't be happy with an unbuntu phone that doesn't have all these features and probably couldn't care less about the privacy argument here. Do default installs of Sailfish, Tizen, and Jolla have any of this? Joe Consumer won't buy these things if they can't compete feature-wise.
Windows 10 Mobile has some of the advantages of iOS in terms of security updates and the Microsoft developer infrastructure -- whether that's a good thing depends on one's technical opinion of Visual Studio versus Xcode and Android Studio in terms of programming ergonomics and features and languages.
All that said, that doesn't mean that Windows Mobile will ever be successful or that a world where it's Apple, Google and Microsoft would be significantly better.
I'd still like to see a credible OSS alternative in the mix as well, and I wonder if Mozilla couldn't make that work if they dropped their low-end focus.
It has some parallels with Microsoft's strategy and could roll back into phones as just another device. And I think that getting a platform that works from embedded to server clusters has a good chance of how provisioning phones works ten years from now.
There's really nothing magical about phones. It's some compute cores, a bit of memory, some radios, a battery and a display. The only distinguishing feature of a phone is how the radio is tuned.
That is how hard the problem was to solve for Mozilla OS. They were essentially building a competing OS when they could have just been building a competing distribution.
Android (AOSP) + Firefox + Firefox Market + Firefox Mail could have been amazing.
Firefox OS should have competed against Chrome OS instead. Partner with some OEMs and you have a great alternative to Chromebooks.
A great Windows Phone 10 launch would not have put them in the top two, but it may have solidified them as a third platform.
I think it's pretty simple: people want to use apps on their phones, and no phone OS is viable without a competitive library of apps.
Most major apps are developed for both iOS and Android, and convincing app developers to develop for a third platform is going to be a tough sell, unless that platform is very attractive to users. However, to be attractive to users, it will have to have a lot of apps already...
I suspect that the only way to gain marketshare for a new mobile OS is to ship it with an Android or iOS compatibility layer, which would be pretty difficult to do well. The developers would have to re-implement the entire iOS or Android API, and keep up with all of the changes. If they did that, there would be no incentive for developers to target the native APIs of the OS, because they could just target Android or iOS like they do already. So, the compatibility layer could never be deprecated.
So yeah, I think we're stuck.
People aren't interested in apps. They're interested in capabilities.
The apps markets are good for ... delivering a completely dizzying (that is: intentionally discombobulating and confusing) array of crappy software that sometimes works, always intrudes on your privacy and steals your personal information, and frequently goes titsup.com for no particular reason and with limited notice.
I don't want apps.
I want decent browsing capabilities with document management.
I want explicit control over networking.
I want a messaging capability. SMS, IRC, eMail, whatever -- there's no reason these need to be split out.
I want a multimedia player.
A basic set of utilities. The same ones as were on the Xerox Alto 48 years ago: A calendar, calculator, notepad type editor. Basic spreadsheet wouldn't hurt.
These days something with maps and an encyclopedia would be handy. Stills/video camera and gallery.
And since I'm not the 99.98%, I'd like a goddamned full-fledged shell running Linux or BSD.
But StuffMyCrapWebsiteIntoThisApp.com? Not so much.
I've been living this for the last several years both with Android and ARM devel/hobbyist boards and it isn't much fun. It would be nice these quasi-business entities (i.e. Mozilla, Canonical) would forget about their brand-exclusive strategies and try to rally around an open ARM-based platform (you know, with support for things like, I don't know, GPUs and such) they can all run on. THAT I could get excited about and we could all win. Short of that, I don't get what I want and they continue to lose relevance in the mobile era. Granted, I'm part of the 1% that runs Linux. But here's a newsflash: right now we're the only ones who care about Canonical, Mozilla, etc. and ~1% beats 0%.
I don't know of any situation where the ARM ecosystem works like that, the companies compete for differentiation, they have a very limited interest in standardisation. Maybe I'm missing what you're referring to. It also wouldn't get you a phone, it would get you a base board but all the other bits like radios compete on the different manufacturers platforms.
I'm not suggesting that this be done purely from the standpoint of altruism: for both the IP providers and the various foundations, this would provide them with a possible path to participate in mobile that is closed to them currently so it seems like it's in their interest from an existential standpoint. That said, maybe it really is impossible to motivate any of the players necessary to go down this path. In which case it seems worthwhile for the open source crowd to go all-in on something like RISC-V/OpenGPU and jettison the proprietary IP as completely as possible, as soon as possible.
This has to be one of the best ways into handset market for MS/Ubuntu or others.
I love it, because it's un-addicting. android and ios are designed to get your attention, all the time. FirefoxOS ist a tool that is there for you when you need it.
I wish they had succeeded, I even ran an FirefoxOS meetup in Vienna, I will miss it. Now back to my Android Phone, I think it beeped, vibrated or needs me in some other way.
And thanks Mozilla for making an OS that glitches out if you use the power button in the wrong moment, nothing wakes you up better than having to reboot your phone to stop the damn alarm clock.
FirefoxOS is such an unfinished shitfest. I have no idea how 1.3 passed QA. (Nor why Alcatel still isn't releasing any update, even though they're still selling the phone in question.)
Only now, pieces of the HTML/DOM/JS spec that have been kickstarted out of need when FxOS was being developed start landing in the spec.
Whoever will try next, will have an easier job because of the FxOS experience.
source: I'm an engineer who worked on FxOS in 2014-2016
To me this is synonymous with "has less features" or "unusable". I think Microsoft actually did an ad campaign on this "un-addicting" thingy.
If you're actually optimizing for time well spent, re-read https://medium.com/swlh/distracted-in-2016-reboot-your-phone... (you can apply most of this to Android).
There's no other OS on the market that lets you do this.
I took a major step back in UX because of poor hardware designs. I shouldn't be forced out of an app just because my finger slid a little bit off the screen and hit the home button.
I'm actually trying to get rid of it and move because Window Phone 10's UX is a mess. Nothing makes sense, and apparently most developers don't have a clue about UX in the WP10 ecosystem.
For example, the native app to watch video, doesn't have a control to swipe and fast-forward. Wut? So you have to actually click on the length bar to get to the minute you want. That's like UX 101. And it's like this with so many apps...
Edit: I was amazed by LG's UI on android 4.4. It's fucking cool. Those guys know how to make life easy and pretty for folks. It is actually a 14 bucks phone that kicks 100++ bucks phone assess
Roughly at the time the 950 came out I switched to androidland. This year I wanted my upgrade to be the iphone but when the rumours about the lack of headphone port became undeniable I ended up by upgrading into a new android phone, which I'm using right now.
All of this sucks because there's absolutely nothing that comes close to the fantastic design and usability patterns of windows phone.
You mean you love it because you hate using it?
> un-addicting.
Interesting marketing formula. "Un-addicting". Might be useful in the future to justify the uselessness of a product. "but it's a feature! it's un-addicting". It was so un-addicting Mozilla killed the project dead.
This is always true to a degree, but the more true you think it is, the less likely you are to jump onto said initiatives.
While I'm sad since I can't now run Firefox OS on my OpenMoko phone, while listening to my ogg vorbis files and rocking Chandler, the revolutionary PIM app and posting updates to Diaspora, this should have been the conclusion from the beginning.
It was pretty clear that nothing much was ever gonna come out of it.
To be fair, on whom can you count? Although Google has had a success with Android, my impression is that the ground is littered with the projects that it advertised heavily but then left behind, abandoned, or killed.
It's certainly the reason I've never paid Firefox OS any attention (and it's a lot of why I won't even look at most things coming out of Google).
If leadership aren't aware of this general "meh" attitude, they really should be.
You can't compete with Android by being slower, less responsive, and ship with less features.
Maybe they thought Gecko would be ready by the time the OS was going to ship?
And FF is not FF-OS.
And FF-OS was a complete OS that ran on Gecko, so yes, if Gecko (FF) is slow, the entire FF-OS is slow.
Open dev tools, type `for (;;) {}`. Notice the whole browser becomes unresponsive. This has been improved upon (as in it doesn't block the whole Firefox UI, just merely every single content tab) thanks to Electrolysis partially reaching stable but "there are no problems whatsoever" simply isn't true performance wise (and this is the most obvious one, there are numerous other very well known performance issues with FF)
DOM painting/manipulation times in Gecko are a joke, probably the worst pain point of Firefox. And it's not the only one...
There is a very simple solution to both these problems, which most people employ to great effect: just don't do that.
The one downside is that it's memory-hungry, so on my very underpowered phone, it gets pushed out of memory a lot when switching apps. On a more powerful device I'd never notice.
Most of the Smart TV on the market today are total piece of Junk. They are what "Smart"phones were before the iPhone came out. As a matter of fact, SmartTV from China are pretty good on the software front, and lacking ( price cutting too much ) on the hardware.
Just wanted to mention about Mozilla leadership. And so call leadership in general, HOW DID these *&@^$% ever got to their position? This is speaking from a user who has been with them before the Firefox era.
It's why I have a TV and a Roku, rather than a Roku TV. Why combine them when their upgrade cycles don't match up?
The UX we currently have TV Sucks.
P.S - The problem with this solution is that no manufacture is willing to sell you a display panel only.
This is a problem for TVs and other home appliances that are usually replaced by people once every several years or even once a decade or longer, on average (this does vary across regions and on incomes, but it's definitely a whole lot longer than people's replacement times for smartphones).
Rather than build an OS, why not create the foundation or platform for others to build on? I am thinking of Electron here. Although, I am not a fan of Electron, the framework and approach are gaining a lot of traction with developers. Where is the slim, fast, embeddable Firefox engine that's easier to deploy and develop than Electron (and superior to the heavy embedded Chrome)?
What about offline capabilities for web apps? Firefox should be trailblazing in this space. This is a huge privacy advantage (amongst other things) over cloud-based systems.
I really want to see Firefox succeed, but am worried they have lost direction and focus, or even the ability to excite and inspire developers with their future plans.
Mozilla has no technical leadership problems, but they have some huge people and business leadership problems, and until they figure out a path forward, the path will continue to be a meandering trail to the bottom :(
I don't want smart features, a fancy remote with two dozen buttons, TV tuning, or anything. I'd be happy with a thin TV but I don't need one.
Just give me a way to put my PS4 on the wall and I'll be happy as a clam.
The market will force a correction at some point if the value is there for an open platform.
IBM tried to close the PC again with the PS/2 models but it was too late for them.
http://www.extremetech.com/computing/57702-hewlettpackard-co...
And regarding the burden that IBM's choice strained Compaq with, in the overall impact on the industry, any difficulty was by far offset by the benefits. If we're going to focus on BIOSes, for example, the fact that the source code was available certainly helped Phoenix.
All computers on those days had such manuals and extension slots.
Had Compaq not done a clean room reverse engineering, everyone would have to license from IBM just like in other computer systems and the PC market would never have blossomed as it did.
In fact we are just going back to those days in what concerns selling packaged hardware and software as one single product.
Original commenter mentioned IBM's publication of its source code and schematics. You spoke up to dispute that it happened. You took action. As if to call them out and say, "Hey, just as a point of fact, that isn't true". But as a point of fact, it is true.
If you have some commentary that focuses on some other market/industry forces that you think were more salient, then fine, let's have that conversation. But don't dispute facts and then try to rewrite the record as if that's not what you did. This is text. We have the conversation on record, you know.
That iOS/Apple (of today) are so revered by open-systems loving folks is a little bit counterintuitive.
In order for a solution to be successful it must be good at first place. FirefoxOS wasn't good at first place no matter how open it was.
[1]: http://janos.io/
I remember looking into whether there were alternatives for a while and really not being able to find anything.
I still miss WebOS and my Pre.
I will repeat my take here, for the last time, on where they screwed up: They screwed up by pretending to target low end devices but still only supporting centralized communications. They should have had Ad-hoc/Mesh Wifi as a requirement, and designed the OS API to give those features to developers. Developing world people want to send things between one another, not huddle around shared wifi or pay premiums to carriers. I wrote this up in some detail at https://bug945047.bugzilla.mozilla.org/attachment.cgi?id=840... ... nobody bothered to reply, except for "wifi supports in FFOS is relied on wpa_supplicant which is provided by partner mostly", ie. the business setup within Mozilla was that the actual device manufacturers were the ones who had control of the wpa_supplicant build, and there was no way for the developers to rely on, require or enforce features in that software being present. Nobody took ownership, everyone lost.
From what I've gleaned, the only differentiating factor was that all apps are Javascript. Like my mom cares what languages her apps are written in.
Of course the big difference is that Linux succeeded while Firefox OS failed. But thats after the fact.
I think something like Firefox OS is important, but probably wasnt something Mozilla should have undertaken when their key asset was under massive threat and it keeps dropping other stuff that, admittedly small numbers of people are using, were still successful in Theur niche and could have continued with minimal effort (examples of projects that affected me directly are Thunderbird and Prism).
The relevant big difference is that Linux filled a need and had a particular niche that had nothing to do with being "libre": it was good and costed nothing to run servers on.
Big UNIX vendors charged an arm and a leg (and often required their own hw platforms to run), and their software was behind the times (to the point that loading the GNU userland was necessary for getting them remotely comfortable to admin/program on).
Otherwise, Linux has been a failure on the Desktop too (statistically, nobody cares if someone here personally uses it -- the original idea of most Linux advocates was that it would conquer the desktop, overtaking Microsoft. Not that "it would get good enough to be used by some users on their desktops". It was already that, back in 1999).
However, I've heard the high cost of UNIX licenses in the early 90s was the reason why Linus decided to start his project.
Also, Linux has never been "a failure" on the desktop: you seem to think that the definition of being successful is to have a complete monopoly.
Complete strawman.
First, I used the Linux advocates' own definition of "success": Linux overtaking MS on the desktop, and the fabled and continuously moving "Year of Linux on the desktop". Which never happened.
Second, what "complete monopoly" rubbish, which I never alluded to? Linux has less of 2% on the desktop (by all browser-based stats). For a completely free OS, that's a failure. 10-20% would have been a great success.
Anyway, where did you get that definition? It is the view of the Linux Zealot. To say that it some sort of general definition is just silly.
You also seem to think that if an operating system is free (as in cost?) people would automatically go for it. That is simply false.
In any case I think Linux will outlive Windows. Windows is pinned on one single player and Linux is has reach over many.
You have to understand that "Linux" differs greatly from Microsoft Windows(R) because of its philosophical underpinnings of being "free as in freedom" software.
BTW I've heard the market share of Linux on the desktop has steadily been rising for the past few years... just give it some time ;)
I'm not even a web dev, but I'm sad to hear that it didn't pan out.
I told Mozilla people on this forum for many years that it wasn't going to work, anybody can check my history. It didn't fail because they were using web techs but because they were releasing low end phones. Firefox OS phones should have been "geek" phones, phones for people who already own 2/3 phones and want something they can "hack" and boast about. The product itself wasn't bad, the strategy was. Again targeting emergent markets was stupid, people in emergent markets either have "feature phones" or android phones, because of what's app and co, Firefox OS should have targeted geeks and hipsters , with high end models... That's how you make a brand or a product desirable.
Mozilla tried to market it as a low cost alternative but nobody wants low cost rubbish. You are better of with a feature phone.
I think the biggest mistake was the reliance of the OS on javascript. It was dead on arrival or better said from start.
It's a tough market because as soon as you release something, there is a ticking clock until all of the low cost manufacturers release something cheaper and faster. Moore's law is not your friend when you're trying to differentiate a mobile product.
Beyond that general difficulty, a web phone faces some specific inevitable challenges:
1) No access to the "app world" of Instagram, Snapchat, etc
2) Can't optimize performance to the same degree
3) Web app access to hardware devices is limited
I think those are things you can't fight, you just have to accept them, but they are really hard to accept. This is the key psychological hurdle in any new web phone design project.
But let's get over them for a second and see what we're left with. The web also has some indominable advantages:
1) Instantaneous installation/startup of new "apps"
2) Long tail of web content can be a first class citizen in the UI
3) Novice-friendly development platform, i.e. "show source", embeddable HTML widgets, etc
4) Cloud-based by default
5) A community who will deploy infrastructure for free, so long as it is open source and decentralized
If I squint my eyes, I can imagine a web browser that really tries to capitalize on these things. From first principles, I think a development platform where the infrastructure for getting started is free-ish, apps and development environments all load instantaneously, data is never lost because it always lives in the cloud, emerging standards allow data to federate freely between services... you just float around allowing app access to your cloud data... such a platform would have substantial advantages over something like iOS or Android.
Those advantages may or may not be able to outweigh the inherent platform weaknesses I mentioned, but I can at least imagine it becoming a major player on mobile.
I think the trouble for Mozilla is there are still quite a few research projects there:
How do you federate data between services?
How do you host open source web apps in such a way that neither the programmer nor the end user has to be a sysadmin?
How do you make it easy to write performant, mobile friendly apps?
How do you organize a decentralized global community to adopt good usability practices?
How do you design a web browser so that web developers can make simple, fully integrated apps that fit into a more unified mobile experience?
I think if you could design something that at least solved all of these problems in a simplistic way—not fully robust, but a proof of concept with a few core apps, messaging, video, etc—and you really leaned in to the kinds of experiences that become uniquely possible on a platform like this, and then refine the shit out of it in an empirical Apple-style user-centered design tsunami, I think you might have a leapfrog product that could put Android and iOS on their heels.
Maybe.
If you could make it fundamentally easier to build and deploy web apps, you could get a huge store of long tail apps, which would form a kind of exclusive content moat. Not because those apps would be inaccessible on iOS or Android, but because they would be second-class citizens there.
To different extents Google and Mozilla have both been trying to tackle some or all of these research projects in different ways. But I'm not even sure if it's time yet. Maybe we just need to wait a little until some more of these answers shake out. Or maybe Mozilla just lacked the strategic vision to really know what to hammer hard on here.
But I am totally grateful to them (and Google) for trying. I still am drinking the Kool-aid. I still think the web is the future. Thousands of people are working on these problems all over the world. I think as Ethereum matures, it will fill in a lot of the gaps.
So, I think the Firefox can rise again. We'll see.
I prefer my phone to be a phone and not a general purpose computer. The less complexity the less problems incurred. Few vendors are willing to put in the really hard optimization to make a lowend device work well.
The lowend target of FFOS was an additional concern because it meant the software had to be that much better.
[0]: http://www.flatpanelshd.com/news.php?subaction=showfull&id=1...
Or well, any lightweight Linux distro, really.
There's also this, in case that comes closer to what you see as ChromeOS competitor: https://cublinux.com/
And after the dud launch, whatever momentum had been there, simply dried out. Nothing major has happened since launch for Firefox OS, while Android and iOS have had several major releases.
That it took Mozilla this many years after the fact to admit this failure, is (as other comments) a sign of bad leadership.
The effort spent here could have been much better spent elsewhere. And these days Mozilla needs to spend its resources efficiently more than ever.
IMO the whole "connected devices" initiative which Mozilla also mentions here (I had completely forgotten about it) will suffer the same fate. It's not connected to anything they currently do, or anything they have a natural ability to reach out to. Whatever drives this initiative, it seems completely disconnected from engineering.
Unless they kill it now, we'll see a similar announcement in a few years. And that too will be resources that could have been spent more wisely.
The first Firefox OS phones shipped in early 2013. After spending around two years trying to make the project work, Mozilla stopped releasing new versions in May 2015 and officially started winding down the project by the end of 2015, as mentioned in the linked newsgroup post. So it wasn't really many years at all; also, it's hard to place the blame on "bad leadership" when the current CEO didn't come on board until the middle of 2014.
Neither CEO did anything to mitigate this issue. I don't know how that's not bad leadership.
(Not that updates would have helped much: 1.3.0, the last and only FxOS version my phone received – which is still sold by Alcatel – was much worse than Android 2.0 in terms of UX and stability. I have no idea how anyone thought this was in any way ready to ship.)
Arguably that's great leadership because the CEO knew instantly to cut his or her losses, and not give into the sunk cost fallacy by pursuing this failing venture "because we're so invested in it already; we just have to try harder you see!"
Maybe part of the idea, because the bit about targeting low-end phones was completely stupid from the beginning. It was launched at the same time that Nokia was crashing and burning while similarly targeting "emerging markets" with obsolete phones.
This was pointed out right away, and they just shrugged. There was (and is) a feeling that a lot of Mozilla employees are just looking for excuses to hack on something fashionable; that's a natural geek instinct, but an effective leadership should be in place to crack the whip when people go astray.
This really stood out for me as well. My impression was that they used it as a scape-goat for not having to immediately deliver a completely polished experience.
I mean... Who's going to be paying for a phone with top-tier hardware when the software limits it to do less than most Androids out there... since ever? No-one would buy that phone. So it would be impossible to get a hardware vendor to fund such a venture.
If they (at first) targeted lower ends phones, chances of getting something out would improve. And they did get something out! So that part worked.
Obviously from there on they should have made improvements, and when the software platform had become good enough to sell itself, you should expect it on higher tier phones too. That's at least how I envisioned that they planned to execute, which IMO wouldn't have been a terrible plan if they had followed up.
But ofcourse, we saw what happened, and it was obvious at launch that this wasn't going anywhere anytime soon. Touché really. I would have a liked a third platform, based on open standards.
So, according to the history of past announcements, if I translate from Mozilla speak to normal English, Gecko will be abandoned in March 2017.
"Gecko is being abandoned."
"But their replacement, Servo, isn't ready yet!"
"That's true, but WebKit is and they already have a WebKit-based browser."
If you don't want your comment considered in the context of the conversation you replied to, you can make a top-level comment instead.
I think it's more likely they'll make Gecko/Firefox into community led projects and dissolve Mozilla Corporation.
2) Firefox iOS uses WebView not by choice, but because of Apple's App Store restrictions.