> it was pushed all at once

For some of my projects I develop against my own private git server, then when I'm ready to go public, create a new git repo with a fully squashed history. My early commits are basically all `git commit -m "added stuff"`

Do you have any criticism of the content, or just "I don't know the author"?

They didn't say "this is in error", so they don't need any such example errors. They also didn't say just "I don't know the author".

The largest country on the planet is chasing solar and electrification

So much this, 'murricans are still struggling to grasp a reality where they're not in the planet's driver's seat anymore.

Using AI you can write a naive scraper in minutes and there's now a market demand for cleaned up and structured data.

My Apple Sillicon macbooks are the coolest running computers I've had in decades. Something might be wrong with your cooling system.

Most Macs (both Intel and Apple Silicon) refuse to thermal-throttle until they reach the junction temp.

Both you and the parent can be correct, here; many Macs are quite cool at idle, but also throttle much slower than equivalent Intel or AMD chips under load.

The big banks (unless they do fraud again), health insurance companies in the US, the major telecoms, Airbus, Bayer, Tyson, JBS SA, Nestle, PepsiCo, Coca-Cola, Anheuser-Busch, Cargill

This would have been great when I was learning Lisp in school! I tried emacs but due to joint issues the keybinds were painful to use, so I gave up and did the course in vim+SBCL's REPL instead.

It is fairly common for emacs users to bind Ctrl or Meta to caps lock for improved ergonomics. There's also a bunch of RSI sufferers that are using foot pedals, which actually makes a lot of sense.

I personally switched to emacs for more than just Lisp when I started developing early signs for RSI. Switching to a purely KB driven interface has saved my wrists.

I use kmonad to make Space act as Control when held, and it's absolutely life-changing - not just in Emacs, but in all applications.

This is my configuration -

https://codeberg.org/contrapunctus/dotfiles/src/branch/produ...

And here's my blog post about it -

https://contrapunctus.codeberg.page/blog/keyboard-machinatio...

I will absolutely try this one out, it looks a lot more useful than binding caps lock.

wait foot pedals ?

Or an accordion! https://x.com/ykarikos/status/1038145486618861573

It pops up a surprising number of times.

Keysets or chorded keyboards have been around since The Mother of all Demos, but never really seemed to have caught on. It makes sense to me to put them at your feet to chord some common actions or modifiers.

Which joint issues? Have you tried evil mode?

> Which joint issues?

Pretty sure it's rheumatoid arthritis.

> Have you tried evil mode?

This was like fifteen years ago and I just went back to my working Vim setup I was already using for all my other classes.

Sorry to hear that. I have a family history of that as well. I think I'm starting to show signs of it.

Vim forever I guess. Im typing on a full split with cherry reds (very soft). What are you on?

Started using an Ergodox EZ with a custom map after I shattered one of my wrists in a vehicle crash, have stuck with it since.

> better nulability checks

In development: https://github.com/uber-go/nilaway

I'm still trying to convince the scientists I work with that they should format their code or use linters. Making them mandatory in Go was a good decision.

> I'm still trying to convince the scientists I work with that they should format their code or use linters.

Consider adding a pre-commit hook if you are allowed to.

My group's repos enforce strict rules, theirs does not.

Yeah, I've been there. I would get passed down horribly formatted code from another repo and it showed the data scientists writing it barely knew what they were doing. It was their repo, we couldn't do anything about it. They wouldn't reformat the code, because they were afraid it would break. They also passed us a lot of Python, and you can see where they got this fear from.

TLS is basically SSL 4. They only changed the name to signal the backwards incompatibility.

Not quite.

The name was changed from SSL to TLS as part of the adoption in IETF. I imagine different people had different motivations, but in part it was a signal that it was going to be controlled by IETF rather than Netscape.

As far as compatibility goes, TLS is backward compatible with SSLv3 [0] in that the client can send a ClientHello that is acceptable to both SSLv3 and TLS servers and the server can select the version to use.

Re: the version number, we're now on TLS 1.3, so I guess that would be SSLv7.

[0] The situation is more complicated with SSLv2, which had a different ClientHello format.