Breath on your fingers like you’re trying to fog up glass. Immediately open by running your fingers in opposite directions along the edge, using the additional friction you created.

How broken are we talking here? Like, installation is kinda borked but technically works broken, or purge it with fire and salt the storage medium broken?

I have often busted my machine learning rig as it runs an ancient (but spacious VRAM) GPU. If I upgrade the drivers by accident, it takes an average of 1-2 days to make everything happy again.

I used to be more cavalier with my boot partitions; I am no stranger to a busy box for repairs. Best moments are when I used to try and adjust a live partition to make more room for the swap partition (or vice versa).

I have screwed up more Raspberry PI installations than I care to count. Usually by my own hand.

I have completely broken Xwindows multiple times due to drivers, trying to go between desktop environments, and most frequently trying to get video cards to work that aren’t natively supported.

Friend, while I appreciate the time and effort on the docs, it has a rather tiny section on one of the truly worst aspects of pip (and the only one that really guts usability): package conflicts.

Due to the nature of Python as an interpreted language, there is little that you can check in advance via automation around “can package A and package B coexist peacefully with the lowest common denominator of package X”? Will it work? Will it fail? Run your tool/code and hope for the best!

Pip is a nightmare with larger, spawling package solutions (i.e. a lot of the ML work out there). But even with the freshest of venv creations, things still go remarkably wrong rather quick in my experience. My favorite is when someone, somewhere in the dependency tree forgets to lock their version, which ends up blossoming into a ticking time bomb before it abruptly stops working.

Hopefully, your experiences have been far more pleasant than mine.

More context: https://www.langton.cloud/python-pip-requirements-txt-lock-file/

Hahaha!..

Oh shit, you’re serious.

It’s all fun and games until the wheel variant you need for your hardware acceleration package conflicts with that esoteric math library you planned on using.

Windows 11 is trash. Microsoft kept boasting it was “faster” than 10, but it is (unsurprisingly?) heavy in some weird areas, including a less snappy start menu, more telemetry, invasive integration with their software, you name it. Tried one machine in my collection to try it via an upgrade (a Microsoft Surface Pro 6), and the performance was so bad I ended up going back to Windows 10. Multi-second lag just to get to the program shortcuts is a really bad sign.

Yes. So much yes.

Sure, at least half of the FAANG use Linux. But they use a homegrown Linux flavor often maintained by an entire dedicated team. Not some random ass Ubuntu or Mint ISO you downloaded; these images are custom tailored to the workflows, dev needs, security needs, and even package management needs of the corporation. They often carry a complete profile template that integrates with whatever they’ve chosen to enforce authentication, have a lavish on-board remote monitoring system, you name it.

This won’t hold true if your RAM gets to the limit, and you end up creeping into swap space. If you do, everything becomes a potentially streamed asset! While certainly not ideal, you’ll feel it harder on a HDD vs. SSD. Remember, you need at least 16GB of RAM for this monster, which these days is basically standard on most PCs (and about 70% of all Steam users as of August have no more than 16).

Maaannnn… I got another steering wheel. Anyone willing to trade for an ignition system? I’ll settle for two NPCs who will get out and push!

This is the real answer to this question. Not just an invention to unfairly evaluate folks (and charge them originally to see it!), but nothing more than a “how much we can fleece you for” score that has become so widely embraced you can’t ignore it.

Let’s not forget HP making an “update” that effectively self-destructed the printer for use if you don’t use their cartridges. Evem after the public outcry and back pedaling by the company with a new bios update, my printer still “manifested” the same problem they intentionally introduced.

Replaced parts, tried other things, then just said “forget it” and replaced it with a more expensive color laser from a competitor. Happiness and reliable printing ensued.

Yeah, and this only gets worse with bigger monitors. Want to use that 43" TV as Monitor #3? Wigglin’ isn’t going to help.

Real users give up and start using keyboard shortcuts to move crap around until they find it again.

Or just get a wireless gaming mouse with adjustable DPI, crank it up to 11 billion, and try to catch it doing near lightspeed as it goes through all four monitors at once. The only drawback is that, according to physics, it will likely have experienced time dilation, which means your mouse cursor has aged significantly in the short time it was in flight.