@yeraycaballero.bsky.social
Reposted
Ok, here's my second post on a potential native DOM templating API, diving into exactly what such an API should actually look like and why.
justinfagnani.com/2025/06/30/w...
justinfagnani.com/2025/06/30/w...
What should a native DOM templating API look like?
justinfagnani.com
June 30, 2025 at 6:37 PM
Ok, here's my second post on a potential native DOM templating API, diving into exactly what such an API should actually look like and why.
justinfagnani.com/2025/06/30/w...
justinfagnani.com/2025/06/30/w...
Reposted
The more I think about "functional" components, the crazier they seem to me.
They try to combine:
- One-time initialization
- Instance-local state
- A repeatedly called render callback
- Other lifecycle callbacks
into what looks like - but definitely *is not* - a pure function.
They try to combine:
- One-time initialization
- Instance-local state
- A repeatedly called render callback
- Other lifecycle callbacks
into what looks like - but definitely *is not* - a pure function.
February 26, 2025 at 8:30 PM
The more I think about "functional" components, the crazier they seem to me.
They try to combine:
- One-time initialization
- Instance-local state
- A repeatedly called render callback
- Other lifecycle callbacks
into what looks like - but definitely *is not* - a pure function.
They try to combine:
- One-time initialization
- Instance-local state
- A repeatedly called render callback
- Other lifecycle callbacks
into what looks like - but definitely *is not* - a pure function.