my blog https://overreacted.io
bla
+3
-2
+3
-2
public/functional-html/index.md
+3
-2
public/functional-html/index.md
···
580
580
581
581
There's a few different ways we could express this JSON as "real" HTML. We could decide to render our application on the client-side *only*, in which case all we'll want is to emit a `<script>` tag for the bundle and another inline `<script>` with data:
582
582
583
-
```js
583
+
```html
584
584
<script src="bundle.js"></script>
585
585
<script>
586
586
const output = LikeButton({ color: 'purple' });
···
590
590
591
591
Or we *could* prerender the Client Tags to the "real" HTML for a faster first paint:
592
592
593
-
```js {1-4}
593
+
```html {1-4}
594
594
<!-- Optional: Initial HTML -->
595
595
<button>
596
596
Like
···
967
967
- [An evolution of SDUI pattern from top native apps](/jsx-over-the-wire/#sdui)
968
968
- [A way to create full-stack abstractions](/impossible-components/)
969
969
- [A language-level `<script>` and `fetch()` ](/what-does-use-client-do/)
970
+
- [A way to split a function across time and space](/react-for-two-computers/)
970
971
971
972
In this article, I've tried to show that they can also be thought of a functional, programmable, and composable version of HTML--with tags on both sides.