Yep. I’m now on my second 4-year period of news avoidance (sorry US folk), and all I do is skim headlines every other day—-everything I need to know seems to surface in social media (which I only check once a day or when waiting for something with my phone), and that has taken a lot of the pessimism off.

Sample video of creaky hinge simulator (and theremin mode!) at https://hachyderm.io/@samhenrigold/115159295473019599

s/Cost/Price/g

Microsoft has an arguably better and more generally useful solution in GitHub Copilot.

Sorry, but I tried and just couldn’t get compose and networking to work the way I wanted - as well as permissions, volumes and a lot of other stuff…

Which compose? Podman-compose [1] wasn't fully up to date with the latest compose-spec [2] the last time I checked it. However, the docker-compose v2 [3] (the one in Go, not Python [4]) is compatible with the Podman engine [5] and works like a charm for me.

I have also had no issues with networking, permissions or volumes while running as non-root user. Are you simply facing issues setting it up, or are you hitting some bugs or missing features?

[1] https://github.com/containers/podman-compose

[2] https://compose-spec.io/

[3] https://github.com/docker/compose

[4] https://github.com/docker/compose/tree/v1

[5] https://www.devopsroles.com/how-to-use-docker-compose-with-p...

One of the things this model is actually quite good at is voice cloning. Drop a recorded sample of your voice into the voices folder, and it just works.

bonus usage

You should look into the various Pool classes. Back when asyncio came about, I did a lot of experimenting with various multi-core approaches: https://github.com/rcarmo/newsfeed-corpus

I personally recommend aiohttp. Setting up a ClientSession and letting it do its thing is quite nice.

httpx also supports sync and async, but I remember seeing an issue in their repo about worse performance than aiohttp.

I've had no real issues with async, although I primarily use libraries like aiohttp and aiosqlite and even write my own helpers (https://github.com/rcarmo/aioazstorage is a good example).

The vast majority of the Python code I wrote in the last 5-6 years uses asyncio, and most of the complaints I see about it (hard to debug, getting stuck, etc.) were -- at least in my case -- because there were some other libraries doing unexpected things (like threading or hard sleep()).

Coming from a networking background, the way I can deal with I/O has been massively simplified, and coroutines are quite useful.

But as always in HN, I'm prepared for that to be an unpopular opinion.

I share your experience

asyncio is easier than threads or multiprocess: less locking issue, easier to run small chunks of code in // (easier to await something than to create a thread that run some method)

There is no locking issue, if you don't mutate some global state from more than 1 thread at the same time. If you program mostly in pure functions, this is a non issue.

I took the Pi Zero route a few months back and have a reincarnated Quadra in the 3D printed case of an SE/30.