Using Emacs in an IDE world. IDEs all look too complex to me. I am happy with fine-grained text editors like Emacs or (Neo)vim. Every time I try to use a light (VS Code) or not so light (IntelliJ stuff) IDE, I blow up after 10'.

Euler’s Formula. Looks like a nice Lisp-based website, right?

For making a viable Google competitor, I believe that ranking is a harder problem than indexing, but even if we just look at indexing, there are individual domains that contain on the order of one trillion pages we might want to index (like Twitter) and I’d guess that we can find on the order a trillion domains. If you try to configure any off-the-shelf search index to hold an index of some number of trillions of items to handle a load of, say, 1/100th Google’s load, with a latency budget of, say, 100ms (most of the latency should be for ranking, not indexing), I think you’ll find that this isn’t trivial. — I could do that in a weekend!

Is Hacker News a Good Predictor of Future Tech Trends?.

However, we shouldn’t forget that we are still living in the stone age of computational science. Fortran was the Paleolithic, Python is the Neolithic, but we have to move on. — Exploring Racket

Benefits of not using an IDE. Main point as far as I’m concerned is that even light IDEs (e.g., VS Code) are too complex for what I really need to do. Git and debugger integration are a plus, though, but I already get that using Emacs or Vim.

Using Vim - Beyond the Basics. #vim

An Opinionated Guide to xargs. #unix

The “true” program does nothing; it merely exits with a zero exit status. This can be done with an empty file that’s marked executable, and that’s what it was in the earliest unix system libraries. Such an empty file will be interpreted as a shell script that does nothing, and since it does this successfully, the shell exits with a zero exit status. — The /bin/true Command and Copyright

Let’s write a compiler, part 1.