funcDropShadow

The web page "Why, oh WHY, do those #?@! nutheads use vi?" [1] convinced me almost 20 years ago to give it a try. Already then, it looked like an outdated mode of editing text, but I was wrong.

[1]: https://web.archive.org/web/20180318023156/https://www.viemu...

This is a indeed an important reminder that there is still progress to be made in the realm of software development. By raising the bar of abstractions, perhaps by guiding agents toward them, we might be able to follow along better. It is too tempting to take allow the growing capabilities of ai to lower the standards on software developmenbt.

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?

You could manage those VMs with https://microvm-nix.github.io/microvm.nix/ that helps with mounting the nix store read only from the host into the vm. That should save more space than trying to reduce the dependencies of the system closure of the vm.

STM is seldom used in modern Clojure projects, it is certainly not the dominant model. Most projects I am aware of use a few or even exactly one atoms with immutable data structures.

No other mammal eats cooked or baked food. Raw meat or raw plant contain more water than our food.

When you are administrating so many Java applications, you should investigate an hour or ask your favorite AI how to configure the logging library used in your application of interest. They allow you to remove stack traces and lots more.

They wouldn't have to, if the file format accepted floats in proper exponential format.

If companies are allowed to change the meaning of terms in legislation we are in even more trouble.

> Garbage collection, by definition, trashes locality.

No, it doesn't necessarily. It is correct if you are thinking about mark and sweep GC. But that is 50 years old. Generational GC has much better locality. And GC can even improve locality sometimes by moving objects together that are connected by references. I am not claiming that GC is always a big win for locality. That would be very far from the truth. On the other hand it is not by definition so, that locality is trashed by GC.

OMG no. Politician have no business making technological decisions. They make it harder to innovate, i.e. to invent the next generation of ECC with a different name.

The same panel produces much more electricity in space than at the bottom of the atmosphere, because the atmosphere already reflects most of the light. Additionally, the panel needs less glass or no glass in space, which makes it lighter and cheaper.

Launch costs have shrunk significantly thanks to SpaceX, and they are projected to shrink further with the Super Heavy Booster and Starship.

Self-cataloging can be become a method of procrastination. But that doesn't mean that there is no value to be found in methods like Zettelkasten. The activity of looking through your own Zettelkasten has the potential of creating associations and sparking ideas. That can be very valuable and requires some care of your notes. But trying to find the perfect taxonomy for your own notes is foolish mistake. The technical limitations of the original Zettelkasten, makes refactoring the notes to the current approximation of the perfect taxonomy such a huge task, that it is usually avoided.

A nice example of a limitation that supports creativity.

So, in order to avoid the negative consequences of a European monopoly, we make sure that a Chinese monopoly prevails? That doesn't seem like a wining strategy for Europe.

Even if we assume that JSON numbers are JavaScript numbers. There is the problem that some large natural numbers cannot be represented in double or float although some even larger numbers can be represented. This is very bad if you use these numbers as IDs.

    scala> (Long.MaxValue-1)
    val res4: Long = 9223372036854775806
                                                                                
    scala> (Long.MaxValue-1).toDouble.toLong
    val res5: Long = 9223372036854775807

The fact that I used Scala is irrelevant here. That is true for many programming languages that 64 bit long and double types.

Because, Truffle is reused in multiple language VMs their overall attack surface is smaller than it would be with classical language VM architectures.

But with a visible scrollbar you would have a visible indication which behavior you triggered. If the scrollbar is invisible you get a changed viewport in both cases but you have to infer which gesture triggers which behavior.