The trick, of course, is to do this without slowing down development. It's tough, but I think it's doable.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
WebAssembly could allow us to ship our own layout engines and such with the “right” lower level APIs. So many things could have been WebAssembly modules / plugins.
-
The scare quotes are the most important part of that tweet.
End of conversation
New conversation -
-
-
chrome: jUSt FORk It dUDE
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
OpenDoc!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This would be a lot easier in something other than C++ where basic design decisions don't infect your entire application.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The LLVM of browser engines?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Would be interesting to have an easily pluggable css engine. (For example to make a HTML → PDF library). Weasyprint for example reimplements the whole css stack. Don’t know if one could use stylo for that. (Besides weasyprint being implemented in python).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Oh yes should is here again
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I’m working on such browser. Now it has pluggable network layer which allows users to add custom networks support, like IPFS, from userland. The main issue there I see is the “hell of engines”. Still thinking about the solution, it could become a real trouble.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.