Note that the 2D page is nowadays often an entire application instead of just a bunch of text and images. If the protocol to access a machine in a dumb terminal

Note that the 2D page is nowadays often an entire application instead of just a bunch of text and images. If the protocol to access a machine in a dumb terminal fashion becomes an application programming environment of its own, maybe you need dumb terminals to access that protocol in turn. Then there is the bloat issue. If websites were designed as lean as news.ycombinator.com, there would be no need for mighty. But they aren't. Instead we have js framework upon js framework, lots of tracking, ads, etc... you can make lean stuff using web technology, but you can't make it using the most popular frameworks. elm had this precise problem. They made their library really fast and really lean and people were like shrug, while flocking to the popular and bloated frameworks. IDK it seems to me that Chrome and evergreen browsers have led to a stagnation in innovation of the browsing model. I feel like Mighty is a breath of fresh air. That being said, should Mighty ever become powerful, they'll likely benefit from funding maintainers to make js frameworks even more bloated so that even more people use their product... which means that they might do it. On the other hand, large user bases using products like Mighty might be a wake up call to website and browser developers that lean-ness is a real user demand, and maybe fixing it on their end, similar to how people taping up webcams led to builtin mechanical shutters.