> Maybe a future Firefox OS phone will run a new processor that was specifically designed to execute JavaScript. I haven't heard of any such plans, but that wo

> Maybe a future Firefox OS phone will run a new processor that was specifically designed to execute JavaScript. I haven't heard of any such plans, but that would be fun. Ah, the good (?) old days of the Lisp machine... > Any sufficiently complex UI toolkit contains an ad hoc, informally specified, bug-ridden, slow implementation of half of HTML and CSS -- and then probably contains a full Web browsing engine, too. Let it be said that the Mwcampbell Law was first enunciated on Hacker News on the Ninth of July, 2013. > Can you explain why you think the Java storage APIs are ill-suited to mobile devices? Generally, it's a set of simple things. The File API, for instance, should forbid execution of any I/O call on the UI thread, or on any high-priority thread, as the duration of any I/O call is unbounded (Dalvik can be executed in a "strict mode" that prevents I/O calls on the UI thread, which is good, unfortunately that's not the default mode). Also, the default manner of doing any copy with the File API is a read/write loop, which is very inefficient in terms of memory copies, especially when Linux offers in-kernel copy. etc.