Today I announce a new project: Swig. Swig is a monolithic, multithreaded, micro web framework designed for an air-gapped intranet environment. Aside from Python 3, it has zero dependencies; just download and deploy. Out of the box, Swig supports IPv4 and IPv6, HTTP and HTTPS, block and chunked responses, and gzip compression. I encourage you to go through the README for more information, and to check out the code on GitHub repo.
Here on this website, I predominantly write about technology: Apple, iOS, the web, code, and the like in a mixture of original articles and link posts. I also put together a weekly collection of excellent podcasts that I, quite creatively, dubbed “This Week in Podcasts”. Roughly once a month I write about cabins too, and every so often talk about outdoor gear. The vast majority of the pieces I publish here, however, are at least tangentially related to technology. So if today you have come here looking for one of these articles, perhaps one where I hypothesize as to the future of podcasts or Apple’s next operating system, you might as well leave now: today I will touch on none of those topics, for I have sat down to, for the first time in quite a while, talk about myself. Myself, and my future.
Had I picked one paragraph or sentence as a pull quote from Ben Thompson’s Chromebooks and the Cost of Complexity, I would have done the rest of his article a great disservice by holding one fascinating line above another equally excellent passage. Having read Stratechery for a few months now, I can honestly say that out of all his articles, I consider this one by far and away his best.
Also of interest, Ben posted a followup piece earlier today titled The Best Analogy for Chromebooks are iPads, where he explained the use case of a Chromebook and its similarity to that of an iPad. When I can justify another large technology expenditure, I will have to do some serious work to talk myself out of a Chromebook after these two articles.