Live data from Hacker News

Ripple – A TypeScript UI framework that takes the best of React, Solid, Svelte

github.com

11–20 of 74 posts

Re: Ripple – A TypeScript UI framework that takes the best of React, Solid, Svelte

#11
> Now given $startingCount is reactive, it would mean that $count might reset each time an incoming change to $startingCount occurs. That might not be desirable, so Ripple provides a way to untrack reactivity in those cases: ...

This automatic reactivity thing is really what makes these frameworks more complex than they need to be.

I'd much rather handle all re-rendering calls manually. It's more work for me, but at least I don't work with a chain-reacting foot gun that's hidden in a black box.

Re: Ripple – A TypeScript UI framework that takes the best of React, Solid, Svelte

#13
post #9

In case people don't know who the author is... Dominic is the original author of Inferno, was part of the React team, and also was a major contributor to Svelte 5 (the runes thing).

Yeah, seems that he has the credentials for this type of a push

Re: Ripple – A TypeScript UI framework that takes the best of React, Solid, Svelte

#14
post #10

Since this is marked as a departure from HTML and has it's own syntax, I think this is a good point to improve upon JSX. - Remove curly braces from props and children canBeInParanthesis()) /> userName "Text contents" - Add punning (like how { age: age } becomes { age } in JS) const age = 40; / // explicit boolean attributes

How about... inlining children:

    const age = 40;
    const children = [, , ];
    return ;
Rationale: single child elements are ubiquitous in web dev, but most JSX formatters will require 3 lines of code even if there's a single child.

Re: Ripple – A TypeScript UI framework that takes the best of React, Solid, Svelte

#16
post #12

https://xkcd.com/927/

This isn't proposing a standard, it's a new framework which takes inspiration from the other mentioned projects, while choosing a different set of trade-offs. This is just what it looks like when people try new stuff, and I don't think the snark of the comic is appropriate.

Re: Ripple – A TypeScript UI framework that takes the best of React, Solid, Svelte

#17
post #11

> Now given $startingCount is reactive, it would mean that $count might reset each time an incoming change to $startingCount occurs. That might not be desirable, so Ripple provides a way to untrack reactivity in those cases: ... This automatic reactivity thing is really what makes these frameworks more complex than they need to be. I'd much rather handle all re-rendering calls manually. It's more work for me, but at…

Frameworks handle more than 95% of cases to make your life easier. For the corner cases, you can write custom logic yourself outside the framework.

> ...handle all re-rendering calls manually.

Have you considered writing web components? With them, you handle the rendering logic and lifecycle yourself.

Re: Ripple – A TypeScript UI framework that takes the best of React, Solid, Svelte

#18

Looks quite nice, I'm not 100% sold on having flow exposed (for, if) and plain text always escaped (wrapped in {''}), I suppose at least it encourages not having magic strings everywhere. There's some other details that look interesting like the @use feature. I like the reactive prefix concept but having had so many reactive headaches I'm interested in how this plays out. Overall it's a wait and see project for me wi…

I really like having to escape all the plain text. I think all the React-like code I’ve written has been at least 90% code and tags, not plain text, and the lack of escaping occasionally causes bugs (usually printing the name of a variable instead of its value).

Re: Ripple – A TypeScript UI framework that takes the best of React, Solid, Svelte

#20
post #12

https://xkcd.com/927/

This isn't proposing a standard, it's a new framework which takes inspiration from the other mentioned projects, while choosing a different set of trade-offs. This is just what it looks like when people try new stuff, and I don't think the snark of the comic is appropriate.

if frameworks are specifications, then a new framework is definitionally a new standard. it’s not an ISO or ANSI standard. but the point of the comic is, there are 10 web frameworks, we need one to be the best of all of them! there are 11 frameworks.
Post reply on HN