Some of the feature seems good, but to actually make it good will need writing a new FOSS web browser, with rather different internals. Some things that seems

Some of the feature seems good, but to actually make it good will need writing a new FOSS web browser, with rather different internals. Some things that seems to me to be good ideas, mentioned there, includes: split-screen, tab renaming, boosts (hopefully, they will be documented), DevTools. But, needing an accout seems a bad idea. A web browser should just as well be usable to display local HTML files even if you do not have an internet connection, too; and, to make it good should also need FOSS. I think many problem that Chrome does, although, they say that the dev tools is good. Well, making a new web browser will need also the web dev tools, in order to be good. Actually, I think that one thing to make a better one, will be that many things of extensions (e.g. user CSS, header overriding, etc) will be core features, and file formats and protocols will be extensions (some of which, such as HTTP(S), PNG, etc) will be included by default. (A few things will be built-in, such as the data: scheme, and the HTTP request/response model (but not implementation).) (Being able to write extensions in native code also would be very helpful, but most don't do that, or do it badly.)