Re:Flow Browser – A parallel, multithreaded HTML browser
by touchpadder on Friday November 29, 2019 @07:07AM
(#21663846)
I don't think there's that much to improve with current browsers anymore. 8 years ago maybe. Now you have web workers with shared memory, typed arrays, GPU acceleration for canvas and CSS, web assembly with SIMD. It's already possible to utilise all the cores and GPU in 2D. Not even mentioning 3D WebGL and incoming WebGPU. Websites are fast enough already(with ad blocker).
[ Parent
| on HN ]
Re:Flow Browser – A parallel, multithreaded HTML browser
by The_rationalist on Friday November 29, 2019 @02:21PM
(#21666218)
I believe that document.write prevent a lot of parallelism.
Also as always, SIMD are underutilized.
There is also transactional memory, heterogeneous computing, SYCL, etc...
Re:Flow Browser – A parallel, multithreaded HTML browser
by touchpadder on Friday November 29, 2019 @08:18PM
(#21667865)
what do you mean document.write prevents parallelism? Who's using document.write for anything these days?
Re:Flow Browser – A parallel, multithreaded HTML browser
by The_rationalist on Saturday November 30, 2019 @02:14PM
(#21671653)
"Who's using document.write for anything these days?"
It doesn't matter if anybody use it, someone could use it, as such browser must adapt to this possibility and be performance constrained.
"what do you mean document.write prevents parallelism?" I don't remember the details but it force some critical browser operations to be sequential.