Badabinski

Sorry, I was having a shit day yesterday and made many grumpy comments on the Internet. I could have worded that better.

It should still exclude water. Like, there are ways to equalize pressure that don’t allow for water to condense in the phone like OP’s photo. This is a Bad Thing™.

If he were shooting something bigger than 5.56, then you’d want to try to seat it more firmly in your shoulder. An AR-15/M16 generates pretty negligible recoil, so it’s fine. I used to compete in across-the-course service rifle when I was much younger (before I grew up enough to realize I hated the culture in that community), and I’d have the butt even higher up in my shooting coat’s shoulder if I needed to do so in order to get a good cheek weld. At a glance, his technique looks okay. I’ve no experience with the front grips like that (my AR-15 had no rails for mounting shit), but the rest of his stance seeeeems okay.

I’m guessing that he was a dipshit in other ways and this bad publicity brought the other badness to light.

Not trying to be pedantic, but you recover the body once someone is dead. Rescue specifically means that you’re trying to get to a person before further injury or death can occur. Recovering someone’s remains is done almost purely out of respect for our need for burials and closure. It’s a really solomn and respectful thing that’s not to be taken lightly, so recover is absolutely the right word to use here.

Source: I did some search and rescue training as a kid.

I wrote a comment about this several months ago on my old kbin.social account. That site is gone and I can’t seem to get a link to it, so I’m just going to repost it here since I feel it’s relevant. My kbin client doesn’t let me copy text posts directly, so I’ve had to use the Select feature of the android app switcher. Unfortunately, the comment didn’t emerge unscathed, and I lack the mental energy to fix it due to covid brain fog (EDIT: it appears that many uses of I were not preserved). The context of the old post was about layoffs, and it can be found here: https://kbin.earth/m/[email protected]/t/12147

