HN user

zadwang

102 karma
Posts0
Comments43
View on HN
No posts found.

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.

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!

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.

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.

The discussion is mostly about features of teleconference software which is completely off topic. The point of the article is security. I am not sure if Zoom INTENTIONALLY left the bug for future exploits. I have suspicion and no proof. But in any case, not fixing a bug after 8 months is simply unacceptable.

I learned how to ride a bike when a young kid sticking one leg inside the triangle frame of the large adult bike. Kind of dangerous now looking back but I still remember the liberating feeling of more mobility.

Modern software are just ridiculously hungry for memory that even many GB is not enough. This is just bad considering that we used to work with only GB of disk. I wish all software designs are frugal in resources.

mbsync tends to be more efficient and robust. With Gmail it has no problems. With outlook IMAP it has problems with some emails occasionally. I haven’t figured out how to sync Maildir with Office365 other than cloud-mdir-sync which is inefficient for large mail boxes.

Understanding Awk 5 years ago

I have used it for many thing such as extract bibtex entries and checking for missed definition of abbreviations, converting remind entry to ICS format etc. Recent example is to print a calendar like cal but with calendar dates highlighted.

The research approach is distasteful and dangerous. Any one should not introduce bugs or malicious code intentionally, even for research purpose. The results are also a bit trivial. It is easy to imagine that this type of code injection would be possible. So let this be an example of what is the consequence of intentional malicious code injection, even in the name of research.

I wish I could be on the researchers' side, as I am both Chinese and an alum from UMN. But No - wrong is wrong.