starfx VS nicegui

Ah! A real criticism of FE development, I agree with your problem statement.

When you jump into the world of single-page applications, things get complex pretty quickly, because the use case for needing an SPA pushes the web app into a full desktop application.

Ultimately, for a highly interactive and dynamic "desktop-class" user experience, there is added complexity. I think that's why so much movement within the FE world has moved away from "SPA for everything" and into these mixed dynamic apps. Islands, React Server Components, NextJS, they all help create a middleground between a document-based website with no dynamic elements with a full blown desktop app experience. They all have real tradeoffs, in particular adding an entirely new backend service to serve the front end.

For many projects, react + react-query is probably enough.

Having said that, my argument from https://bower.sh/dogma-of-restful-api still stands: when you build an API that is RESTful (1:1 mapping between endpoint and entity) you are unknowingly pushing the complexity of data synchronization to the FE, which requires a well thought out ETL pipeline.

This probably doesn't help my case but I've been building a simplified middle-layer for react to bridge the gap between react-query and full blown SPA: https://starfx.bower.sh

`redux-saga` maintainer here.

I've been using `effection` to build a replacement for `redux-saga` over at https://github.com/neurosnap/starfx

Effection has demonstrated to me how truly powerful delimited continuations are and why structured concurrency is an incredible asset for anything that requires async flow control -- basically everything in TS/JS.

I know sometimes it's hard to imagine why someone would need structured concurrency or care about delimited continuations for a front-end application, but this is a game changer in terms of expressing async flow control.

Some things to note about Effection:

- API surface area is small https://github.com/thefrontside/effection/issues/851

- It tries to stay as close to JS constructs as possible so it will feel very familiar

- Resource cleanup is automatic (when a function passes out of scope all descendent tasks are shut down automatically)

- End-user doesn't need to think about delimited continuations

The only leap users need to "deal with" coming from async/await is the syntax.

    import { main, call } from "effection";

- https://github.com/thefrontside/continuation

- https://github.com/thefrontside/effection/tree/v3

- https://github.com/neurosnap/starfx

The last one intends to replace redux-saga using DCs.

Here’s a presentation I gave recently talking about DCs in typescript: https://youtu.be/uRbqLGj_6mI?si=XI0JNMKMoO2VHMvM

A couple of us have been experimenting with deliminited continuations and I think it’s gonna take off soon:

https://youtu.be/uRbqLGj_6mI?si=kgKKjpCnehJ9bpIG

https://github.com/neurosnap/starfx

I feel the same way which is why I decided to help maintain the project. Async flow control is very tricky even in js–land. Having watchers live inside of a while-loop is a powerful construct that lends itself to interest flow control patterns.

I'm also in the process of rebuilding redux-saga but without the redux part: https://github.com/neurosnap/starfx

It's still in alpha stage, but it is very reminiscent of redux-saga.

I was looking at this space and nicegui seemed like the best ootb experience.

https://nicegui.io/

Dash is similar in spirit, as a "build web UIs with Python" framework. Dash seems more similar to nicegui (https://nicegui.io) architecturally than to Hyperdiv. Like nicegui, it builds a static dom that is then mutated via callbacks or data bindings.

By contrast, Hyperdiv lays out UI declaratively based on state, and when state changes, the app re-runs, generating an updated UI. Streamlit and Hyperdiv seem to work similarly, though I'm not sure how Streamlit handles state and state-based layout.

For native GUI, DearPyGui[0] as modern as you can.

For browser web-based GUI, you can use nicegui[1]

[0] -- https://github.com/hoffstadt/DearPyGui

[1] -- https://github.com/zauberzeug/nicegui

I want to bring to attention a set of frameworks that make webdevelopment using Python simple and fun. The popular opinion maybe that webpages developed with Python maybe slow. But this is not the case. Do checkout https://github.com/ofjustpy/ofjustpy/, https://github.com/zauberzeug/nicegui/ and https://github.com/justpy-org/justpy . All these frameworks are build on top of Starlette and make web development really easy. If you want simple and ready to use the nicegui is the choice. If you want fast, scalable, and more control then give ofjustpy a try.

Yes, NiceGUI aims for a very gentle learning curve. Coming from Streamlit I suspect your main adaptation will be that in NiceGUI you need to write valid Python code. Streamlit constantly reevaluates your script which feels nice and easy but creates lots of problems down the road. See https://github.com/zauberzeug/nicegui/discussions/21.

Auth is a big limitation. It's not a built-in component, they have [an example](https://github.com/zauberzeug/nicegui/blob/main/examples/aut...) using the FastAPI layer for auth, but I haven't had time the time to try implementing it. It's definitely not something you get out of the box with NiceGUI.

For scaling, I am viewing it mostly as an internal tool builder. I wouldn't recommend it for external applications. So as far as scaling an internal app I think it works fine. [Their website](https://nicegui.io) is built with NiceGUI, and it works fine, but you can feel the lag occasionally on some of their larger demo pages.

Well, I was at PyCon Ireland last weekend and I missed the NiceGUI talk. I hear postive things about it and anything shiney and anything frontend-related always catches my attention (although I admit talking to a friend when I missed this talk was just as fun, and it was worth it).