Thanks. I remember one of these had people being excited about it and I felt bad that I couldn’t try it. But Linux is hard and we are all so grumpy. I get it.

Is that the Mac only one?

Windows -> RedHat -> Windows -> Gentoo -> Ubuntu -> RHEL -> Ubuntu -> Debian -> Arch

Do folks still use logstash here? Filebeat and ES gets you pretty far. I’ve never been deep in ops land though.

The point of the license combination they use is to allow the enterprise version to be open and live in the same repo as everything else. Dunno if that’s what they do, but that’s why the elastic license exists.

The only surefire way is to read it all. And understand it all. That ain’t happening though. So you decide how much to do.

You should figure out how many people are landing patches and get a rough sense of why. Same for folks filing issues or talking about the project in general. Maybe you trust one of the contributors for some reason. Either way, you want to know how alive the project is.

You could land a patch.

You could spot check parts of the code.

You could run vulnerability scanners on it.

I dunno. It’s hard.

I’m not sure I’d attach any meaning to real names online. There’s a whole group of us whose online names are just things they thought were neat when they were 12. And they’ve just stuck forever. There’s lot of reasons.

But otherwise, yeah. I’ll spend ten minutes looking up someone’s online profile. Mostly for GitHub if I can find it. If someone’s commenting on public prs and seems nice that’s a big signal.

I agree. Light touch until you have a bunch of changes landed.

I was a professional open source contributor for a while. Still have the same job, but the license changed. Culture still quite similar though.

I review a ton of code and have a bunch reviewed in turn. I don’t remember that last time I’ve had this come up. Either direction really. I guess I’m lucky. We just split naturally in similar places.

I think it’s a bad analogy because it’ll distract some people.

I believe they were referring to this: https://youtu.be/9eyFDBPk4Yw?si=sb_v_EPhTM9C6bZZ

I imagine a delta encoding scheme similar to what the time series DBs use would work well for the geo points. Maybe even a delta-of-delta encoding for things like ships which move very consistently.

It’s probably not worth it given how small they’ve already go their data. But it is fun.

I don’t believe Prometheus supports geospatial data. Two minutes of googling though, so I could be wrong.

It sort of looked like you’d construct the key by input. Like an old school password entry screen or something. I wonder if you could correct horse battery stapler it enough to have a respectable key length.

It’s not just Google. If you enjoy that sort of thing there are industries where it’s more important. Not every day. Not every team. And you’d have support like you say.

But you can go a lifetime without using it beyond rules of thumb.

I think Linux has grown beyond the good will from contributors. I got the sense most folks do this as part of their job.

So it’s not your boss. It’s someone who you have to make happy to do your job. And your boss can’t help. Quitting won’t help. Not if you want to work on the kernel.

It really does drive people away. I’m not good enough for the kernel, but there’s a project I could contribute to as part of my job but I don’t because there are mean folks there. My first contribution there was met with cursing.

I was never a fan either. Doki Doki Literature Club was good though.

I like this video with it.

Sorry. I wasn’t clear. If the conditional is constant a compile time you get the dead code optimization. The path not taken is removed. If it’s not constant at you may get the loop invariant movement. But only if the compiler can tell that it’s invariant.

My point wasn’t that you should always rely on this behavior. At least, I didn’t mean to say that. I suppose what I should have said is more like “in many cases you won’t see any performance difference because the compiler will do that for you anyway.”

I suppose I have value judgements around that like “generally you should do the thing that is more readable and let the compiler take care of stuff like moving the loop invariant”. That’s been mostly true for me. But only mostly.