←back to thread

Web Browser Engineering (2021)

(browser.engineering)
770 points MrVandemar | 1 comments | 15 Oct 24 09:42 UTC | HN request time: 0.204s | source
Show context
currygen ◴[15 Oct 24 13:35 UTC] No.41848445[source]▶
It's refreshing that browser engineering seems to become a "trend" now. The ecosystem is quite sparse with basically only Google, Apple and Mozilla defining it. I'd like to see forward into a future with more independent browser engines.
replies(4): >>41848575 #>>41848648 #>>41848756 #>>41850985 #
pmarreck ◴[15 Oct 24 14:06 UTC] No.41848756[source]▶
Or perhaps an entirely new platform/protocol, since this one is completely saturated with complexity at this point.
replies(3): >>41851754 #>>41854366 #>>41862168 #
niutech ◴[16 Oct 24 00:09 UTC] No.41854366[source]▶
Why not go back to WAP & WML? ;)

There is QML (see https://www.canonic.com) and Gemini (see https://gmi.skyjake.fi/lagrange/) as alternatives.

replies(1): >>41855118 #
1. pmarreck ◴[16 Oct 24 02:46 UTC] No.41855118[source]▶
These are fascinating!