zadwang

The simpler and I think correct conclusion is that the LLM simply does not reason in our sense of the word. It mimics the reasoning pattern and try to get it right but could not.

Such ideas generally interfere with usability. I loath any such automations. Some more examples: the menu changes when the mouse hovers over the item; the window size or position changes when the window movement nears the border; Word automatically indent bullet items etc etc. The people designing such systems think they are designing a smart system and the usability is horrible, for me at least.

Fourier basis is unique in that the complex exponential basis functions are the eigen vectors of the linear time invariant (LTI) systems. No other transform has this property. Many real world systems (circuits, communication channels, antennas, etc) are LTI. This property make sure for example, signals transmitted over different frequencies do not interfere. That is why Fourier transform is so useful and used instead of other transforms. There is also the connection with quantum physics, in using Fourier pair as wave functions of position and momentum, which other transforms don’t have.

The set of unix utilities have been tested a long time. I just wish the kernel and key utilities keeps fixed and not changed. Unless absolutely necessary. Don’t fix it if it ain’t broken. The software empire seems out of control.

I use DDC and synergy. So no hardware. It is mostly working OK.

Excellent illustration. After reading it I thought this looks like the PHD style. And I checked the author, who IS Jorge Cham. About 22 years ago I was reading his Piled higher and deeper, PHD, series and bought several books of his. It is a great feeling to see that he is still doing comics. Thanks Jorge!

Is this the reason modern apps like Mozilla are so slow? Basically OS memory movement is the bottle neck?

Vi was designed for very slow connections, maybe 300 symbols per second. As such it needed to minimize the keys needed to accomplish a task and maximize user friendliness within such constraints. Turns out that goal is still very much relevant today - although there is a learning process to learn the code book.

Last time I checked I disliked the size of search index folders and files. So I am sticking to mairix, which integrates well with mutt and is small and fast.

You are right.

Would it be possible to add closure use as another case?

Correct.

The “static analysis” section says that it is impossible to catch all cases where address is used which is true. However if the analysis checks for whether address is TAKEN, then it is trivial. I would like to propose that as an alternative- whenever address is taken the variable is per iteration. Otherwise per loop.

This seems the simplest and logical modification.

If I understand correctly the fix requires the new code to add a line in go.mod to use the new behavior. This is about the same as adding x:=x in the loop, and more hidden. Not good.

The alternative can be that whenever address of iteration variable is used inside the loop the variable is per iteration and otherwise it is per loop. This way it is not breaking the old code and have new semantics.

Are there open data for this type of research? If someone would like to improve their algorithms.

I have not met him but have used his LetsEncrypt service. I felt thankful for existence of such service. RIP.

I think the reason Vi wins even at infinite terminal speed is that it minimizes the things you need to type to express what you want to achieve/edit to computer. This was motivated by slow terminal speed in the beginning but is also addressing the bottle neck of human computer interface.