funcDropShadow

They have to under GDPR.

Yes, Elon's time tables are very aggressive. But that is by design. And FSD is here, although it took much longer than anticipated, no competitor caught up.

Similar, to the time Tesla was fucked, because they wanted to sell EVs when there was neither demand nor charging infra. Or when SpaceX wanted to build a rocket that could land on legs, whereas every wannabe rocket scientists knew that to be impossible.

herdr has good, not perfect, support to restart a session after a server reboot. It can automatically restart an agent cli while resuming the session they were running before the reboot.

The point I tried to make wasn't that we still need to be able to do everything by hand. My point is more that we need to develop our brains. And for that we need training excercises. Similar to excercises in the gym. I doubt anybody encountered a barbell in real life outside the gym. Yet it is good tool to develop muscles. Math is an excellent tool to develop certain aspects of the brain.

Skipping to learn long division by hand because you'll always have a calculator (or better a smartphone at hand) is like going to a gym with a forklift. It is faster to lift the weights, but it kinda defeats the purpose.

Learning to do long division by hand trains the mind. It prepares you to understand polynomial division. It teaches you the deep connection of division and subtraction. So, mastering it should be part of the curriculum. As soon as it is truly mastered, it should be allowed to use a calculator.

I am wondering why people are so hyped about Ghostty? I gave it recently a try coming from kitty. And I had to configure stuff that worked out of the box with kitty, like Ctrl-Enter support and other key combos for agent harnesses. I like the development model of ghostt. And the developer really cares about creating great building blocks, e.g libghostty. But I am a bit underwhelmed.

Unless it is the led showing the status of a camera.

Does anybody know why it wasn't implemented in a backwards compatible manner?

One could wrap a whole merkle-tree with an additional extension tree, that just adds the new hashes. That way both kinds hashes could be used to traverse all data. The new hashes could be used to check the consistency, the old hashes would still be there to use in UIs or old release documentation. The downside being that you introduce more nodes in the overall data-structure which will have to be supported basically forever. And if SHA-256 is to week a third layer would need to be introduced. But the point is, it could be done. Albeit it would loose some of the elegance of the data structures involved.

No, that argument misses the point. Cryptographic hashes enable you to trust, that I only have to review the changes since the last trusted commit. That is more important for the developers and maintainers of the software and less for the users.

Interesting, but I've read for a long time, that our humanoid predecessors at some point figured out how to get to bone marrow with tools. That provided the energy dense food as well an evolutionary impetus to develop larger brains to build better tools and handle them better. Fire and the capability to cook were developed much later.

How do we know that? Any sources?

But the Inca lived to late for this discussion. They already had advanced agriculture. For evolutionary terms, the time before agriculture and the time of the predecessors of homo sapiens are more relevant, because that time span was larger by orders of magnitude.

source?