| ▲ | flohofwoe a day ago | |
OTH all the complexity ends up baked into the browser where it will be frozen forever (even the shitty/overengineered ideas, like WebAudio). At least frameworks can be discarded and replaced when something better comes along. IMHO even HTML+CSS should be completely implemented outside the browser in the 'framework layer', but I guess that's not a very popular opinion among the more 'conservative' web devs ;) | ||
| ▲ | afavour a day ago | parent | next [-] | |
That would mean some shitty load times for even the most basic web site. But there is probably a world where what you’re describing is possible with WASM and Canvas. Would need to solve for accessibility though. | ||
| ▲ | Rygian a day ago | parent | prev [-] | |
If that means having an "HTML+CSS framework" that I could easily swap out for a "Typst framework" and publish my blog using Typst, then sign me up! Meanwhile, there's Typst bundles [1], still experimental, that implement the same idea backwards: convergint a Typst project into a set of output files (which can be HTML). | ||