Ripple: The Elegant TypeScript UI Framework
jsdev.space
Ripple: The Elegant TypeScript UI Framework
1–10 of 28 posts
Re: Ripple: The Elegant TypeScript UI Framework
#2For the first time in a long time, I actually like the look of this.
It’s like htmx and jsx teamed up for world domination. I like the component keyword as a first class citizen. I like the bind and event stuff too. Man, I’m going to have to try this.
Re: Ripple: The Elegant TypeScript UI Framework
#3The end result seems very close to svelte with runes, except with lower learning curve because we dont have special syntax for things like loops, conditionals etc.
Re: Ripple: The Elegant TypeScript UI Framework
#4For the first time in a long time, I actually like the look of this. It’s like htmx and jsx teamed up for world domination. I like the component keyword as a first class citizen. I like the bind and event stuff too. Man, I’m going to have to try this.
+1
Re: Ripple: The Elegant TypeScript UI Framework
#5Why did you use `track` for variables and `#` for lists instead of using the same syntax for both?
Re: Ripple: The Elegant TypeScript UI Framework
#6Please.. no more UI frameworks. Can we just agree to make react native to the browser, get rid of redux, and simplify things?
Re: Ripple: The Elegant TypeScript UI Framework
#7Please.. no more UI frameworks. Can we just agree to make react native to the browser, get rid of redux, and simplify things?
I recommend MobX as a solution for state management
Re: Ripple: The Elegant TypeScript UI Framework
#8Why did you use `track` for variables and `#` for lists instead of using the same syntax for both?
Scalars and collections have different update semantics. track() is for atomic updates, # is for structural mutations — separate syntax makes reactive tracking and optimization simpler.
Re: Ripple: The Elegant TypeScript UI Framework
#9Please.. no more UI frameworks. Can we just agree to make react native to the browser, get rid of redux, and simplify things?
erm, no? React has painted itself into a usability and optimisation nightmare corner by insisting that components are the most granular level of resctivity.
That's why they need 20 different hooks to do anything.
You want signals in the browser for granular reactivity, and they are making their way there: https://github.com/tc39/proposal-signals
Re: Ripple: The Elegant TypeScript UI Framework
#10And just like svelte this is elegant exactly until you realize that it is not possible to correctly track all the dependencies and just like svelte you realize that a mix of explicit and implicit reactivity is really hard to debug and then you seitch to explicit reactivity and then you are just as complex as any other reactivity based framework