Trying to shoehorn a performance hungry HTML5 OS on low-end phones was a complete waste of time.
Trying to shoehorn a performance hungry HTML5 OS on low-end phones was a complete waste of time. Just read this review of the $35 Firefox phone [1]: it's completely unusable to the point that even typing is difficult. What an embarrassment. I bought the mid-spec Flame developer device out of curiosity, and it's not much better. Everything feels slow, sluggish and unresponsive. Even Android 2.x was better. My quad-core i7 desktop still occasionally struggles to render the latest and greatest HTML5 stuff at 60 fps. How on earth do they expect a phone to do the same? [1] http://arstechnica.com/gadgets/2014/10/testing-a-35-firefox-...
Posted by veeti on May 25, 2015, 7:04 PM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
Trying to shoehorn a performance hungry HTML5 OS on low-end phones was a complete waste of time.
Trying to shoehorn a performance hungry HTML5 OS on low-end phones was a complete waste of time. Just read this review of the $35 Firefox phone [1]: it's completely unusable to the point that even typing is difficult. What an embarrassment. I bought the mid-spec Flame developer device out of curiosity, and it's not much better. Everything feels slow, sluggish and unresponsive. Even Android 2.x was better. My quad-core i7 desktop still occasionally struggles to render the latest and greatest HTML5 stuff at 60 fps. How on earth do they expect a phone to do the same? [1] http://arstechnica.com/gadgets/2014/10/testing-a-35-firefox-...
Comments (0)
No comments yet. Start the discussion.