A Libertarian Walks Into a Bear: The Utopian Plot to Liberate an American Town (And Some Bears)

Matthew Hongoltz-Hetling (2020)

A group of libertarians decide that they need to form a free utopia, and move en masse to a town in the forests of New Hampshire that just happens to be in the middle of a massive boom in the local bear population. Hilarity ensues.

Well, not hilarity exactly, although this book is laugh-out-loud funny in places. But there are serious points being made too. The libertarians take apart the town’s community activities and services, to some extent by freeloading off the services in neighbouring towns that have only fractionally higher taxes but have larger populations because they’re … ermm … better places to live. The collective resources are depleted to the point that the bear become more than a metaphor, a problem for which the town can’t summon a collective response. And the final humiliation is that, when a national libertarian movement in the same vein starts, and also picks New Hampshire as their target for their new society, they don’t find the original enclave welcoming enough and start their own communities elsewhere.

It’s hard to know exactly what the moral of the story is, if there is one. Certainly it makes a point about the benefits of community very well. But it’s also somewhat trapped within a rather American rubric of democracy simply meaning having more votes than the other groups, where the majority can impose their will without too many safeguards,

5/5. Finished Thursday 25 March, 2021.

(Originally published on Goodreads.)

Veritas: A Harvard Professor, a Con Man and the Gospel of Jesus’s Wife

Ariel Sabar (2020)

What happens when an academic is offered the physical support for their theories? This is the story of the “Gospel of Jesus’ wife”, a Coptic fragment purporting to contain and almost-contemporaneous quote of Jesus referring to Mary Magdalene in this way. If that sounds like The Da Vinci Code, well, yes it does – and one of the many ironies is that the academic receiving the fragment was a consultant on the film….

The details of this simple-sounding con – and it does sound like a con, even from such a short description – involve a deep-dive into the provenance of ancient documents, the international market in papyri, the intricacies of Coptic linguistics, and other high-culture sub-cultures. Very few people come out well.

But there’s no physical evidence to link the papyrus’ creation to the specific individual, and while the circumstantial case is compelling, there’s still something slight unsatisfactory about the investigation. Why did the forger – if indeed he was the forger – do it? He seems to have had no motive. Even though he had the background, did he have the practical skills? And indeed, might he have been more skilled than he turned out to be?

4/5. Finished Saturday 20 March, 2021.

(Originally published on Goodreads.)

November 1918: The German Revolution

Robert Gerwarth (2020)

The Weimar Republic is a period often forgotten and often treated merely as a failed precursor that led to dictatorship. This book deals with its formative period. It’s extremely focused, dealing with only the period between the Kaiser’s abdication and the signing of the Treaty of Versailles, and the focus gives it momentum. The interpretation is balanced and not overly distorted by what the author (and reader) knows comes next.

4/5. Finished Monday 1 March, 2021.

(Originally published on Goodreads.)

IDE convergence

I recently tried out a new development environment for my Python development, and noticed an unexpected convergence in the designs of the two tools.

I’ve been a long-time Emacs user. I periodically get a desire to try something new, something less old-school, just to see whether there are advantages. There always are advantages, of course — but often significant disadvantages as well, which often keep me coming back to my comfort zone.

My most recent excursion was to try Microsoft’s VS Code.

Microsoft VS Code

This is handily cross-platform, being built in Javascript on top of Electron. It’s got a lot of nice features: a tree view of the project in the left-hand pane, syntax colouring, code style linting, integrated debugging and unit test running, integrated connection to git, and so on. Looking a little closer there are all sorts of status markers around the code and in the ribbons at the bottom of panes and the window overall to show status that might be important.

But it’s so slow. That’s a feature of VS Code, not of Electron (as I first suspected), because other Electron-based editors like Atom aren’t as slow. And my development box isn’t the latest, but it also isn’t that old.

So I reverted to Emacs, but upgraded it a little to more modern standards. Specifically, I installed the elpy Python IDE, with assorted other packages suggested by various sites. The result is this:

Emacs with elpy

Now for anyone who’s used Emacs for a while, it’s definitely still Emacs — not least with the convoluted keystrokes and infinite customisation you either love or hate. But it’s striking how similar the two IDEs now are, and striking how VS Code has inherited some ideas from Emacs: resizeable panes, modelines in the ribbon, markers in pane gutters, and so forth — things that Emacs-based applications have had for years, which have now migrated into “the mainstream”. Both the feature sets and the visuals of the two systems are very similar indeed. Both are entirely cross-platform and extensible. For VS Code you write extensions in Javascript; for Emacs you write them in Lisp; and that’s about it. And Emacs is a lot faster on my set-up. There are some limitations — I’ve yet to get the hang of using pdb as a debugger, for example, especially for modules and from within tests — but the functionality is really quite comparable.

I think it’s safe to say there’s been cross-fertilisation between VS Code (and other IDEs) and Emacs over the years. A lot of the developers of the former quite possibly used the latter. But I strongly suspect that most of the traffic has gone from Emacs to the other systems: the similarities are just too great to be accidental. It’s interesting to think that a system that emerged at the dawn of the free-software movement has had — and is still having — such an influence on modern development tools. And I’m happily back in my comfort zone.

American Kingpin: The Epic Hunt for the Criminal Mastermind Behind the Silk Road

Nick Bilton (2017)

The Silk Road occupies an interesting place in the history of the internet. To many it is the “dark web”, the place where people can buy contraband with cryptocurrency. (Indeed, this is basically the only real-world use case for cryptocurrencies so far.)

It’s a strange tale of someone who didn’t seek to create the world’s dark marketplace, but once he had was sucked-in to a vortex of ever-expanding crusade to support “freedom”, of that particularly libertarian kind in which no harms are admitted and no constraints regarded as valid. Ross Ulbricht also seems curiously divorced from the success of his creation, in the sense that he never spent any of the millions he made, and never seems to have much intention of doing. It’s a fascinating to ask what would have happened to him if he’d walked away (as he told his girlfriend he had) in the relatively early years.

There are some questions left largely unanswered, though. Does having a safe, legal, marketplace for drugs reduce harms, by removing the criminals and violence? It’s hard to say, as the Silk Road never really removed the criminals from the equation. Is a recommender system sufficient to regulate a marketplace for contraband? Is the middleman as guilty as the seller – or the buyer? Taking down the Silk Road didn’t end the dark web, and indeed it’s now a fragmented and dynamic place that’s more difficult for both law enforcement and consumers to navigate. Another thing Ulbricht never seems to have foreseen.

4/5. Finished Thursday 18 February, 2021.

(Originally published on Goodreads.)