Android now runs a Debian VM, too. It's early days, but I'd be surprised if they don't get Linux GUI apps integrated into Android in desktop mode soon.
There was a time in the 90s when quite a number of governments were aware of this Microsoft problem and insisted on open formats, so that important govt records and data could be open down the track. It seems like all of that was forgotten and traded for 'convenience'.
That's not exactly for slowness reasons. The creators of uv have stated that if pip followed the same algorithms they'd see similar performance benefits. People greatly overstate the Python performance penalty.
... Actually, could you show me where they said it? I've been explaining it from first principles from a while now and it would be nice to be able to go "but don't take my word for it" as well.
(Python does incur a hefty performance penalty for things that are actually CPU bound. But that doesn't describe most of the process of installing Python packages; and the main part that is CPU bound is implemented by CPython in C.)
I'm well aware of it. But I don't think I have ever seen an editor/website which would display it as 9 spaces. Github for example default to 4 spaces width.
Yes, this is very weird. But Go Playground[1] has always been using 8 spaces per tab for some reason. I always found that very jarring, particularly where almost every other editor or documentation has settled on 4 spaces per tab.
Yes, of course that works, but then you have to start up and shell into WSL. With podman, you can run all commands directly in Windows which is more seamless. Plus, getting it working is just a matter of running "winget install -e --id RedHat.Podman". This is particularly helpful when trying to roll things out for larger teams as they don't have to know anything about WSL and everything integrates in their environment seamlessly. Of course, just using Linux is preferable for development if you can get away with it.
> You absolutely can run docker on the CLI in WSL2.
But again, they're talking about Windows, not Linux-in-Windows or virtualized Linux on Windows. Just because you can do something in WSL2 doesn't mean you "can do it on Windows", as much as you "can run systemd and Wayland on Windows" because you could run it inside a Linux VM...
Yes. For some the distinction between the two is almost nothing as WSL is pretty seamless. However, using Podman directly in your normal Windows shell opens up more use cases. Podman is of course running everything behind the scenes using WSL.
> For some the distinction between the two is almost nothing as WSL is pretty seamless
WSL1 yes, but not WSL2, which the parent explicitly mentioned. WSL2 is just virtualization with a fancier name, might as well use VirtualBox and similar at that point.
Your posts in this thread seem to be focused on the inability to use Docker from the Windows shell, but it's not true: you just need to set DOCKER_HOST. Then the Windows client can connect to a Linux engine in WSL2. Docker engine in WSL2 runs as a systemd unit and doesn't need to be manually started. Podman/Docker Desktop are doing far less work here than you might be expecting. They are just automating this setup for you. I run this setup and it is genuinely a one-time nothingburger. If you have a bunch of Windows machines, you can have them all share one Linux Docker engine if you want, by pointing DOCKER_HOST at the same host.
Niri looks promising to me. After I discovered PaperWM I moved on to Material Shell, which was still the best workflow I've come across to date. It was basically gnome with a 2d grid: you could scroll workspaces left and right and then again on the vertical axis. The author sort of abandoned it (it was a Gnome extension) in order to go all in on their own desktop environment with the same concept. I'm guessing that'll take a while to get off the ground.
> Then came the SQLModel problems. The author pushes it very hard in the FastAPI docs
No it doesn't? The front page for FastAPI contains a pretty lengthy tutorial with no mention of SQLModel. The only time SQLModel gets a significant mention is on a page explaining connecting a relational DB, but it makes it clear that any DB at all can be used. Something has to be chosen for the tutorial, so it makes sense the author would choose their own.
If SQLModel isn't right for you then you're the only person to blame. I've been through that tutorial before and settled on plain old SQLAlchemy.
Also, minor nitpick:
> Without that we would have been reduced to tracing through switch ARP tables (for switches smart enough to report that)
You'd only need your switch to have a viewable mac address table rather than an ARP table.
reply