Using runways in browser seems a bit strange to me

Serverless? So it runs on... nothing?

No it just runs on other people's servers.

Why would we use something that makes us dumber and wastes our planet more than anything else.

Nah, I'll skip.

Windows becoming less and less relevant every day and then they do this. 2026 is gonna be true Year of the Linux Desktop.

Because a lot of people have no clue about packaging or how to write compatible software, one that is actually installable as normal application. I suspect a lot of them learned stuff in node.js or ruby ecosystem first and this is the result. Same as requiring using docker to install or build an application. It isn't cool, funny or right way to do stuff. I still don't get what was so wrong about venv that anyone needed uv. I have no need to even try and i'm writing python stuff so long that i cannot even estimate it. To me it feels like reinvention for sake of rewrite in rust. If it is so good, ok, i get it, it might be - and all that good stuff needs to go back to python as python.

> I still don't get what was so wrong about venv that anyone needed uv.

Pip is slow, far slower than it needs to be in almost everything that it does, regardless of being written in Python. It's "standard" but not part of the standard library (so that it can be developed independently), and was never designed to install cross-environment properly (the current best approach, since 22.3, is a hack that incurs a significant delay and expects everyone to move in lock-step with the CPython EOL schedule). It wastes disk space, both by re-copying packages into new environments (rather than hard-linking them as uv does) and by spawning copies of itself in those environments (the original work-around to avoid needing cross-environment installation support, which a few people have also come to rely on in other ways).

> If it is so good, ok, i get it, it might be - and all that good stuff needs to go back to python as python.

I like these threads because they encourage me to work on my main project.

If so, ok, let's port this prototype to back to python and get rid of uv.

What does this comment mean? Port the dependency and virtual environment manager back to the language?

Should we port npm “back” to node js?

Well, go does have the module management, including downloading new versions of itself, built-in into the `go` tool itself. It is really great.

But I don't see this hapenning in python.

You don't see that happening because you don't want to.

npm is written in javascript, not rust or c#.

yes, we should bring package manager back. if it is so awesome and solves some problem.

Sounds good, I agree that uv should come with the language in the same way npm comes with node and cargo comes with rust.

You keep using words like "we" and "us" so I assume you'll be kicking off writing the PEP to make this happen?

It unfucks nothing because it wasn't fuckd in the first place. Whole uv is solution to non existing problem.

Also very good way to instantly spend all your air time. Remember, legally you can only transmit at something like 10% of time. In some bands even less, afaik.

> Remember, legally you can only transmit at something like 10% of time

In Europe. See the duty cycle limits summarized at https://meshtastic.org/docs/configuration/radio/lora/#region

It's best not to retransmit MQTT. Unless you want to set up some very specific link between two meshes, or just some private or non-default channel.

I've also found meshtastic to be totally unusable in practice. Tried it, really really hard. It barely worked in a city i live in. Did not work at all when i took the node for 500km ride. Bad protocol, yes, it is.