When I went to high school, things started disappearing.
I wrote essays in Word, saved them on floppy disks to print at school. Text would get deleted or garbled. Sometimes a file wouldn’t load at all, so I would re-type it from memory.
Textbooks, worth hundreds of dollars, would vanish from my locker. I’d take someone else’s book from the lost and found, scratch my name in the cover.
The dotcom bubble burst.
Version 0.6 of aretext has been released! Aretext is a minimalist, terminal-based text editor with vim-compatible key bindings. Here’s what’s new!
Markdown syntax highlighting Aretext now supports syntax highlighting of markdown! It looks like this:
The current implementation supports most of the CommonMark 0.30 spec, including:
Headings Links Emphasis and strong emphasis (bold and italic) Bulleted and numbered lists Code blocks The new markdown parser has been validated against the CommonMark 0.
This morning, I joined the eCHO livestream to chat about a feature I worked on for the Cilium 1.12 release! Discussed delegated IPAM and my experience as a first-time contributor to the Cilium project.
KubeCon this year featured a panel discussion of IPv6 adoption. One of the panelists mentioned in passing that many organizations are unprepared for the security implications IPv6. With IPv4, most addresses were hidden by NAT; with IPv6, addresses are publicly routable. Firewalls can block external traffic, but might not be configured correctly.
So I did an experiment on my home network. Would enabling IPv6 expose my devices on the public internet?
A few weeks ago, I implemented syntax highlighting for markdown in aretext, the minimalist vim clone I’ve been building. Like most context-sensitive languages, markdown is difficult to parse. Although it handles only a subset of the CommonMark 0.30 spec,1 my implementation required 845 lines of Go code.
Parsing is especially tricky because the code needs to handle any document a user might open. It can’t crash or enter an infinite loop.
This is a story that begins with some code I wrote and ends with a rejection.
First, the code. In high school, I wrote a little Mac OS X application that would encode text as binary. It had a window and textboxes and buttons and everything. You could type in “hello”, and it would output something like “0110100001100101011011000110110001101111”. You could also convert back from binary to the original text.
In hindsight, the implementation was pretty terrible.
Vim was my preferred text editor for nearly eighteen years, until I switched to aretext in 2021. I appreciated vim’s efficiency and ubiquity, the way I could rely on it regardless of what project I was working on or what machine I had ssh’d into. Like any software, however, vim reflects the time in which it was written. In many cases, vim optimizes for speed above all else, an approach that made sense given the limitations of late ’90s computers.
Today marks the fifth release of aretext, the minimalist text editor with vim-compatible key bindings! This post describes the highlights.
(Wait, what’s that? You say you want to install it right now? Well, then just go straight to the installation docs!)
Faster fuzzy menu search Aretext uses a trie-based fuzzy find algorithm for selecting files in a menu. This worked well for most projects… until I ran it after building Kubernetes.
This is the second post of a two-part series on Starcraft and late-90s networking. Part 1 describes Starcraft’s many connection options.
Configuring Starcraft networking in 1998 was an adventure. There were four different connection options (plus AppleTalk on Macintosh computers), each of which required specific software and hardware to function. How did anyone figure this stuff out?
It turns out that the Starcraft CD included detailed support documentation. Today, this provides a glimpse of computing history circa 1998.