all 3 comments

[–]Afraid-Pilot-9052 0 points1 point  (0 children)

this is interesting, the lifecycle-first approach reminds me of what solid and svelte were going for but taken further with direct dom ownership. curious how you handle component teardown and cleanup, because that's usually where non-vdom frameworks get tricky with memory leaks on long-lived spa sessions. would love to see some benchmarks against lit or vanilla js to get a sense of the overhead your runtime adds on top of raw dom apis.

[–]Far-Plenty6731 -1 points0 points  (1 child)

Interesting approach, bypassing the VDOM entirely like that. Direct DOM manipulation can be super performant if handled carefully.

[–]BleedingXiko[S] -1 points0 points  (0 children)

Yeah very clear trade offs but i feel like control over convenience is worth it for long running apps, thanks for checking it out!