While I wouldn't normally link to a YouTube video in this context, KaiOS Technologies specifically reached out to TechAltar to provide him with details so he could cover the story.
It's likely that one of the reasons KaiOS decided to reach out was because of his July 2018 video[2] covering KaiOS, which has over a million views.
[1] https://www.youtube.com/watch?v=_UPk3mpcDP4 [2] https://www.youtube.com/watch?v=OA_g2bQgOXY
> As such, it allows re-licensing. MPL software can thus be converted into a copyleft license such as the GPL, or to a proprietary license (example:KaiOS).
Which means user authentication apps will not come any time soon, like Authy (Authenticators), Bitwarden (Password Managers) or BankID (Swedish) (Identity Verifiers).
I can't imagine Mozilla putting in the resources without also open-sourcing all the things.
I'm not sure what's actually interesting about this partnership, it seems obvious, but one thing I think is a huge problem is that they're mentioning Gecko so much -- they should be trying to move to Servo as fast as possible.
There is already a project called servonk[0] that shows this might be very possible.
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
"Currently, we are prioritizing apps for QA that use KaiAds for monetization. Visit the KaiAds website to learn more.
After you have integrated KaiAds, go through this checklist."
I wonder if there's a way to pay to opt out of their ads though...
I've bought a ZTE Open[0] back when FFOS was made since i am in general a fan of Mozilla (despite their missteps now and then) since before Firefox was a thing. The phone was a disaster - applications were very slow, everything was sluggish and in some cases i lost calls because the UI had frozen due to swapping or whatever it was doing.
Now, you might say that it was a low end device, but here is the thing. Years before that i had a Nokia 6600 [1] which has literally less than 10% of the resources ZTE Open has, yet it was able to run multiple applications without a breeze (it was the first time i ran an IRC client on a phone) and even had several 3D games (which, imagine that, used software rendering despite the phone's limited CPU power).
(and of course there were PalmOS devices that were running on even weaker hardware yet they provided UIs so responsive that put even the fastest Android to shame -- but i have very limited exposure to those to judge properly)
Nokia 6600 puts in perspective how awful Android is nowadays, let alone FFOS that couldn't even manage to remain literally usable with more than ten times the resources.
webOS in 2009 isn't even a comparison for a few important reasons.
* They were primarily RAM restricted at only 256mb.
* The then new v8 engine was about 4x slower than the current iteration (not to mention using much more RAM). Webkit is also much, much faster today
* They used QtWebkit -- a slow and grossly outdated version of webkit that offered bad performance even back then.
* There team seemed to have zero experience in actually using and optimizing a Linux OS.
A single-core 1GHz A5 chip was a crazy idea. The ZTE Open C came out 6 months later *at the same price8 and had a better screen (480x800 instead of 320x480), twice the RAM (512mb instead of 256mb), and probably close to 4x the CPU power (2x A7@1.2GHz instead of 1x A5@1GHz -- for reference, AMD runs an A5 as their security coprocessor on their x86 chips).
The ZTE Open was simply a mistake. It would have been a mistake no matter the OS or native vs web apps.
- ease of development
- leveraging gains in the platform development
At this point, the web is already the biggest app store the world has ever seen. FFOS succeeded in one of the most difficult areas of building a new platform -- getting companies to write progressive web apps that ran on the phone. I even spent time writing little utilities, a tinder clone, and an instagram clone for the platform.
There are at least 3 big companies with huge dedicated teams to making that platform better and faster. Slowness can definitely be an issue but that's a lot more solvable than a dearth of applications or a lack of open interest in improving the platform. Optimization is a long-tail problem, and it's clear by android's dominance and the progressive slowing of apple software every year that you just have to be good enough, but hardware goes a long way to help.
Even more than this the biggest problem was the market FFOS was aimed for didn't give FFOS time to go down the optimization path. You can mask inefficient software with beefy hardware, and I actually had two firefox phones that worked wonderfully -- the Flame[0] and the Fx0[1]. Those two phones only scratched the surface of how powerful the hardware could be, and I didn't have any of the problems you mention. I still have 2 (!) FX0s in my closet somewhere.
[0]: https://wiki.mozilla.org/Firefox_OS/Flame
[1]: https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Phon...
Looks like servo might only be a breeding ground for ideas after all.
[0]: https://en.wikipedia.org/wiki/Servo_(software)#Relationship_...
I don't think KaiOS will be. It seems that Google is one of the main investors in KaiOS Technologies[0][1].
[0]: https://www.kaiostech.com/google-leads-seriesa-investment-ro... [1]: https://www.crunchbase.com/organization/kai-technologies#sec...
Maybe KaiOS/Mozilla's (now defunct) mobile department in particular can't, but companies can definitely survive on high end products only.
If an analysis of FFOS being bad depends on (in my opinion) running good-enough software on terribly slow hardware, the wrong question is being answered.
The question on my original message was rhetorical - of course it doesn't have to be a platform built around a web browser. That is a massive waste of resources that could be used for a ton of other things.