Read on the website: Binary Lambda Calculus is a really alluring idea. But it’s also hard to grasp and use! Here’s my list of complaints and obstacles to using BLC.
Read on the website: Kaktovik numerals are a surprisingly good counting system. It allows many arithmetic operations to be done visually and effortlessly. Though it takes some getting used to. Thus this page!
Read on the its own page: We all love READMEs. We also love websites. Why not have both in one file?
Read on the website: Package-inferred systems follow a useful one-file-per-package convention structure. But package-inferred systems themselves are harmful and should not be used. rss.xml:z15n
Read on the website: Markdown seems to have taken root. But it’s not really a good choice of markup language, because it’s incomplete, non-semantic, and tool-specific.
Read on the website: HTML is flexible and was shaped by generations of web practitioners. It has enough tricks up its sleeve to actually be nice to author. Here are some.
Read on the website: There are narrow screen CSS problems I often email people because of. These three fixes should be enough for most.
Read on the website: This was a hard year, filled with Lisp hacking, ed(1) editing and meta-programming, escapist writing, and heavy feeling. A good K-pop soundtrack tho.
Read on the website: Submodules give you the flexibility to fetch the dependencies, or not. And they enable more granular reproducible builds. Use submodules!
Read on the website: The concept of text editing word is inflexible and outdated. We need better.
Read on the website:
Read on the website: There’s data encoding in Lambda Calculus. But there are also algorithms. Recursive, usually. So let’s look at how recursion works when all you have is lambdas.
Read on the website: ed(1) is a versatile programming system. Yet no one talks about metaprogramming and algorithms in it. Now someone did, and that’s me!
Read on the website: Not all environments have Lisp-aware structural editing. Some are only line-oriented. How does one go about editing Lisp line-by-line?
Read on the website: ed is a stupid simple text editor. sed is a nice streaming text processing tool. Why would one even want to use ed for anything, let alone for text processing if there's sed?
Read on the website: Threading macros make Lisp-family languages much more readable. Other languages too, potentially! Except… other languages don’t have macros. How do we go about enabling threading “macros” there?
Read on the website: Text is a universal medium. And yet we try to prevent users of our UIs from using it. Let’s not.
Read on the website: I am an ed(1) fan. Naturally, I have a lot of scripts and implementations handy. Here are some.
Read on the website: Lisp REPLs are a good tool, but some consider it too rigid. Which leads to abundance of proxy REPLs. Except… you don’t need them!
Read on the website: Just stop artificially restricting yourself to bad software.
Programming
Data Visualization
Web
Web Development
HTML
Security
DevOps
CSS
Frontend
Tutorial
Writing
Culture
Design
Open Source
Backend