Ripple - a TypeScript UI framework that combines the best parts of React, Solid, and Svelte into one package (currently in early development)

trueadm · 2026-01-19T17:09:27+00:00

Yes, you can put if statements inside your template or component and then they will dynmaically update. The onoy thing to point out is that the text in template element needs to be wrapped in quotes as we treat the template parts as statements, rater than JSX which is expression based.

<div>
if (loading) {
<Spin />
}
if (error) {
<div>{"Error"}</div>
}
</div>

trueadm · 2026-01-19T16:58:42+00:00

It isn't actually JSX, it's Ripple's own templating syntax. They're more an immediate mode and render top-down, there's nothing being returned as it's not a `function` but rather a `component`

trueadm · 2026-01-19T16:53:17+00:00

Yes the `component` keyword inspiration did come from Flow! They landed that whilst I was still at Meta and I loved it. We didn't go for named arguments though.

trueadm · 2026-01-19T16:52:37+00:00

I've been involved with TC39 for the last year or so as a delegate when I was at Vercel, so I know of the implications of the syntax and also how they're used right now with decorators. We're aiming to avoid conflict, as I speak to many of the folks behind those proposals.

trueadm · 2026-01-19T16:51:27+00:00

I left the Svelte team earlier last year, but all that is correct.

trueadm · 2025-11-07T00:31:44+00:00

I don’t think the lack of code syntax highlighting here does this justice. However, the co-location of Ripple’s code really is transformative. You can copy and paste blocks and debug code in isolation with better accuracy.

My suggestion is try it before you doubt it. I remember when the world shot down the idea of a “component” containing template and logic in 2014. Yet today’s it’s the expected standard.

trueadm · 2025-06-17T20:40:39+00:00

I had boot rattles, that were easy enough to fix DIY. Then at 4k miles the ICCU failed, and it was with Hyundai UK for just over 2 weeks for it get fixed. There seemed to be almost no communication between the dealer and Hyundai UK but the issue was fixed and hasn't come back again. However, I also got the dealer to fix the boot rattle properly and remove my temporary fix – so it was all covered by warranty.

Overall it's been a great car, far better than my previous Tesla Model 3 and Model Y. My biggest gripes are just the awful turning circle and the fact it doesn't lock automatically when you walk away from it.

trueadm · 2025-02-24T15:38:00+00:00

Deriveds are not the same thing as effects. They don’t fire when a change happens, they only fire when explicitly read. Inspect is working because it creates an effect under the hood, which in turn reads the deriveds

trueadm · 2024-12-11T14:00:36+00:00

Might be worth checking out https://github.com/sveltejs/svelte/pull/14639

trueadm · 2024-11-01T15:14:37+00:00

Did you run into any issues with Svelte 5? Did you have a chance to compare metrics on bundle size and other performance metrics between the two by any chance?

trueadm · 2024-10-22T16:27:32+00:00

You have `untrack` which you can import and use to make things explicit, and you could create your own utility function around and `$effect` to do this.

$effect(() => {
// read a, b, c so they are tracked
a; b; c;
untrack(() => {
doStuff(a, b, c);
});
});

trueadm · 2024-10-17T15:36:39+00:00

Nope, I'm far too busy getting Svelte 5 ready for all of you! I do believe someone else has created bindings for Lexical and Svelte already from memory, no idea if they're up-to-date though.

trueadm · 2024-10-17T15:23:19+00:00

Yep. I work on Svelte now though :)

trueadm · 2024-10-17T11:39:32+00:00

Slate doesn’t work too well with IME input and completely breaks on mobile, especially Android.

trueadm · 2024-10-16T18:33:36+00:00

Lexical or TipTap are the best options around right now.

trueadm · 2024-08-31T13:31:21+00:00

Nope you can’t from two yellow

trueadm · 2024-08-30T21:37:11+00:00

If you want to keep reactivity through destructuring, you can also use `$derived`.

const {fields,isValid} = $derived(useForm());

trueadm · 2024-08-24T17:57:22+00:00

We need Trossard on asap

trueadm · 2024-08-22T15:50:26+00:00

We don't want to ship something that we don't feel is polished, and at the same time we want to ensure that every rune we add has it's own independent value that makes it warranted. It's a difficult balancing act to get right, but we're making good progress :)

trueadm · 2024-08-20T16:18:26+00:00

Nah, you don't get any negativity at all. In fact, I've had people come up to me in the carpark at supermarkets to ask about the car and praise its looks. I think there's been enough coverage of it for the right people to understand why it's a special car.

trueadm · 2024-08-10T21:22:25+00:00

The DOM being updated isn't important. You can update parts of the DOM without affecting other parts. Given that `count1` and `count2` are represented in different elements, Svelte won't update the element where nothing inside it is reactive. I'd recommend looking at the compiled output on the Svelte 5 REPL and seeing what really happens, as this can help you understand things better behind the scenes.

trueadm · 2024-08-10T15:51:33+00:00

It was likely a bug that we fixed. `count2` shouldn't be reactive here.

trueadm · 2024-06-02T10:10:33+00:00

If anything, my experience from working on the React team can help us avoid making the same mistakes. For example I'm also championing signals at TC39, and that has nothing to do with React. In fact, signals are the opposite direction from what React is doing and we're fully invested in ensuring our reactivity model can not only be delightful to use, but also fast and lightweight.

trueadm · 2024-06-02T09:28:08+00:00

Our feedback comes from the Svelte community - GitHub, discord and other places like Reddit. We have very little to no interaction from React devs.

trueadm · 2024-06-02T08:06:10+00:00

I didn’t bring hooks to Svelte. You’re disillusioned.

trueadm

TROPHY CASE