Nice. Imagine the lady in the post’s face when she learns that “oom badness” is how they decide which child to sacrifice.

What’s that from?

Idk, if you don’t get too flummoxed by “stranded preposition” and “relative locus,” the rest is pretty plain IMO.

Kernel Panic at the /dev/disk/0

Yeah lol I’m familiar with “kill child” in a process management context, but I’ve never seen the word “sacrifice” come up. Is that a thing?

unexpectedinterrobang

Lol you just saw “stranded preposition” and bailed, hey?

Hack with benefits!

Is it really less secure than a password? How so?

Ah, you’ve never worked somewhere where people regularly rebase and force-push to master. Lucky :)

I have no issue with rebasing on a local branch that no other repository knows about yet. I think that’s great. As soon as the code leaves local though, things proceed at least to “exercise caution.” If the branch is actively shared (like master, or a release branch if that’s a thing, or a branch where people are collaborating), IMO rebasing is more of a footgun than it’s worth.

You can mitigate that with good processes and well-informed engineers, but that’s kinda true of all sorts of dubious ideas.

You can get in some pretty serious messes, though. Any workflow that involves force-pushing or rebasing has the potential for data loss… Either in a literally destructive way, or in a “Seriously my keys must be somewhere but I have no idea where” kind of way.

When most people talk about rebase (for example) being reversible, what they’re usually saying is “you can always reverse the operation in the reflog.” Well yes, but the reflog is local, so if Alice messes something up with her rebase-force-push and realizes she destroyed some of Bob’s changes, Alice can’t recover Bob’s changes from her machine-- She needs to collaborate with Bob to recover them.

I gotta say, I was with you for most of this thread, but looking through old commits is definitely something that I do on a regular basis… Like not even just because of problems, but because that’s part of how I figure out what’s going on.

The whole reason I keep my git history clean and my commit messages thoughtful is so that future-me (or future-someone-else) will have an easier time walking through it later, because that happens all the time.

I’ll still almost always choose merge instead of rebase, but not because I don’t care about the git history-- quite the opposite, it’s really important to me in a very practical way.

Yeah, tbh the “no timezones” approach comes with its own basket of problems that isn’t necessarily better than the “with timezones” basket. The system needed to find a balance between being useful locally, but intelligible across regions. Especially challenging before ubiquitous telecommunications

Imagine having to rethink the social norms around time every time you travel or meet someone from far away. They say “Oh I work a 9-to-5 office job” and then you need to figure out where they live to understand what that means. Or a doctor writes a book where they recommend that you get to bed by 2:00PM every night, and then you need to figure out how to translate that to a time that makes sense for you.

We’d invent and use informal timezones anyway, and then we’d be writing Javascript functions to translate “real” times to “colloquial” times, and that’s pretty close to just storing datetimes in UTC then translating them to a relevant timezone ad hoc, which is what we’re already doing.

That’s what my rational programmer brain says. My emotional programmer brain is exactly this meme.

I have two of em-- They’re pretty good! Definitely not perceptibly laggy or anything, at least to me.

Probably just outed myself as a casual.

Yeah, I get that. Do you have any sense of whether that’s a limitation of the ESP32, or with your implementation?

If anyone else was wondering, I found this neat data table of controller latencies to compare:

https://rpubs.com/misteraddons/inputlatency

It looks like 18.35ms is not really among the best, but there are still lots of products in that range.

I dunno if I’d say your project didn’t work out… Maybe more like you succeeded but still have work to do. Do you think you’ll try swapping the Bluetooth for a 2.4Ghz module or something and see if that performs better?

Lol yes, people would often rather avoid getting involved with a piece of software at all (and perhaps complain about it), instead of taking over the burden of developing and supporting it themselves. Kids these days, right?

Great, I knew you could understand if you wanted to (hence the “deliberate” part).

So… Yes. Exactly. The complaint is about poor choices in the implementation of the project’s community. Not everybody who would want to use the software (e.g. Typst, in this meme) knows how to code at all. Those people are reliant on the community for support, and may choose to avoid a project if the community isn’t good for them. That’s the premise of the meme, and orthogonal to any properties of the version control system.

Among those who can code, it’s still reasonable that someone might consider the community when evaluating the cost of integrating the project… Especially if they plan to be an end-user of the application.

It’s great if you grok the source of every project you use and accept the burden of maintaining them yourself in lieu of a good community. That’s really neat. But I don’t think it’s practical for everybody to do that for everything they might want to use… Yes, even though the Fork button is right there.

Haha that’s not the issue, but it’s pretty clear that you’re deliberately misunderstanding at this point.

Fork… what? The software project that you’re trying to get help with? The problem isn’t that you need to change the code, the problem is that you want to be able to leverage the community.

“Starts” lol. They are way ahead of you, my friend.

I recommend reading Discord’s Terms of Use and Privacy Policy some time. It is… more eyebrow-raising than usual.