Badabinski

OP is in the US, so no 3 phase power unfortunately ):

Was this done according to proper clean-room design principles? If so, then imo the GPL is still working as intended. The company had to spend a fuckton of money and time getting one engineer to read the source and describe what was done to other engineers, and then ensure that one engineer never ever worked on the project again.

If they didn’t do that then they violated the GPL and someone should report them to the SFLC.

Relevant XKCD.

It’s amazing that he released the game for free, given the amount of time he’s spent on it.

I hadn’t even thought of that! I did some oxyacetylene welding many moons ago and I remember the heat being absolutely intolerable at times.

I do machining as a hobby now and I’d really like to filter out cutting oil smoke. My biggest fear using a PAPR is my shop is the hose—I’d need to find a way to keep it REALLY close to my body. I don’t want to get pulled into my lathe face-first.

I very much want a PAPR as well. I seem to recall that there were some units that came out of COVID that are somewhat cheaper, at least.

I feel despair every time this project comes up ): I really like the idea of rewriting coreutils in rust, but GNU-compatible coreutils in a permissive license is just asking for trouble…

If you’d like to learn more about Bash itself, this is an amazing resource: https://mywiki.wooledge.org/BashGuide

Probably the ONLY place on the internet that will teach you to write safe shell scripts. Most shit on StackOverflow (and consequently, most shell generated by LLMs) is dangerous garbage.

Open source can be enshittified. FOSS with many contributors should be basically proof against being fucked with.

Yep, that’s my use-case. I am not interested in unlocking the door, only locking it.

This script is why I ended up learning how to use OnShape. It’s probably much better nowadays, but I could not get it working a few years ago. I needed CAD and OnShape was close enough to Inventor that it was almost frictionless.

Honestly, I don’t think the tooling would be too terrible. Ron Covell has been making crazy shit out of sheet metal using nothing but hammers and simple wooden forms for many years, and I think it might be possible for OP to do the same. Granted, it would be hideously time consuming and would require great skill, but I think it’d be doable.

Here’s a link to the CVE itself, which has useful details: https://nvd.nist.gov/vuln/detail/CVE-2025-38352

Yep, my org had a Falcon sensor outage take out tens of thousands of Linux servers. Fuck Crowdstrike. Also, fuck Windows and fuck Microsoft.

I’ve been on a Lethal Company kick for a few months. I’ve been getting super involved in the “high quota” scene, where people try to get the highest quota possible. It involves a lot of crazy tech and good team work, and I’m really enjoying it.

Yep, taking some care early on can pay dividends down the road. The data structures you choose really matter, and YAGNI can stop you from going overboard with indirection and other shit. Premature optimization is bad, but there’s nothing wrong with writing performant software as long as it’s still comprehensible and extensible.

Anubis has worked if that’s happening. The point is to make it computationally expensive to access a webpage, because that’s a natural rate limiter. It kinda sounds like it needs to be made more computationally expensive, however.

Do you have any sources for the 10x memory thing? I’ve seen people who have made memory usage claims, but I haven’t seen benchmarks demonstrating this.

EDIT: glibc-based images wouldn’t be using service managers either. PID 1 is your application.

EDIT: In response to this:

There’s a reason a huge portion of docker images are alpine-based.

After months of research, my company pushed thousands and thousands of containers away from alpine for operational and performance reasons. You can get small images using glibc-based distros. Just look at chainguard if you want an example. We saved money (many many dollars a month) and had fewer tickets once we finished banning alpine containers. I haven’t seen a compelling reason to switch back, and I just don’t see much to recommend Alpine outside of embedded systems where disk space is actually a problem. I’m not going to tell you that you’re wrong for using it, but my experience has basically been a series of events telling me to avoid it. Also, I fucking hate the person that decided it wasn’t going to do search domains properly or DNS over TCP.

Debian is superior for server tasks. musl is designed to optimize for smaller binaries on disk. Memory is a secondary goal, and cpu time is a non-goal. musl isn’t meant to be fast, it’s meant to be small and easily embedded. Those are great things if you need to run in a network/disk constrained environment, but for a server? Why waste CPU cycles using a libc that is, by design, less time efficient?

EDIT: I had to fight this fight at my job. We had hundreds of thousands of Alpine containers running, and switching them to glibc-based containers resulted in quantifiable cloud spend savings. I’m not saying musl (or alpine) is bad, just that you have horses for courses.

Is it? I thought the thing that musl optimized for was disk usage, not memory usage or CPU time. It’s been my experience that alpine containers are worse than their glibc counterparts because glibc is damn good. It’s definitely faster in many cases. I think this is fixed now, but I remember when musl made the python interpreter run like 50-100x slower.

EDIT: musl is good at what it tries to be good at. It’s not trying to be the fastest, it’s trying to be small on disk or over the network.