That I can understand! Being able to write ts/js would have made it easier for me to get started, for sure. This is all very cool and I would love to play with this if you ever decide to publish! 🙌

I was thinking around the same lines. But then i really started digging into openscad and realised that it doesn't need jsx. It's well designed for the task it mas made for. There are vscode plugins to get realtime previews.

The web de-facto won, and if PWAs support wasn't purposefully hindered by Apple, it would've won in the app market as well. But one cannot monopolize an open market by design so we are here we are.

🙏

Good to see! Thank you for all your work on moving this forward 🦸‍♂️

My view is that async react is first and foremost transitions. Suspense is to mark pieces of the next view as less important for the transitions. Ie "don't wait for this, it can complete later"

I mean, their concurrent rendering model is what enables the "async react" patterns, no?

I understand that. Am I correct to say that the big difference is that the core of react is built on top of their concurrent rendering architecture (fiber) while preact is based on a synchronous model. And that that's the tradeoff?

Yeah. There are so many reasons, but just the fact that another company is dictating whether or not your application is available tomorrow should be enough. On the web you can just change host if you like. DNS is universal.

I've been a consultant for almost 15 years and I've found the PWA agenda to be almost impossible to push.

I think it's 80% about "being on the app store".

Preact is great. I can see myself using it if it had the concurrent features of React, but then it would probably just be React?

I'm curious, what do you know around the latest research from the react team and the latest additions to the library? I feel like what has been happening in React for a while is very impressive and solves real UX and DX problems. And I see other libraries like solid and svelte taking inspiration.

Because they are innovating in the right areas

Good for you :)

I hope github.com/reactwg/asyn... is either resolved with a simple solution or starts a deeper discussion around this.

So meanwhile I feel like we have to fork the behaviour of our design components at some level. Be it exposing both "onX" and "xAction", having wrapper components, or just leaving transitions to the user...

The async-react demo from rick doesn't show the problem because the dataset of each tab is directy based on the state of the checkboxes, so it makes sense to wait. But there are cases where you don't want to wait, as you described.

I have been thinking about this problem and I really think this is the bottleneck for transitions and one place where you will get a better experience not using action props. Which is a shame, because I'd like the model and I think it will be great long term.