Author invents a programming language where the code is server-side JSX tags ("Early World") and the runtime evaluation is divided into as multiple lazily-evaluated stages ("Late World") in the browser.
Author unfortunately fails to justify or provide a demonstration that justifies the increased complexity over current methodology.
Interesting exploration of an unexplored space, but should be more concise (and use either better or no attempts at humour).
> In the Early world, you dissolve all the Early Components with interpret. This gives you a string that represents how to finish the computation in the Late world: [code]
> In the Late world, you parse that string, load the references, and then dissolve the Late Components with interpret. That leaves you with a tree of Primitives: [code]
> Finally, those Primitives are ready to be turned into DOM or some other format: [code]
Author isn't inventing a new language. They are "inventing" react server components. It's not unexplored, they are teaching the reader how server side rendering in react works.
Author unfortunately fails to justify or provide a demonstration that justifies the increased complexity over current methodology.
Interesting exploration of an unexplored space, but should be more concise (and use either better or no attempts at humour).
> In the Early world, you dissolve all the Early Components with interpret. This gives you a string that represents how to finish the computation in the Late world: [code]
> In the Late world, you parse that string, load the references, and then dissolve the Late Components with interpret. That leaves you with a tree of Primitives: [code]
> Finally, those Primitives are ready to be turned into DOM or some other format: [code]