Are homemade PCBs really that effective? I’d wanted to try my hand at them but never could settle whether it was worth attempting.

Yeah I got it completely wrong.

Yeah that one’s on me. I did Google lens it, but I realized I had no hope of knowing what glyphs those were, I just assumed Japanese cause idk. But good call.

Works fine for me on first glance, with ETP set to strict. Perhaps due to the recent domain cut-over in the web stack?

If it wasn’t obvious that the Debian box is a parody, here’s what the Japanese Chinese text along the top reads on each box:

Please read the instructions carefully and use it under the guidance of a physician. It is strictly prohibited to be used in food and feed processing.

Please read the installation instructions carefully and use it under the guidance of the administrator. It is strictly prohibited to use for server installation.

so yes, the title is correct-- this is not a coincidence, the Debian box was made explicitly for this joke

edit: thanks for the correction folks, honestly thought it looked more like Japanese than Chinese at first glance and I am obviously not an expert in either. Appreciate the call-out, very deserved.

Translation: “HELP I JUST BOUGHT THIS THING OFF AMAZON THAT’S SUPPOSED TO GIVE ME FREE TV TO DISTRACT MY KIDS BUT NOW ITS SAYING THINGS I DONT UNDERSTAND AND IM SCARED”

Also, please someone send her a L1ZY

Just give up hope. It’s really not worth it.

I loved Pop!_OS as it made Debian/Ubuntu extremely usable as a daily driver. Finally I got fed up with outdated package bullshit coming from different angles and went to Rocky. Wish I did it sooner.

Appreciate System76, but they’ve dropped the ball hard and I don’t think it’s recoverable

Red Hat

No, you’re angry at IBM. When news of the IBM acquisition broke, sector veteran colleagues I’m close with moaned and groaned that IBM was sure to do something to piss everyone off again, which was apparently their habit a couple decades back. Sure enough, they could not have been more accurate in their assessment.

Turns out IBM is three hot messes in a trenchcoat and always has been. Hence why they have already lost the Quantum wars and likely the GenAI wars as well. One AI vet I know says they’re posed to even lose the AI war altogether, which is pathetic given the groundwork provided by Watson alone.

you have to flip the mouse on it’s back to charg it how tf is that logical

nevermind the fact that you don’t need to make legacy compatibility a hassle. The Darwin kernel should still maintain backwards compatibility and if it doesn’t then LMAO

Linux is freedom, Windows is serfdom, Mac is just dumb.

Idk about hierarchy but PATH is a thing and the proper terminology is filepath, so the word path becomes ambiguated as it could be used to refer to either. Hence why I say it is bad practice to use it as a primary reference in conversation. Otherwise you’ll get interns and users modifying their PATH for no damn reason and wondering why nothing works.

As long as you don’t call it a path.

If I were to fully elaborate, I’d be typing for hours, so I’ll sum up:

• pip - default behavior is to install to system-wide site packages. In a venv, it will try to upgrade/uninstall system packages without notice/consent unless you specify --require-virtualenv. Multiple things can fuck up your ENV to make the python binaries point to system-wide, while your terminal will still show you as in a venv. Also why TF would package metadata files need to be executable? Bad practice, -1/10
• nix - they acknowledged years ago that they should probably have some kind of package signing and perhaps an SBOM or similar mechanism, but then did nothing to implement it and just said “oh well, guess we’re vulnerable to supply chain attacks, best not to think about it”
• brew - installing packages parallel to your system packages manager, without containers. My chief complaint here is that brew is a secondary package manager that people might treat as a “set and forget” for some packages, rarely updating them. So what happens when a standard library used by a brew package is vuln? A naive Linux user might update their system packages but totally forget to update brew. And when updating brew, you can easily hit max_open_file_descriptors because kitchen sink

From there, it’s all extremely nit-picky and paranoid-fueled-- basically, none of the package managers I mentioned are conducive, in my eyes at least, to a secure and intuitive compute environment.

Unfortunately, there’s not much I can do about it except bang pots and pans and throw maintainers under buses when the issue that has been present for years rears it’s ugly head. Because they are the only ones who can change this, and pressure is the only thing that might motivate them to.

Nix is already beyond fucked because they actively dismiss the need for appropriate security measures to prevent supply chain attacks. There were multiple discussions about this over the years that appear to have succumbed to neglect.

I wouldn’t trust nix, just like I don’t trust pip, brew, or a whole plethora of other package managers and repositories. They are just too neglectful

This deserves a ban imo

Yeah and that makes sense. But I still choose to die on the hill of tabs or nothing. That’s just how anal I am about my code.

And I realize there are niche scenarios where tabs don’t make sense, but I could care less about those. Afaik, even assemblers support tabs. If you have tabs, I feel it is almost sacrilegious not to use them for indentation.

Yeah I liked him better then /s

I will fight tooth and nail with anyone who agrees with this decision. Not because Torvalds did it, but because fuck you use tabs you goddamn neanderthals

arch security

the decades long joke still keeps paying dividends. well done to trolls that kick-started the whole thing.