I heard it works great for jax
@jeremyphoward
-
JSX Syntax Evolution and Historical Design Decisions
By
–
Yeah I don't love the {}, but it's not so bad I guess 😀 IIRC at the time jsx was created some of this syntax didn't exist?
-
Auto-formatting tools for nested functional components
By
–
No there aren't any auto-formatting tools yet I've found that do a good job of laying out nested functional components. E.g here's an example formatted with yapf:
-
VS Code Parenthesis Matching Tools Discussion
By
–
Yes spent quite a while trying that direction, but ultimately decided I don't like it as much. But it's a perfectly reasonable choice and there's no best answer. BTW vscode has really great tools for parens-matching nowadays (disabled by default sadly).
-
F-String Alternatives in Python String Formatting
By
–
Actually we don't even need the f-string. `H1('Hello ', name)` would work too…
-
Measuring Information Gain: Luck versus Skill
By
–
It's based on measuring the change in information resulting from your choices. If there's an improvement in information higher than expected, you're lucky. If you choose something that is expected to increase information a lot, you're skillful.
-
FastHTML rejects JSX syntax, leverages Python functions instead
By
–
I've had quite a few people ask if we plan to add syntax like jsx to FastHTML. We don't. That's because Python's function syntax is already a perfect 1:1 match to html element trees. JS isn't, so they needed something new. Here's an example I just showed on the HTMX discord:
-
Jeremy Howard discovers he’s luckier than average in Wordlebot
By
–
Never noticed there neat little feature in Wordlebot before! Turns out I'm luckier than average…