Flow Browser – A parallel, multithreaded HTML browser

Re:Flow Browser – A parallel, multithreaded HTML browser by wtmt on Friday November 29, 2019 @05:08AM (#21663396)

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.

[ Parent | on HN ]

Re:Flow Browser – A parallel, multithreaded HTML browser by true_religion on Friday November 29, 2019 @07:34AM (#21663959)

It means we can’t end up in an IE6 scenario, where the caretaking company loses interest in developing the browser, and we are all stuck using old technology forever.

Someone can simply fork it, with all its idiosyncrasies, then build new versions with new features.

Do you want a browser that natively supports a language other than JavaScript? Chromium is a great starting point.

[ Parent | on HN ]

Re:Flow Browser – A parallel, multithreaded HTML browser by palashkaria on Friday November 29, 2019 @12:00PM (#21665433)

Well, I think the argument was more about Webkit, then Chrome itself. Even flow here does not use a JS engine written from scratch - they use SpiderMonkey.

PS: As a webkit-based Chrome alternative, Brave browser does really well.

[ Parent | on HN ]

Re:Flow Browser – A parallel, multithreaded HTML browser by ksec on Friday November 29, 2019 @03:09PM (#21666538)

Interesting they choose Spidermonkey over Webkit's JS Engine .

I could sort of understand not choosing v8 which is now quite bloated as it is also optimising for lots of other things, but Spidermonkey?

[ Parent | on HN ]

Re:Flow Browser – A parallel, multithreaded HTML browser by Terretta on Saturday November 30, 2019 @06:02PM (#21672624)

Remember when you could test on WebKit, to hit both Chrome and iOS, with OSX Safari as a bonus?

[ Parent | on HN ]