Comment by quietbritishjim
4 hours ago
I genuinely have no idea what this comment is about. Why is a to do list a bad example? It's common precisely because it's ideal: it shows a few different basic widgets, and it shows how to update state in a way that keeps them in sync.
Is it because it's clichéd? That doesn't matter so long as it gets the point across.
Is it because you object to having desktop applications that do a simple task like this? I remember when simple single-purpose desktop apps were common e.g. Card File in Windows 3.1. Also this is meant to be an example for both desktop and mobile. Are only SPA web pages allowed to do things like this now? What a depressing world if so.
Or is your comment satire? I honestly can't tell.
Edit: What would you allow as a first example of a new UI toolkit. (Not that Flet is new, it's had plenty of 0.x releases.)
I don't think there is demand for this framework in the first place.
- Cross platform frameworks are starting to become an anti pattern these days
- Hello world examples are losing relevance when I'm not the one writing code
- A To Do list is just the absolute least impressive thing you can showcase
From a marketing perspective, I want to showcase something that other frameworks cannot do and "this only took 10 lines of Python code" is a very weak sales pitch in 2026.
OK, I think your main objection is really that you don't like the idea of a cross platform UI toolkit. I don't share that view, but fair enough. But your first comment, complaining about a to-do list example, is a very confusing way of expressing that.
And you think the front page shouldn't show a basic example because you just vibe code everything anyway. That is a very odd objection - it would be very concerning if a code library didn't include a basic usage example on its front page. Also, guess what, some of us do actually write (or at least look at!) some of the code in the programs we work on. And even AI benefits from a clean API.
And your complaint about a to do list is that it's not "impressive"? It's not meant to be! It's a basic illustration of the API. It's like reading the Rust tutorial and objecting, "ugh, another programming language with for loops".