As much as we’re delighted to present you this new version, we are also sad to announce that our friend and prolific FreeCAD developer bgbsww has passed away a few weeks before this release came out. He was one of the main architects of the topological naming fixing effort, wrote a lot of additional code and tests, and became FreeCAD’s TNP specialist. He also helped virtually all other developers out to adapt to the new algorithm. This release is dedicated to him.

😥

Install is the easy part. Nobody ever thinks about maintenance.

I had the same thought - an entire 8U rack to hold a single raspberry pi with an external drive?

I think adults can and should disagree on things and feel free to voice opinions - especially if done as civilly as this. Not “this sucks” but just “it’s not too my taste”.

Pop 22.04 with Nvidia 3070 and it “just worked”.

You haven’t described in what way it is not working for you.

Go ahead and try to use it then.

That’s all proxmox does too, just provides a gui and management tools.

Theme for what?

Do you often recommend people running single-developer maintained software that has existed for about a fortnight for “security purposes”?

You seem to understand neither security nor privacy.

I get to give you access to all my photos so that you can just proxy calls to my server?

Just share your own damn server people, this “I’m behind 7 proxies” bs is getting tiring.

It’s on the “official website” but it’s a “user processed image”. Looks like it was a color enhanced version of this original: https://www.missionjuno.swri.edu/Vault/VaultOutput?VaultID=53518&ts=1723603688

God, this old argument… Careful, it’s an antique.

The idea is to minimize memory management and have people who are experts on it deal with it.

I did - it says he’s supporting rust in the kernel.

Why the swipe at Linus? He’s been supportive of rust in the Linux kernel.

The main use of wsl is often for things like docker, not as a “Linux desktop”. Microsoft has been getting killed by Linux in server environments. This lets developers stay on windows and build containers.

What reasons? They gave reasons? They just said that windows fixes the flaws Debian has which is quite the “compliment”.

ChatGPT - give me an example of what an insufferable Linux elitist would say about wsl.

“This article is not for Linux experts. If you are one and have a Windows machine (main reason is gaming), I hope you are using Debian for WSL and not Ubuntu.”

Yes - they’ll start automatically. There are other options for “restart” that define the behavior.

You can give whatever you like to “servicename” and use that rather than the ID.

For example:

docker run -d --name mysite --restart unless-stopped nginx

docker stop mysite

docker start mysite

At its simplest:

docker run -d --name servicename --restart unless-stopped container

That’ll get you going. Youi’ll have containers running, they restart, etc. There are more sophisticated ways of doing things (create a systemd file that starts/stops the container, use kubernetes, etc.) but if you’re just starting this will likely work fine.

With all the hype surrounding Python it’s easy to forget that it’s a really old language. And, in my opinion, the leadership is a bit of a mess so there hasn’t been any concerted effort on standardizing tooling.

Some unsolicited advice from somebody who is used more refined build environments but is doing a lot of Python these days:

The whole venv thing isn’t too bad once you get the hang of it. But be prepared for people to tell you that you’re using the wrong venv for reasons you’ll never quit understand or likely need to care about. Just use the bundled “python -m venv venv” and you’ll be fine despite other “better” alternatives. It’s bundled so it’s always available to you. And feel free to just drop/recreate your venv whenever you like or need. They’re ephemeral and pretty large once you’ve installed a lot of things.

Use “pipx” to install python applications you want to use as programs rather than libraries. It creates and manages venvs for them so you don’t get library conflicts. Something like “pip-tools” for example (pipx install pip-tools).

Use “pyenv” to manage installed python versions - it’s a bit like “sdkman” for the JVM ecosystem and makes it easy to deal with the “specific versions of python” stuff.

For dependencies for an app - I just create a requirements.txt and “pip install -r requirements.txt” for the most part… Though I should use one of the 80 better ways to do it because they can help with updating versions automatically. Those tools mostly also just spit out a requirements.txt in the end so it’s pretty easy to migrate to them. pip-tools is what my team is moving towards and it seems a reasonable option. YMMV.