Show HN: Keep track of why you muted someone on X (github.com)
9 points by klntsky 3d ago 3 comments
Show HN: What Are People Doing Now? (whatpeopledoingnow.com)
2 points by mazzystar 8h ago 0 comments
Proposal for Standardized JSX
25 90s_dev 19 5/21/2025, 3:18:31 AM vanillajsx.com ↗
tl;dr:
My proposal transforms <foo bar={qux}>bla</foo> into { [Symbol.for('jsx')]: 'foo', bar: qux, children: "bla" }
It's self-contained, generic, doesn't rely on imports or globals, and avoids tag key collisions. It's the only way I can imagine it ever being standardized.
I currently use JSX for:
* Creating custom GUI view objects in https://90s.dev/os/
* Using JSX as a convenient & composable string-builder in Node.js via https://immaculata.dev/ when generating all my sites at build-time e.g. https://github.com/sdegutis/immaculata.dev/blob/main/site/te...
* Using JSX to generate plain DOM objects in the browser in some of my sites like https://github.com/sdegutis/minigamemaker.com/blob/main/site...
React used to transform it into React.createElement("foo", { bar: qux }, "bla")
Now it transforms it into import _jsx from "react/jsx-runtime"; _jsx("foo", { bar: qux }, "bla")
My proposal transforms it into { [Symbol.for('jsx')]: 'foo', bar: qux, children: "bla" }
It's self-contained and generic, doesn't rely on auto-imports or globals, and doesn't have key collisions.
It's the only way I can imagine it ever being standardized.
> 'children' are specified twice. The attribute named 'children' will be overwritten. ts(2710)
https://facebook.github.io/jsx/ is a mirage, apparently.
(Emphasis theirs.)
I like to create the HTML and CSS as I'd like it with test data, then just wrap that with <template> tags. Easy to preview without triggering function calls or pasting it into code.
Probably not important, but as I recall I think there was some minor overhead in translating from a JS String to an Element.
I wish this were available natively.