at a high level it sounds comparable to angular's template compiler. is that a fair comparison?
-
-
-
Somewhat, but our compiled templates are literally orders of magnitude smaller.
-
The approach I'm talking about is compiling the template down to opocodes that we run rather than JS. Just more optimizable in practice.
End of conversation
New conversation -
-
-
um data binding is way older than the virtual dom thing?
-
our approach has some prior art lineage (want to write it up) but in total is new. And in general today's ecosystem is vdom
-
multiple competing approaches *today* are important for forward progress.
-
congrats on the launch btw! Dying to play with it
End of conversation
New conversation -
-
-
Pun intended?
- End of conversation
New conversation -
-
-
same here, just 1 month before
https://medium.com/@WebReflection/hyperhtml-a-virtual-dom-alternative-279db455ee0e … -
we first talked about glimmer VM architecture a year ago after a year of woke ;)
-
Do I understand right that Glimmer uses approach similar to Svelte? cc
@Rich_Harris -
not quite. Svelte compiles straight to JS. Glimmer compiles to opcodes, uses VM at runtime
-
hyperHTML is straight JS with JIT'ed DOM ... it's cool we all found different ways to perform that good

-
I just really really liked idea of not having any framework code in runtime :)
-
so you like hyperHTML
/ @Rich_Harris@wycats -
I like it too, but Svelte even more :D
- 1 more reply
New conversation -
-
-
any docs anywhere that go over those differences? super curious
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Can one glimmer without ember?
-
Yes indeed! https://glimmerjs.com/
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.