@Skoll3 > WebKit ain't exactly hot or works well outside of walled garden of Apple ecosystem
Works well enough to have been a daily driver for me for the past 3+ years, in fact websites these days probably work worse on firefox given how much it's user share plummeted into irrelevance. And "hot" has nothing to do with being technically good but everything to do with marketing, which is often a tool to make something worse look better than the rest.
> Would not hypothetical tailor-made native application achieve that specialized use case that does not involve chasing Google at this point?
WebApps should be ran into a dedicated browser anyway, this way you can control updates or even deploy your own fork without caring about the remote server. Haven't used it but https://github.com/sonnyp/Tangram might be going in that kind of direction.
> There is some hope that Flow browser is not vapourware
I forgot it was even a thing, I care once there is running code.
@Skoll3 WebKit exists, it's just that nobody does marketing about it except Apple via Safari even in it's embedded devices space (it's either a chromium fork or webkit anyway, chromium being a pain to maintain since you'll probably be forced to do your own fork).
And I'd say it's still possible to write another web engine, specially for some devices / use-cases where all the desktop bullshit doesn't matters, but you need to have a team, great leadership and time. Team and leadership that you're going to need for a chromium fork btw, if it's too few devs they're going to burn out because there is 0 fun in chasing after Google's whims and you're going to have some deal breakers.