Viewing profile — volfpeter

It's just sugar. It hides the manual template selection, context creation, and rendering logic behind a simple decorator. This way you always write standard FastAPI routes (or you …

It's a shame you did all the rendering manually :) FastHX would have simplified your life a bit. devpush seems really interesting! I wasn't aware of it, but I'll check it out! It a…

Well, the thing is, FastHX, htmy, and holm should be powerful an unopinionated. Think of them like ReactDOM, React, and Next.js. On the other hand, I already thought about building…

It's very early days for the project, but I wanted to share it to see if there is interest. It is the final piece of the FastAPI server-side rendering stack I started building with…

With the current renderer (which is super basic because simplicity and features were the main priority over optimization for now), if a component has multiple async children, they …

I did some testing in the meantime. Depending on what you render, it's about an order of magnitude slower currently. The renderer is as simple/minimal as possible at this point (th…

Yeah, the renderer itself must be async to enable async tooling, but everything else can remain sync unless async is really needed. Regarding data fetching (it's a recurring theme …

That's a pretty complex question. Reflex is a great project with a great feature set, it does everything (client rendering, state sync, API) and you can even write your callbacks i…

I haven't done benchmarking yet. To be fair, I had limited time and I focused on developer comfort and the features I needed for projects I work on. Simplicity and flexibility was …

The most important difference is that htmy does not bring its own web framework, you can use it your preferred one (preferably one with async support, but you can always delegate t…

Funny, I went through the exact same process before I started creating this project :)

I've seen htpy before starting this project. While creative, I'm not too happy with the interface if I'm honest and it feels quite a bit more limited. There are no magic methods re…

That's a fair point, although my feeling after working quite a bit with Jinja recently is the opposite (primarily for lack of static analysis and IDE support). You're right, for ex…

Components don't really need to fetch anything, they don't need to be smart. It's up to you where data fetching happens. If you look at fasthx for example, you'll see that routes/v…

You're right, fetching all the data (that you may or may not need during rendering) in advance is of course doable and quite common. That's what you do for example with tools like …

Thanks for this answer. Async support is handy if the framework in which you're using the tools is async (let's say FastAPI). See my answer to a similar question on reddit: https:/…

I just noticed on Reddit that someone posted my package here. I see there are several comments already. I'll try to answer a few as I have time.