No video comparisons, nothing?
Also why dont they release this for mobile?
Flow Browser – A parallel, multithreaded HTML browser
21–30 of 48 posts
Re: Flow Browser – A parallel, multithreaded HTML browser
#22Earlier quoted context omitted.
Nevertheless perhaps it has a chance to conquer the market if it's so good otherwise. I love free software but have to admit a browser (or whatever an app) doesn't have to be open-source for this.
and then it takes over, does whatever it wants, and now you've got IE6 again. open source is our insurance policy against the next IE6. One may come again, but we can head it off at the pass before it dominates the market.
While I agree with you, open source chrome didn't really help push for anything good.
Thanks to chrome we now have AMP and basically total web domination by the GOOG company.
Re: Flow Browser – A parallel, multithreaded HTML browser
#23Will it have its lunch eaten by tools and techniques for lightweight web apps on Webkit/Quantum? Svelte made a headstart making 200k laggy Webkit devices snappy again while these guys will be selling proprietary licenses.
Frameworks like Svelte focus on reducing the time spent running JavaScript. This project focuses on reducing the time spent on layout and rendering.
Theoretically they'd complement each other, but in practice I imagine UIs for super-resource-constrained set-top boxes are already written in pretty efficient JavaScript.
Re: Flow Browser – A parallel, multithreaded HTML browser
#24Earlier quoted context omitted.
Nevertheless perhaps it has a chance to conquer the market if it's so good otherwise. I love free software but have to admit a browser (or whatever an app) doesn't have to be open-source for this.
and then it takes over, does whatever it wants, and now you've got IE6 again. open source is our insurance policy against the next IE6. One may come again, but we can head it off at the pass before it dominates the market.
As opposed to having Chrome, which contributes to Google's ownership of the whole internet? Google does what it wants and developers write for Chrome. Users of Firefox find websites that won't work because someone used some Chrome extension to the spec.
People writing software are no match for behemoth.
Re: Flow Browser – A parallel, multithreaded HTML browser
#25Earlier quoted context omitted.
and then it takes over, does whatever it wants, and now you've got IE6 again. open source is our insurance policy against the next IE6. One may come again, but we can head it off at the pass before it dominates the market.
As opposed to having Chrome, which contributes to Google's ownership of the whole internet? Google does what it wants and developers write for Chrome. Users of Firefox find websites that won't work because someone used some Chrome extension to the spec. People writing software are no match for behemoth.
At the very least Chrome allows forking (and has happened in practice multiple times), so a competitor need not start from scratch. That's will always be an insurance.
Re: Flow Browser – A parallel, multithreaded HTML browser
#26Earlier quoted context omitted.
As opposed to having Chrome, which contributes to Google's ownership of the whole internet? Google does what it wants and developers write for Chrome. Users of Firefox find websites that won't work because someone used some Chrome extension to the spec. People writing software are no match for behemoth.
At the very least Chrome allows forking (and has happened in practice multiple times), so a competitor need not start from scratch. That's will always be an insurance.
There's hardly any point forking if most or all websites are tested for Chrome and its idiosyncrasies, and don't work well on other browsers. We have seen that playing out for sometime.
Re: Flow Browser – A parallel, multithreaded HTML browser
#27This is almost certainly going to be proprietary, so it's nothing to hold your breath over. Ekioh makes enterprise software for set-top boxes. They do know their browser rendering, though: they stripped Webkit down to have a 24mb memory footprint.
So this is a closed-source webkit fork?
Nothing to see here, moving on then :)
Webkit a comparably easy target to strip down and embed elsewhere. See Apple watch.
Re: Flow Browser – A parallel, multithreaded HTML browser
#28This is almost certainly going to be proprietary, so it's nothing to hold your breath over. Ekioh makes enterprise software for set-top boxes. They do know their browser rendering, though: they stripped Webkit down to have a 24mb memory footprint.
So this is a closed-source webkit fork? Nothing to see here, moving on then :) Webkit a comparably easy target to strip down and embed elsewhere. See Apple watch.
> developed a clean room browser architecture
Implies that this isn't a webkit fork, they started from scratch.
See also: https://twitter.com/FlowBrowser/status/1200098712816631809
Re: Flow Browser – A parallel, multithreaded HTML browser
#29Earlier quoted context omitted.
and then it takes over, does whatever it wants, and now you've got IE6 again. open source is our insurance policy against the next IE6. One may come again, but we can head it off at the pass before it dominates the market.
While I agree with you, open source chrome didn't really help push for anything good. Thanks to chrome we now have AMP and basically total web domination by the GOOG company.
> Thanks to chrome we now have AMP
How does Chrome enable AMP?
(Disclosure: I work for Google, speaking only for myself)
Re: Flow Browser – A parallel, multithreaded HTML browser
#30I 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).