Comment by classichasclass
8 years ago
Maybe it's the curmudgeon in me, but while I salute the ingenuity in this UI/UX idea, I think we need a new kind of browser engine at least as much as a new kind of browser interface, perhaps more.
I used to worry that WebKit would eat the world, for awhile Trident did eat the world, and now I worry about Blink.
Maybe you should take a look at Servo from Mozilla: https://servo.org/
A few things from Servo were integrated in Firefox 57. But the project is far from complete I think.
I'm aware of Servo. Servo is neat to play with, though it's pretty bad with older legacy HTML pages. Also, I'm not sure how likely Mozilla is to develop it into a product; it seems more like a testbed for later Gecko evolution (which, to be sure, is still a good thing).
> I'm not sure how likely Mozilla is to develop it into a product
It's unlikely to become a standard desktop browser, but the roadmap [1] does mention investigating options like a standalone mobile browser [2] or perhaps to be used embedded in an app, e.g. for packaged web apps.
[1] https://github.com/servo/servo/wiki/Roadmap [2] https://github.com/servo/servo/issues/20855
Firefox already includes parts of Servo, so it’s not a question of “how likely” it is to be used in production. https://en.wikipedia.org/wiki/Quantum_(Mozilla)
6 replies →
The only thing I worry about is high complexity. If its so complicated, that only a few megacorps can implement it, it should be abolished. That would especially mean to scrap most web standard concepts and replace it with more general concepts.