With any windowing system running so slow, how will porting all that to JavaScript improve matters?
However let's turn that the other way: One of the Pi's cooler features is its digital I/O's. Will this mean they'll add GPIO support to Firefox OS then? And maybe to Firefox, too?
"This web site wants to control your hand-soldered peripherals. [Allow] [Don't allow]" - Cool!
I didn't notice any part of that being "so slow". Sure, the system UI isn't quite as snappy as it could be, but Mozilla has several months to work on it. Usually most of the visible performance optimizations happen near then end, and I bet they'll get it pretty smooth.
The actual Broadcom port of 4.0? I haven't seen anywhere that it's actually available to acquire (which is too bad, because it would be quite useful for the project I'm working on).
There's a lot of work going on performance-wise right now, especially on the gfx side. We should be seeing some serious performance benefits soon; honestly, I'm amazed that WebGL apps run as well as they do right now -- they're getting a huge boost soon.
FxOS could very well add GPIO. Bluetooth is currently in the works for FxOS v1 (it'll be certified apps only for v1, but it should expose RFCOMM sockets all the way up through JS, so the potential is there), and host-mode USB has been talked about for later versions. Basically, the idea is "if it's the phone, we should be able to access it". As things branch out, hopefully that'll morph into "if it's on the hardware, we should be able to access it"
Comments
With any windowing system running so slow, how will porting all that to JavaScript improve matters?
However let's turn that the other way: One of the Pi's cooler features is its digital I/O's. Will this mean they'll add GPIO support to Firefox OS then? And maybe to Firefox, too?
"This web site wants to control your hand-soldered peripherals. [Allow] [Don't allow]" - Cool!
I didn't notice any part of that being "so slow". Sure, the system UI isn't quite as snappy as it could be, but Mozilla has several months to work on it. Usually most of the visible performance optimizations happen near then end, and I bet they'll get it pretty smooth.
Indeed, the Android port is actually faster than my phone.
The actual Broadcom port of 4.0? I haven't seen anywhere that it's actually available to acquire (which is too bad, because it would be quite useful for the project I'm working on).
Well, I meant from the video the developer put up - I'd love to get a hold of it too (would like to try splitting HDMI and putting Android over many).
There's a lot of work going on performance-wise right now, especially on the gfx side. We should be seeing some serious performance benefits soon; honestly, I'm amazed that WebGL apps run as well as they do right now -- they're getting a huge boost soon.
FxOS could very well add GPIO. Bluetooth is currently in the works for FxOS v1 (it'll be certified apps only for v1, but it should expose RFCOMM sockets all the way up through JS, so the potential is there), and host-mode USB has been talked about for later versions. Basically, the idea is "if it's the phone, we should be able to access it". As things branch out, hopefully that'll morph into "if it's on the hardware, we should be able to access it"
Telefonica will use Firefox OS on feature phones with specs that are below Raspberry Pi.
There is a difference between running Ubuntu and just running a little OS using Linux kernel.
X on Raspbian is not GPU accelerated. Since the CPU (but not the GPU!) is a bit anemic even by current ARM SoC standards, that's a big deal.
Firefox OS is accelerated, running on top of OpenGL ES. :)