[anongraddebt]

Twice bricking my laptop’s ability to do python development because of venv + symlink bs was the catalyst I needed to go all-in on remote dev environments.

I don’t drive python daily, but my other projects thank Python for that.

[kermatt]

How do you brick a machine with venvs?

[bombolo]

He runs pip as root and doesn't use venvs.

[anongraddebt]

By debugging homebrew issues during Moneterey updates.

I didn’t brick the machine, just the ability to setup a typical python venv.

[mixmastamyk]

System administration skills are necessary to be productive developer. There is nothing re: python that can't be fixed with a few shell commands.

[ElectricalUnion]

If a rogue package rm's your root directory as root, you need a bit more that a few shell commands to fix it.

[mixmastamyk]

Can't happen unless you install as root. You're NOT DOING THAT are you?

Also LiveCDs are a thing for about twenty years. Recovery has never been easier, even after hardware failure.

[ElectricalUnion]

It doesn't even need root to cause damage most of the time, it just needs to overwrite all files under your user by mistake.

> Recovery has never been easier, even after hardware failure.

If you can use a LiveCD to repair it, it most likely wasn't a hardware failure to start.

[cwsx]

I've managed to break venv, npm and composer (php).

I don't use that as a reason to choose what I'll use in my projects, that's decided by the PTSD incurred from 7 years of php.