(Disclaimer: I haven't seen the video yet. But yeah.)
That's a quantum mechanics thing. And quantum mechanics has a long history of making physicists and physics students really uncomfortable. The following two quotes illustrate just how fucked up quantum mechanics really is:
God does not play dice
Albert Einstein
I don't like it, and I'm sorry I ever had anything to do with it.
Erwin Schrödinger
Before quantum mechanics, our Newtonian understanding of the world was really simple. We thought particles were little billiard balls floating around and bumping into each other and being attracted and repelled by electric fields and such. But nope! Turns out you can't even conceptually understand what's going on at that scale without making the observer/measurer/measurement a central feature of the literal math. But if you don't do the uncomfortable things in the math, you can't get results from the math that match what happens in the real world.
W.
T.
F.
Seriously. You're asking exactly the right question. The question that made the discoverers of quantum mechanics uncomfortable in the first place. Unfortunately, there's no one answer to it. There are a bunch.
In practice, you don't really have to have "the answer" to that question to design functioning solid-state storage devices or predict the half-life of a muon. You can just kindof throw up your hands and take it for wrote that "the spin doesn't exist until it's measured" (nor the position nor the velocity nor any of a bunch of other such properties of the particles in the system). But it's not like physicist don't still have this question in the back of their minds keeping them up at night.
Cura's a fantastic slicer, but kindof a terrible program. They gave up on ARM support a while ago. And their dependency situation is majorly out of control. To the point that Gentoo has literally given up on supporting it and maintaining a working package.
For customers to hire them. Yeah, ok. That makes more sense. I mean, in the same way hostile architecture makes sense, but at least now I understand what they're trying to accomplish and how the machines further their fucked-up goals.
I don't understand. If they want people to stop seeking temp jobs there, wouldn't just always turning people away when they ask for day labor work? (And maybe put up a sign that says "we'll never give you day labor".) And given that they've gone to the length of installing machines, surely they already do always turn people away, in which case why are people braving the noise machines to wait to be turned away?
Is this people hoping that customers will hire them for a day job for like... assistance with building a deck or whatever?
Before I read the body of the post, I was going to recommend "gl;hf" (the only podcast I've really listened to in quite a while), but they don't stay on topic. There is no topic, really. It's just rambling about whatever comes to them as it comes up.
At the beginning of every episode, they start with "welcome to gl;hf, the world's first podcast in gaming." And the running joke is that they rarely talk about gaming at all.
Largely they talk about being prolific career YouTube content creators, but they may delve into random stuff like the U.S. National Cheese Reserve or the ethics of eating lab-grown human meat or Uncle Wiggily board games.
On the plus side, they're always interested in what they're talking about.
Here's my GitLab. None of it's "active" really. I'm the only contributor to most things I have on GitLab. At least some of the things there, if they started getting attention and interest, I might very likely make them active. But for now, they're just out there and may or may not receive further updates. Though I'm working on other projects I specifically intend to publish as FOSS in the future.
Simple-CSS-Shrinker was made for a web-based game I wrote back in the day. I ought to dust that game off and publish it.
JeSter, the JS tester. A really simple JS unit testing framework that runs in a browser and doesn't require Node or V8 or anything. Made in service to the same game I mentioned in the previous item.
pystocking was basically in service of hydrogen_proxy
hydrogen_proxy is a "scriptable HTTP proxy" written in Python. Definitely intended for privacy kind of applications. But it's kinda slow. I have in the back of my mind to rewrite it in Go, but it's not high on my priority list. (I'm honestly mulling the idea of quitting the use of browsers all together if I can wrangle a way to do that that doesn't involve switching to a bunch of proprietary software. The main browsers are bullshit these days.)
GoVTT was written because I wanted to play a TTRPG with friends remotely. It's a web-based virtual tabletop application that you can self-host. I may some day offer hosting for it. (Like, if you want to use it but don't want to be bothered to go through the hassle of hosting it yourself, maybe I'll offer to host it for a small fee.) No guarantees, though, except that it'll always be FOSS and it'll always be an option to self-host.
codecomic is a domain-specific language for making simple webcomics or story boards. I made it because I wanted to be able to include webcomics/story boards in my game mastering notes, which are managed with a system that I should also publish as FOSS.
My main side-projects right now that I haven't published yet are:
A domain-specific language for building 3d game assets. Roughly speaking, FreeCAD is to OpenSCAD as Blender is to what I'm currently working on building. (It's in the early stages right now. I intend for it to be able to do modeling, rigging, animations, textures, normals, etc. All in the DSL's syntax. I'm making progress, but of course that project is ridiculously ambitious. We'll see where it is in a year.)
A framework for rapidly prototyping 3d-printable mechanical keyboards. (Also pretty ridiculously ambitious.) The image below is a sneak peak at the first keyboard I'm intending to build with it. Some day.
That's... kindof the question, isn't it?
(Disclaimer: I haven't seen the video yet. But yeah.)
That's a quantum mechanics thing. And quantum mechanics has a long history of making physicists and physics students really uncomfortable. The following two quotes illustrate just how fucked up quantum mechanics really is:
Before quantum mechanics, our Newtonian understanding of the world was really simple. We thought particles were little billiard balls floating around and bumping into each other and being attracted and repelled by electric fields and such. But nope! Turns out you can't even conceptually understand what's going on at that scale without making the observer/measurer/measurement a central feature of the literal math. But if you don't do the uncomfortable things in the math, you can't get results from the math that match what happens in the real world.
W.
T.
F.
Seriously. You're asking exactly the right question. The question that made the discoverers of quantum mechanics uncomfortable in the first place. Unfortunately, there's no one answer to it. There are a bunch.
In practice, you don't really have to have "the answer" to that question to design functioning solid-state storage devices or predict the half-life of a muon. You can just kindof throw up your hands and take it for wrote that "the spin doesn't exist until it's measured" (nor the position nor the velocity nor any of a bunch of other such properties of the particles in the system). But it's not like physicist don't still have this question in the back of their minds keeping them up at night.