To be honest I prefer this type of communication over the I-can't-believe-it's-not-layoffs that my previous employer was doing. At least it's honest that it is a decision they've made.

I ran in to a couple problems when trying that script (details below), but I'm really happy that you shared it, because I had not seen ':windo diffthis' before, and that method of scripting diffs. I'll definitely be customising it!

(I found that my mac machine doesn't support the '-printf' option, and also I was attempting to run 'git bvd main' on a branch but it seems it does a recursive directory diff, so I'll use 'git diff --name-only' as the input to the awk command).

Edit: worked nicely! I haven't used tabs much in vim so is a slightly new workflow but otherwise very handy

I've also found llms seem to love it when calling out to tools, I suppose for them having stderr interspersed messaged in their input doesn't make much difference

The level of engineering and problem solving needed for such a charming game just brightens my day. I remember the post about ssh keystroke obfuscation as well, and I really enjoy how limiting yourself to smaller systems forces you to solve problems that people don't usually see.

This is concerning, it feels a bit tragedy-of-the-commons I suppose where having public tests are a valuable public good, thought I can't quite get the analogy straight in my head.

> feels a bit tragedy-of-the-commons ... I can't quite get the analogy straight in my head

I have a personal theory that "tragedy of the commons" has a very specific meaning, and beyond this meaning it just adds confusion. This isn't your fault - it's an overused phrase.

I'd try to examine the root of your discomfort. Why does it make you feel bad? Avoid thinking about "big ideas" like the commons or the public good.

It was a joke.

The joke is that its not open source?

I've been thinking through what features I'd want in a language if I were designing one myself, and one of my desires is to have exhaustive matches on enums (which could be made of any primitive type) and sum types. The ability to generate perfect hashes at compile time was one of the things that falls out nicely from that

There's so many times where I realise what I thought was simple in C turns out to be a minefield. I'd assumed an enum was 'word' sized, so 64 bits on a 64 bit architecture, but instead it turns out to be unspecified, and left up to the compiler.

Thinking through the standards quote again, I'm not sure that MSVC's behaviour is even wrong (when not using C23 type specification)? Because it doesn't look like it's required that the underlying type has to be sufficient to represent the largest enum. So maybe it's not wrong, it's just ... broken.

Wow TIL thankyou! I've got a bunch of small things like this in my current project that always complicate my PRs, this will solve that handily.

This was really interesting. Man pages are at the same time really useful, while being arcane and frustrating to use. I still never remember is it 'man 1 read' or 'man 2 read' for libc vs the bash 'read' command (checking now 1 is the builtin, 2 is libc). Yes I know about 'man man', but it won't stick in my brain which is which.

They also lack discoverability, I just checked man 1 through 5 of 'open' and 'man 3 open' is a random perl pragma, which is not what I'd expect

For all the negativity on github I will praise them for one really good feature - code search across an organisation. I've found it really useful particularly for 'platform' related changes to be able to find how other people in an org has solved a problem. It's particularly useful when the documentation only shows the happy path (or was written 5 years ago and 'oh nobody does it that way anymore')

The raft of outages lately (my company was disrupted by I think four last week?) have certainly (and deservedly) created some pent-up frustration. I'm personally frustrated with its poor performance on Safari.

Overall, though, it's ... fine. That's all. A little worse than it used to be, which is frustrating, but certainly nowhere near unusable. I stood up my own forge and mirror some repos to it. The performance is almost comically better. I know it's not a fair comparison: I have only one user. On the other hand, I'm on a 9-year-old Xeon located geographically farther from me than GitHub's servers.

I'm largely happy with GitHub though for public GitHub at least, search is now terrible - it doesn't seem to return anything when not logged in and if you are logged in the filtering options are limited (this was the case mid last year anyway - maybe it's improved but I've given up trying to use the web search).

Whatever the motivations are, at least the end result is moving to freer (non-proprietary) and sometimes self-hosted solutions. If virtue signaling is what it takes to get there, I would like more of it. Virtue signaling gave us quality universities and museums, after all...

Is that a unique feature to GitHub?

No I think all the platforms have roughly similar features (it's not too hard - I built a toy one in a weekend using sqlite's fts module), but the speed and usefulness seem much better than the other platforms I've tried

No, Gitlab has it too (don't know about the others offerings). Gitlab integrates Advanced Search via Elasticsearch, last I checked they had plans to make zoekt available as an alternative.