241–250 of 276 posts
Can you Mozilla guys focus on making it so that HTML5 apps can install from web pages with an Install button and then show up on the home screen like a normal app? Please. So that HTML5 developers don't have to rely on people creating bookmarks or typing web addresses and can give users a similar experience as native.
Earlier quoted context omitted.
Any developer version that we could buy? I don't mind if we have to pay more. Need to test this for Burma market. Edit: Didn't read carefully. You already mentioned that developer versions would be available worldwide soon. Any mailing list to subscribe for the announcement?
> Any developer version that we could buy? Like all Mozilla projects, this is developed completely in the open. You can get an original Galaxy Nexus and flash it over to the latest nightly relatively easily. It probably works on other phones, but the nexus is what they gave out at JSConf so that's what I use. ;) https://developer.mozilla.org/en-US/docs/Mozilla/Boot_to_Gec...
Surprised that even the tech community doesn't understand the significance of this.
I apologise for writing a long post - I have not time to write a short one There is a reason MBAs are taught market analysis. Its important to position your product for maximum effect (usually maximum profit, but that may not be the case here) The arguments for FirefoxOS seem to be 1. It's OSS 2. It's Web-technologies only 3. It's aimed at the "emerging" markets' mobile users 4. It runs on cheaper hardware better tha…
>1 and 2 are great. And no-one but us cares, except in 20 years when no child >has even seen a line of code because OSS gets wiped out as all PCs are replaced by mobile devices. While these guys are off saving the world from the evils of proprietary software, is it ok if I just get on with teaching my kids to program using Codea on our iPad? Edit: Ok, I too wish Apple devices in particular were a little less locked d…
If it weren't for these guys we'd be much worse off than we are today. Firefox single handedly dethrowned IE.
It's philosophical but in the same way that IE was at one time the best browser and quickly became the worst - it's not unimaginable that iOS will do the same.
I'm a pragmatist myself but if it weren't for folks like RMS and Mozilla there would be no voice at all for FLOSS. I don't agree with RMS on many things but it's vital that someone as unwavering as him pushes back.
Can you Mozilla guys focus on making it so that HTML5 apps can install from web pages with an Install button and then show up on the home screen like a normal app? Please. So that HTML5 developers don't have to rely on people creating bookmarks or typing web addresses and can give users a similar experience as native.
This already works.
That wasn't working last I checked.
I want a standalone operating system that runs on android hardware that gives me low level access, via unix commands and stdio, to phone functions.
So I don't want the javascript dialer, I want /usr/bin/dialer ... I don't want the javascript sms client, I want to run:
/usr/bin/sms --retries=4 --number 800-555-1212 > Hi Joe, I can't make it to the meeting^D ... sent.
So yeah. This article reminded me how much I want something very much like ffox OS, but for unix core principles, like stdio, and not for open web apps (nice as they are).
Earlier quoted context omitted.
webOS also suffered from execution issues (as a company). They were forever rewriting things under the hood as a fair number of things were duct-taped together. For example, they moved from a Java based solution to JS using v8 from webOS 1.x to 2.x. Hopefully, Firefox OS will not suffer from the same issues. And I would certainly like to hear more about the under-the-hood architecture. It's pretty eye candy but thing…
> For example, they moved from a Java based solution to JS using v8 from webOS 1.x to 2.x. Wow, you may want to do some basic checking on your assertions there: * webOS never used Java, Luna (webOS-to-be) was a skunkworks alternative to the Java-based Prima project. there was java stuff below from Prima, it was not the application core and was never made available to developers * webOS always used both Webkit and V8…
I was having a brain fart moment last night and meant node when I mentioned v8. Specifically, webOS 2.x+ shipped with node based services which replaced a lot(all/most?) of the java based services.
Earlier quoted context omitted.
Thanks for the comment, the WebOS question is one I see a lot. One of our engineers answered this recently on Quora, I hope it helps explain the differences a bit: http://www.quora.com/How-does-Mozillas-Boot-2-Gecko-compare-...
I might not be reading this right, but in my mind this summarized as: * WebOS added custom API's to handle parts of the phone hardware that are not web standard, for eg. phone calls, SMS * The Firefox project also added custom API's, except they are submitting them for standardization as web interfaces Why not just implement the WebOS API's and thus make them a standard, or are they considered flawed in some way that…
This would have been great if webOS was in a form ready to be adopted by Mozilla or someone else.
As it stands, open webOS has still yet to ship (hopefully soon). Most likely because it has taken this much time to untangle the non-open bits.
Even though I understand the reasons why, I'm still extremely bummed that this effort does not cover the Pre3 (or phone based device). Which means people will not be able to go back and retroactively fix a lot of the unfinished bits on the phones.
Earlier quoted context omitted.
webOS also suffered from execution issues (as a company). They were forever rewriting things under the hood as a fair number of things were duct-taped together. For example, they moved from a Java based solution to JS using v8 from webOS 1.x to 2.x. Hopefully, Firefox OS will not suffer from the same issues. And I would certainly like to hear more about the under-the-hood architecture. It's pretty eye candy but thing…
You might be interested in this: https://wiki.mozilla.org/B2G/Architecture
Those two things IMO were major things affecting webOS. Pretty much all the phone devices shipped with insufficient memory.
And given that Fx OS is JS, HTML etc. based, those things have a tendency to chew up a fair bit of mem. Throw in a JIT and suddenly you are in a mem swap situation (which is definitely not batt friendly).
So, yeah I would like to see more docs about how those are going to be addressed.
Earlier quoted context omitted.
Theoretically, a c-compiler could produce self modifying code.
Also, this theoretical c compiler could make use of implicit hints (like which variables to place together in memory), making it faster than JS (except asymptotically, when the JIT has run long enough to figure everything out). But the original point is basically right - one day JITs will be faster.
Can anyone try out:
http://anirudhjoshi.github.com/fluid_table_tennis/ on the Firefox OS and tell me its performance?