3 ms·

Here's an analysis of the Flow Browser: https://thereshouldbenored.com/posts/flow-new-engine/ https://thereshouldbenored.com/posts/flow-new-engine/ by browser s

by tpmx 6y ago

Here's an analysis of the Flow Browser: https://thereshouldbenored.com/posts/flow-new-engine/ https://thereshouldbenored.com/posts/flow-new-engine/ by browser standards/testing veteran gsnedders here on HN, from June. I cut out the juciest bit from the middle: > The answer is almost certainly it cannot succeed as a general-purpose browser. Indeed, they've said themselves (emphasis mine) ... Lots and lots of insightful commentary cut out, really do read it!

gsnedders 6y ago
Oh. Hi. :)
faitswulff 6y ago
I thought these paragraphs were particularly interesting: > When I have spoken to them, their approach has been significant: they've chosen what features to prioritize based on a chosen major website, and then attempted a complete implementation of those features. An example of this is that they only implemented HTMLTableElement in the recent past, despite having supported much of the HTML DOM for a lot longer. > Historically, many attempts at new browser engines have started by trying to systematically implement features per specification, only to find that no interesting site is yet functional even when the majority is done. By being vastly more selective and only implementing features when needed, they are undoubtedly cutting out many obscure legacy features unlikely to be used on any major site today.