Firefox OS Pivot to Connected Devices
blog.mozilla.org
blog.mozilla.org
You might want to check out claws-mail. You get notification via a plugin (on debian/ubuntu, the plugin is in another package, but it's very easy to get).
Take a look at https://nylas.com/N1
> it works like a traditional mail client.
Except it's not just a client.
Unfortunately Mozilla [ com | org ] have shackled themselves to Googlemail internally, so seem to have abandoned any aspirations to fight for openness in the domain of e-mail.
I'm not really familiar with Mozilla's internal org - so I have just had a look at Mozilla Corp's leadership page[1]: there is an SVP for Firefox, and an SVP for "Connected Devices" - who authored the linked article. There are no other SVPs: which suggests MozCorp consider connected devices to be as important as Firefox . It looks like Thunderbird is orphaned and has no champion within Mozilla (I don't think the Firefox division wants it).
So it looks like it boils down to org structure & politics (for the lack of a better word): Thunderbird is dying because it's an unwanted step-child, and FirefoxOS is revived because it's the biggest thing going on for an entire division/department ("Connected Devices")
We will explore and prototype new use cases in the world of connected devices as an open source project with a clear focus on the user benefit and experience.
..yada yada, sounds like a buzzword filled marketing crap with no substance whatsoever[1].
0. https://www.linux.com/news/embedded-mobile/mobile-linux/8180...
1. https://media.licdn.com/mpr/mpr/p/5/005/04f/263/04c1eb8.jpg
Third party desktop mail clients are just not a killer feature for the vast majority of users. IoT may not be a winner for various reasons, but I'm sure it can't be easy trying to figure out where to go from here. (let's face it, IoT is going to be the same locked-down, vendor-specific experience that Internet tv has become; and without manufacturing a must-have device or buying out a manufacturer of one, why would Mozilla win in that field?)
And yet somehow Firefox manages to run WebGL a lot worse than Chrome and Opera (Blink/V8 based browsers)...
Browsing is quickly becoming a thing most people do on (only) their phone and email is for more and more something you do on the web.
If Mozilla keeps focusing on these two aspects they will start to cater to a niche market and lose the ability to influence the Internet at large.
Yeah, I would say that I agree with that, but about a month ago, I have joined a tech team of an NGO that works with a lot of sensitive data.
Convincing them to use Enigmail with Thunderbird is hard. Convincing them to use Enigmail with Thunderbird even though you are not sure what will be the future of Thunderbird is just plain frustrating.
And no, there's absolutely no alternative that could handle all three desktop OS's (Windows, Linux, OS X), attachments, and other things that are completely necessary to have a safe, encrypted communication.
There's absolutely no alternative what so ever. I really wish that some cool project (like LibreOffice) takes over Thunderbird and makes it great, but the odds for that are practically non-existing.
If you want to try Firefox OS, even with no carrier support, take a look at https://firefoxos.mozilla.community/devices/ which lists supported devices.
"Thunderbird and Firefox are interconnected in a few different ways. They are connected through our technical infrastructure. Both use Mozilla build and release systems. They’re connected through the sharing of some pieces of technology. The time has come when it is no longer effective for Thunderbird and Firefox to keep sharing the same technical infrastructure. Firefox and Thunderbird have diverging needs."
https://blog.lizardwrangler.com/2015/12/03/thunderbird-updat...
Li Gong, former executive in charge of Firefox OS,[4] also has a startup focusing on Firefox OS smartphones.[5] Having raised $100 million and poached dozens of Mozilla employees, he is looking for even more funding.[6]
[1] http://www.cnet.com/news/mozillas-new-cto-javascript-firefox...
[2] http://www.cnet.com/news/firefox-os-in-flux-as-mozilla-loses...
[3] http://www.cnet.com/news/startup-aims-to-make-home-devices-s...
[4] https://www.linkedin.com/in/ligongcn
[5] http://www.cnet.com/news/startup-lands-100-million-to-challe...
[6] http://www.cnet.com/news/startup-acadine-picks-up-the-torch-...
http://www.fiercemobileit.com/story/acadine-undeterred-effor...
I think companies should understand if you don't have money for just spending on products like these.then don't start them.because it will make you look like idiot. Maybe 25 year from now you can run Gecko(what was their engines name?) On low powered chip.but today?no way.
Mozilla, get your act together, you are burning through a lot of good-will lately.
"Dropping the idea of browser stuff" was never a goal of Rust.
"Here lies Martin. Not dead, just pivoting to connected devices."
EDIT: Forgot to mention Tizen as well.
However there are lots of IoT vendors that offer first class support for Java on their SDKs.
There were lots of talks at JavaONE 2015.
Also there are car makers like VW exploring JavaFX for their infotainment systems.
http://www.bredex.de/blog_article_en/research-into-the-use-o...
Gluon is anyway taking care of it.
EDIT: Changed a bit the content.
What they need to do is work on their browsers, and specifically:
1. Ship Electrolysis ASAP, so Firefox is once again as technically good as Chrome and others
2. Add support for syncing with Chrome and IE if possible, to smooth transition for mainstream users
3. Fund Servo as much as possible, and get it ready to ship it in both desktop and mobile browsers as soon as possible
4. Get the marketing people to work on a strategy to market Servo to get the #1 browser market share spot again
5. Stop eroding their reputation with dumb stuff like the Pocket and Telefonica integrations. If they do something to make money, clearly state so and make sure it's harmless to users and trivially disabled. Then, market their reputation as a trustworthy non-profit much better.
If they REALLY want to do a mobile OS, just work together with Cyanogen on an Android distribution with added/better HTML app support, instead of inventing their own crappy thing.
By the way, it is bizarre that they do not mention their death on the website (http://www.matchstick.tv/overview/company-news/). On their Kickstarter article, their wording is a bit unclear, but it does seem like they have stopped working on Matchstick (https://www.kickstarter.com/projects/matchstick/matchstick-t...).
What people are implicating is their strategy. As others have mentioned, they don't seem to lead entry into any space, and therefore their presence in the space is constantly in the vein of catching up. Thus far, the only clear reason I've ever heard them mention is the same "open web standards" argument. Obviously this approach is valid, but with their browser success they should know better than anyone that you cannot overtake Goliath with open standards if no one is using your product.
Lo and behold, they've apparently shown a product at MozCon that Google and Apple have already bet a ton on and released compelling consumer offerings for. Regardless of how impressive the APIs and UI may be, history repeating itself here.
Aaaaany day now.
Could it also be a fairly static non vendor customized and hence upgradable OS also? Most Smart TVs are never updated after all
Consistent platform could be a decent benefit for the markets where Firefox OS makes sense though.
Along with the usual problems of "smart" (spyware) devices, the non-updatability of IoT devices is a time bomb.
We already have a problem with firmware based on very-old Linux kernels; shipping devices with known kernel exploits should be automatic liability for any damage the device does. It's willful negligence.
As Dan Geer says[1], embedded devices need to either be updated or have a limited lifespan. We cannot allow a situation where common consumer IoT devices are both immortal and unfixable.
Besides, Gecko is still relevant, and will continue to be for quite some time. Mozilla and Google appear to have a good working relationship when it comes to web standards, and new standards are only signed off when at least two browser vendors (or rather, browser engine vendors) implement the proposed functionality.
> "everyone else supports webkit prefixed CSS properties on mobile"
The question is, how often are these directly used? Isn't the common pattern to target modern features without universal support through polyfills and solutions like Babel nowadays?
Which has < 1% marketshare, and is largely ignored by web developers. I didn't say it didn't exist, I said it wasn't relevant. :)
> The question is, how often are these directly used? Isn't the common pattern to target modern features without universal support through polyfills and solutions like Babel nowadays?
Plenty often enough that users refused to use browsers without support for webkit prefixed properties. People who have a clue may well use polyfills and Babel and autoprefixer, but plenty just do copy/paste coding.
There is also ChromeOS and its similar to WebOS and FirefoxOS and runs on low spec notebooks just fine.
There is little performance difference between Android and FirefoxOS, for both you need at least 512MB RAM (memory), so that it works without lags.