If Mercurial were as popular as Git I would presume that it would be rewritten in C or Rust, but who can say.

Also Subsurface, a scuba diving log program, but that one is not quite as well known.

https://subsurface-divelog.org/

Buddy’s probably running code he got from GitHub Copilot that is used to do a visualization of a bubble sort for learning purposes.

What is this, a table for ants? Because that’s the average number of ants in an ant colony and it’s nowhere near an impressive amount of rows to be doing any sort of processing on. It wouldn’t be an impressive amount of rows if your rig was an i386DX-33 running off a 5” floppy.

I think it’s for any motor vehicle where tipping is likely. See this page with all sorts of pictures and examples, including old packaging.

https://sprudge.com/no-spill-mug-feltman-langer-160969.html

How would trickle down work with gold? I’m picturing some kind of golden shower?

deleted by creator

“What one programmer can do in one month, two programmers can do in two months.”

“What one programmer can do in one month, two programmers can do in two months.”

The code directly below:

function getPathToUploadDirectory() {
  return config.tmp_path
}

Riker and Troi learn a life lesson and the exit the holodeck.

She was also part of the team that discovered and coined the term “bug” in relation to a computer defect. She didn’t invent the term herself directly, but she was part of the team that did.

macOS has something to this effect where if it detects too many kernel panics in a row on boot it will disable all kernel extensions on the next reboot and it pops up a message explaining this. I’ve had this happen to me when my GPU was slowly dying. It eventually did bite the dust on me, but it did let me get into the system a few times to get what I needed before it was kaput.

The contacts inside are too big and sensitive and it results in phantom inputs. The DIY fix is to open up the controller and literally cover parts of the input contacts with tape.

Ligature, not lineature.

“What one programmer can do in one month, two programmers can do in two months.”

I wouldn’t say quite the same root cause — the xz back door was clearly intentional, but I don’t recall the Heartbleed bug having been intentional, and developer responsible has denied allegations to that effect. There can be no doubt in the xz case of malicious intent.

That’s easy, just create new accounts every time you login.

The performance improvements in v4 are for compilation times, not rendering.

Learn to use git bisect. If you have unit tests, which of course you should, it can save you so much time finding weird breakages.