4 ms·
> Then for regular websites, have them deliver a HTML rendering engine I think this is a dealbreaker, that is simply too much data to have to send over every t
by phailhaus 4y ago
> Then for regular websites, have them deliver a HTML rendering engine
I think this is a dealbreaker, that is simply too much data to have to send over every time you want to load a webpage. It kills mobile immediately since most users have data caps.
- enos_feedler 4y agoThe idea is you cache a rendering engine. It just isn’t core in the system layer
- phailhaus 4y agoHaving to store all the different versions of rendering engines out there doesn't really solve the problem, because space isn't unlimited either. Imagine: Facebook just upgraded to v1.3.2 of PopularEngine but Google still lags at v1.3.0, now you have to store both!
- enos_feedler 4y agoWhat your saying is I should thank browserland for saving me all this disk storage. Looking over at you Electron
- phailhaus 4y agoYeah exactly. It's not great, because getting a website to work consistently across browsers is a bit of a pain, but it's gotten much better in recent years. Especially after IE was finally shut down.
- drowning-secs 4y ago
- wwweston 4y agoAs if that isn't enough, it isn't really the web if you can't "view source" and get roughly useful semantics for documents. The browser didn't beat out a handful of VMs because it was just another VM.