So, what’s the difference between . and emit? It seems both take a string and output it to the HTML of the page. If so I don’t see why that couldn’t be
LLM-based coding is enabling so much! The crazy weekend project now can have compilation to native code and web assembly, allow server-side or client-side rendering, manage multiple types of persistence, include adaptive compression, and do all of this without breaking a sweat.
React (and the unidirectional FRP approach in general) is the only known sane way to describe complex GUIs. It's the same approach that powers spreadsheet calculations.
Most websites are not complex GUIs though, and do not need React.
> : h1 ( s -- ) "<h1>" emit . "</h1>" emit ;
> "Hello, World!" h1
So, what’s the difference between . and emit? It seems both take a string and output it to the HTML of the page. If so I don’t see why that couldn’t be
We also have: where, I think, the idea is to always have the two strings consistent with each other. If so, why require the blog writer to do that conversion?It's scary but I love it.
Most websites are not complex GUIs though, and do not need React.
If there's a place to use a weird and fun language it is certainly one's own personal blog. Sounds like a great opportunity, I think you should do it.