I want to offer my perspective on the Al thing from the point of view of a senior individual contributor at a larger company. Management loves the idea, but there will be a lot of developers fixing auto-generated code full of bad practices and mysterious bugs at any company that tries to lean on it instead of good devs. A large language model has no concept of good or bad, and it has no logic. happily generate string- templated SQL queries that are ripe for SQL injection. I’ve had to fix this myself. Things get even worse when you have to deal with a shit language like Bash that is absolutely full of God awful footguns. Sometimes you have to use that wretched piece of trash language, and the scripts generated are horrific. Remember that time when Steam on Linux was effectively running rm -rf /* on people’s systems? I’ve had to fix that same type of issue multiple times at my workplace.

I think LLMs will genuinely transform parts of the software industry, but I absolutely do not think they’re going to stand in for competent developers in the near future. Maybe they can help junior developers who don’t have a good grasp on syntax and patterns and such. I’ve personally felt no need to use them, since spend about 95% of my time on architecture, testing, and documentation.

Now, do the higher-ups think the way that do? Absolutely not. I’ve had senior management ask me about how I’m using Al tooling, and they always seem so disappointed when I explain why I personally don’t feel the need for it and what feel its weaknesses are. Bossman sees it as a way to magically multiply IC efficiency for nothing, so absolutely agree that it’s likely playing a part in at least some of these layoffs.

Basically, I think LLMs can be helpful for some folks, but my experience is that the use of LLMs by junior developers absolutely increases the workload of senior developers. Senior developers using LLMs can experience a productivity bump, but only if they’re very critical of the output generated by the model. I am personally much faster just relying on traditional IDE auto complete, since I don’t have to change from “I’m writing code” mode to “I’m reviewing code mode.”

I’m fairly certain that they lend to everyone, not just other tribes. The article makes it sound like the tribes out in the boonies need to do something to survive, and the US federal aid mandated in our treaties is hideously insufficient for their needs. Like, I think that what they’re doing is bad because you shouldn’t harm people, and you especially shouldn’t harm people who are struggling. However, I can at least understand why they’re doing it. I can also see that the society they’re targeting shares responsibility for the situation. If the US had been continuously honoring the letter and spirit of the treaties we signed with the tribes, then the tribes would’ve have to resort to exploitative shit like casinos and predatory lending to make money. People will do whatever it takes to improve their situation, and it’s a shame that the US has failed in this regard.

As an aside and for the sake of clarity, I think casinos are predatory and exploit people who don’t understand their odds, but I’m not against their existence in general, or their existence on reservations. Native American folks can do what they want, it’s their goddamned land, and the consenting adults who go to casinos have a responsibility to themselves. I only bring up casinos because of my perception of them and their presence on reservations.

(Also, fuck non-tribe people that use reservations as a way to skirt US regulations. I had no idea that non-tribe people used tribes as fronts for shitty lending operations. Again, kinda smells like something that could have been prevented with proper federal aid.)

Pig was absolutely brilliant. It totally defied my expectations and left me fucking weeping at the end.

I’d never heard BOHICA before, so thanks for using it!

For others not in the know, it stands for Bend Over, Here It Comes Again. It’s military slang, like FUBAR or SNAFU.

If the root commentor is being serious, then I think it might be a trauma thing. Their profile specifically calls out being queer, and I can imagine many scenarios in someone’s past where conversations about being “masculine” or “manly” were… un-fun, let’s say. I know I felt some uneasiness as I initially read the headline and article summary due to my own childhood experiences. I’ve been told to “grow a pair” and “be a man” too many times for conversations around masculinity to be easy, and that’s as a bi cis man (I can sometimes appear to conform to the societal norms while being true to myself). I’m sure that it’d be much harder for someone who is gay, nonbinary, or a trans woman.

I dunno. I see trauma in so many things nowadays. Maybe it’s there in this case, maybe it’s not, but I figured I’d call it out. Their trauma and the responsibility for managing it and healing from it belongs solely to them if it exists. If they’re being a bad faith actor, then they can fuck off.

This comment is such a beautifully concise argument for the existence of block buttons. Toodles~

They need to do what MacOS and Linux have done. There are safer ways to interact with and inspect the running state of the kernel in those operating systems (eBPF for Linux, a bunch of APIs I don’t know much about for MacOS). Software needs a way to do the shit it’s doing, you can’t just turn it off and provide no alternative.

If Microsoft provides a safe API, then Wine can translate calls to that API and approximate the same degree of protection for Linux boxen.

I also agree with the other person, you should still be allowed to fuck around with the kernel on your own box. Major software vendors should be discouraged from writing shit that directly runs in ring 0, but end users should be allowed to do whatever.

The tiered storage stuff is pretty cool. You can say “I want this data on this disk, so if I get a cache miss from a faster disk/RAM it’ll come from this other disk first.”

I believe it also has some interesting ways of handling redundancy like erasure coding, and I thiiiink it does some kind of byte-level deduplication? I don’t know if that’s implemented or is even still planned, but I remember being quite excited for it. It was supposed to be dedupe without all of the hideous drawbacks that things like ZFS dedupe have.

EDIT: deduplication is absolutely not a thing yet. I don’t know if it’s still on the roadmap.

EDIT: Erasure coding is deffo implemented, however.

What if you need to file a bug? What if you have a question on the config that’s not easily answered by the docs? If you never, ever find bugs and never, ever have questions, then sure, separate the two. There are genuinely people like that, but they’re not common. If you’re one of them, then I’m genuinely glad for you.

My opinion is this: You use software. You don’t use people, but you sure as hell rely on them.

Because Vaxry (the lead dev) got banned from contributing to wlroots or any other FDO projects.

As for why he was banned, this is the only thing I’ve read about the whole thing: https://drewdevault.com/2024/04/09/2024-04-09-FDO-conduct-enforcement.html

Basically, he violated the FDO Code of Conduct when being told that a particular thing he said/enabled in a Discord community would not be acceptable if it was seen in spaces covered by said CoC.

This appears to be his response.

Were you using the kernel module? We’re using Flatcar which doesn’t support their .ko, and we haven’t been getting panics on any of our machines (of which there are many).

Falcon uses eBPF on Linux nowadays. It’s still an irritating piece of software, but it no make your boxen fail to boot.

edit: well, this is a bad take. I should avoid commenting on shit when I’m sleep deprived and filled with meeting dread.

The other person may have responded with a fair amount of hostility, but they’re absolutely correct. I run Kubernetes clusters hosting millions of containers across hundreds of thousands of VMs at my job, and OOMKills are just a fact of life. Apps will leak memory, and you’re powerless to fix it unless you’re willing to debug the app and fix the leak. It’s better for the container to run out of memory and trigger a cgroup-scoped OOM kill. A system-wide OOM kill will murder the things you love, shit in your hat, and lick your face like David Tennant licked Krysten Ritter.

For blood (and especially old dried blood), I’ve found that oxiclean in cold water works well. Fill a bucket with a small amount of the hottest water you can and put some oxiclean in. Give it 30 seconds to dissolve, then fill the bucket up with cold water (follow the instructions for quantities of oxiclean and water). Then, put your bloody garment(s) into the cold water and let them sit for about 6 hours. Remove from the water, gently press some water out, and immediately launder your clothing as you normally would. If there’s still blood, do another cycle before washing.

Don’t do this if the care tag specifically excluded any form of bleach. In my experience, it works especially well on period stains.

Ahhh, I’d love it if I could tie that in with a Bluetooth OBD dongle and Home Assistant. It’d be awesome if I could set up a BLE proxy in my carport to automatically update stuff. It’d be especially handy if I could get alerted about check engine codes.

Hey! Boeing! There’s a saying that’s popular amongst lawyers—“if you must eat crow, do so while it is fresh.”

The uh, crow is already pretty fucking old. Best to just eat it now before you get it shoved down your throat by the DOJ.