![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
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.
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?
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.
We squash. I’m not really interesting in your local journey to land the change. It’s sometimes useful during review, but after that it’s mostly the state of the main branch I care about. It’s what I need to bisect anyway.
I don’t like commits that are just references to issues. Copy the issue into the commit message so git blame
tells you something useful. Unless it’s just closing a simple big. Then the title and issue reference are plenty.
Depends on the project I imagine.
I wonder what my last commit at each job was. I’ll bet it was boring. About 10% of my commit messages are genuinely interesting.
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.
I think the last new instruction the JVM added was invokedynamic like 10 years ago. I believe they did it so lambdas could be called efficiently. Polymorphic incline cache and stuff.
But the JVM has grown more complex in other ways. The way to force simd instructions is pretty wild, for example.
I don’t know enough to call it a mess or not. It works though.
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.
I read it when I was YTs age. Then listened to it when I had kids that age.
My memory is hazy but I think it was this: https://arstechnica.com/tech-policy/2013/04/wikipedia-editor-allegedly-forced-by-french-intelligence-to-delete-classified-entry/
I used to work for them. It was weird and wonderful and I miss it and I don’t. Lots of mission driven folks working hard to keep things going getting very little respect. But a lot of respect. But sometimes none.
Iirc a lot of their budget is spent doing charity stuff. Encouraging contributions for tiny languages. Trying not to cave to Russia or the US or France. Trying to make it less of a boys club. Trying to get local organizations going.
I remember once they sent an email that said “if the French government asks you to delete this page please just delete it. It’s not worth going to jail. Someone outside of France will revert the delete.”
I wasn’t qualified for the work. No one was. But it was honest work.
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.
Usually I use glob patterns for test selection.
But I did use reges yesterday to find something else. A java security file definition.