Hacker Newsnew | past | comments | ask | show | jobs | submit | skeledrew's commentslogin

It uses Flutter for UI and native services, but there's a full Python interpreter there.

I think it does mostly canvas, but that could just be due to my selected option back when I tried web with it (couple years ago).


Native build size depends on what you want in the app, like the app I'm currently working on is almost 300MB, but I've added a few custom extensions to it (charts, iroh, and more). Earliest APK I can find is 140MB. In this day and age I honestly wouldn't worry much about app size though given how much storage devices have.

I like efficiency! Nowadays my phone and laptop are constantly running out of storage since every calculator app is 1GB.

Given the prices of storage and ram you should still worry about wasting user resources

I tried using Kivy some years ago and also found it pretty painful. Flet I've been using for a while now and find it a joy by comparison, and it's actively developed, with a release every couple months or so. With the stability of v1.0 I expect that to slow a bit though, as I'd say at least core Flet is feature complete.

The things it focuses on makes it wildly popular, and will continue to make it so. So popular that quite a few have been using it as a wrapper for packages with a Rust core, for example. I personally think they should stick to all Rust because they're only polluting the ecosystem, making Python less usable for an increasing number of scenarios.

Big disagree. I've been following this project since it's early days, and have made a few projects based on it. I haven't been bitten by any "inefficiencies" in such a way that'd make me give up the language. And at this very moment I'm working on what's essentially a Python REPL that can build and return Flet controls (as well as the traditional string result), making writing and running adhoc native "applets" fully on mobile a possibility (haven't seen anything else that does this).

I'm in the middle. I've been using Python since the early 2.x series.

The good parts are that the inbuilt data structures and their apis are efficient and clean enough to write code that's mostly readable. Most of the heavy lifting is done in hand tuned C and performance intensive external modules are also written in C. There are several good projects that are written using it and while it's not theoretically perfect, it's useful enough. Like Stroustrup said - there are 2 kinds of the languages, ones that everyone complains about and ones that no one uses.

The bad parts are that it's very easy to use. Almost in a Visual Basic "producing crap just takes a squeeze" kind of way. It opened up programming to a lot of people (the genesis of Python was in the CP4E project - where this was the aim). This resulted in a lot of bad patterns, inefficient code, badly written but popular libraries. Also, the indentation idiom and other restrictions resulted in a lot of convoluted APIs.There's also a lot of baggage from the pre multi-core CPU era (threading etc.).

I still think of it as a great glue language. If there are libraries that are fast and can run well, a good FFI or wrapper which Python can leverage will amplify the reach and usability of the library.

On the overall, a language that's older than the venerable Java which people are still using (and hence complaining about) speaks to its longevity. So, atleast by that definition, it is successful.


At least BASIC was originally designed as compiled language, only the 8 bit home computers made interpreter versions more widely known due to their hardware limitations.

Starting with version 5, Visual Basic "crap" was using the same compiler backend as Visual C++.


It should be supported, but if somehow it isn't, support can be added by creating an extension.

https://flet.dev/docs/extend/user-extensions/


Loving it. Been using in projects for a while now.

I've gotten better results both after "shouting at" and praising Claude, though the former causes more token burn because it starts questioning asking permission for everything after, which gets really annoying. Even a session clear doesn't get it completely back to baseline; only after some time does it return to "its old self".

With opencode, I just start a new session and it's the same blank slate, there's no lingering of prior state

Does /clear in claude not do what I intuit it to?


It does, but I feel like something is retained somewhere. There's already auto-memory, and the web chat has a persistent memory feature. It wouldn't surprise me if there's some hidden state that leads to per project or even per user auto-customization over time.

So... what's gonna be done about it? The recent precedent has been to invade the country, grab the president and try them.

It would be good if future elected politicians would choose to remove the president power to starting wars or killing people in special military operations. I am reminded of this 13 year old rap news video being very prophetic, including mentioning bombing Iran. https://www.youtube.com/watch?v=WpMPu5p_QXU

It doesn't really matter what powers the president is "given". As seen with this current US president, there're always ways to grab more power, directly or indirectly, no matter what checks are in place. And there are certain things that a president has to be allowed in some way for them to be able to act as a president in the first place, which preempts making them fully off limits.

A very good one minute summary of exactly what is about to happen: https://m.youtube.com/watch?v=2Whrat_Rn0I

If anyone else got their hopes up: this was a funny video not a serious reply


This was just great... It was so real I couldn't really distinguish the scenes with animate scenes that were clearly CGI from reality.

This is a flagrant mischaracterization and you should be ashamed. They even issued a retraction: https://m.youtube.com/watch?v=5SZYz7lZRRI

What democracy?

You can still vote this government out and organize your community to help with that. Remember the three boxes - soap, ballot, and ammo. You still haven't exhausted box #1 and should use box #2 really well this year.

Tyrants feed on the belief they can't be removed.


Why are you so convinved that the current administration leaves, even after defeat?

Then, and only then, you might consider the third box.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: