News for hackers. Stuff that matters.

A comment on Multi-process Firefox brings 400-700% improvement in responsiveness. Parent comment

Re:Multi-process Firefox brings 400-700% improvement in resp... by srean on Wednesday September 07, 2016 @12:18AM (#12440943)
With applications written in javascript ? Stateful on the client side alone or stateful on both sides ? It wont be safe to assume that state is persisted transparently on the server side. May be they just cache it for a while.

To make this work reliably would be quite difficult.

[ Parent | on HN ]
Re:Multi-process Firefox brings 400-700% improvement in resp... by derefr on Wednesday September 07, 2016 @01:08AM (#12441074)
You could be really conservative: only assume statelessness if the page has no <form> elements and has no calls to the XMLHTTPRequest API (or window.eval).

Or you could be really conservative: only assume statelessness for pages without forms and without any Javascript. (These do exist!)

[ Parent | on HN ]
Re:Multi-process Firefox brings 400-700% improvement in resp... by srean on Wednesday September 07, 2016 @07:22AM (#12442356)
> These do exist

We have seen things people wouldn't believe. Webpages without any Javascript. Webpages using correct http responses. Watched C-beams glitter in the dark near the Tannhauser Gate. All those moments will be lost in time, here come the transpilers

[ Parent | on HN ]