The thing is, the browser needs the tree, but the server doesn't really need the whole tree.
Building the tree on the server is usually wasted work. Not a lot of tree oriented output as you make it libraries.
Building the tree on the server is usually wasted work. Not a lot of tree oriented output as you make it libraries.
> Not a lot of tree oriented output as you make it libraries.
That was actually the point of my library, although I must admit, I haven't implemented actually streaming the HTML output out, before having composed the whole tree. It isn't actually that complicated, what I would need to implement would be to make part of the tree immutable, so that the HTML for it can already be generated.
https://github.com/urweb/urweb
http://www.impredicative.com/ur/
Needless to say it wasn't very practical. But there was one commercial site written in it https://github.com/bazqux/bazqux-urweb (the site still exists but not sure if it's still written in ur/web)
Ur/Web is not very practical for reasons other than type safety: the lack of libraries and slow compilation when the project gets big. The language itself is good, though.
Nowadays, I would probably choose OCaml. It doesn't have Ur/Web's high-level features, but it's typed and compiles quckly.
What do you think about Typescript? I mean it's unsound but - it sounds like an ok compromise
Personally, I'd prefer a fully typed language.