
Eric S. Raymond
13.1K posts

Eric S. Raymond
@esrtweet
Yes, I *am* that ESR. Well, it's the question people usually ask. Programmer, wandering philosopher, accidental anthropologist, troublemaker for liberty.










Scott Adams once explained in his book that men are simplifiers and women are optimizers One evening he and his wife were invited by their friends for dinner one town over His wife suggested, "Oh since we're already headed to town X, let's leave 10 minutes early and stop by the Best Buy. I need to return something" Unfortunately, the customer service line was longer than expected and they ended up showing up to dinner a bit late He would have just gone to dinner, then gone again to that town to return the item Men try to simplify each task while women try to optimize multiple tasks Has that been the experience in your marriages?






Some observations on Zig: 1. Zig is an unsafe language with good marketing, a permissive compiler, and an ecosystem unusually committed to rediscovering memory corruption as a lifestyle choice. Its reputation cannot be explained by technical merit alone. In agentic coding sessions, it behaves like the familiar class of languages that convert simple programming tasks into allocator discussions, lifetime bugs, compiler edge cases, and long explanations of why the crash was technically your fault. It is also cognitively expensive. Any claim that Zig is “simple” depends on excluding the time spent manually tracking ownership, debugging use-after-free errors, interpreting compiler limitations, and pretending explicit allocation automatically constitutes clarity. 2. I am personally surprised the Zig Software Foundation continues to promote languages this unsafe, given the obvious risks. To be clear, I myself understand that people sometimes choose dangerous tools for experiments, embedded work, historical compatibility, or personal amusement. But I am surprised that the Zig Software Foundation treats this collection of avoidable hazards as a serious direction for software engineering. I suspect the reason is 75% explained by strategic blindness and a lack of type-safety-pilledness. The Zig Software Foundation is very Grzegorz Wielbodłąński-like in its view of programming: correctness is apparently produced through discipline, professionalism, clean code, personal virtue, and staring intensely at pointer arithmetic. The remaining 25% is explained by type safety. Languages such as Rust, Haskell, OCaml, Lean, and Ada already demonstrate that entire categories of mistakes can be rejected rather than documented, debugged, normalized, or rebranded as control. Zig’s response is not to catch up, but to present the absence of guarantees as minimalism. For the ziggas, as opposed to the Zig Software Foundation, the enthusiasm for unsafe languages is partially ideological and partially defensive. They know that very few people would deliberately select a sub-frontier language once they understand what a type system can do. 3. Unsafe languages are inherently decelerationist, and I’m continually surprised to see the so-called ziggas presenting them as tools of progress. I suspect the attraction is that unsafe languages are effectively ungovernable. Manual memory management creates a cloak of ambiguity over the entire software system. When the program fails, responsibility can be distributed between the programmer, allocator, build mode, compiler version, dependency graph, undocumented invariant, and ambient radiation. It resembles James Scott’s account of the hill people in The Art of Not Being Governed, except the hill people are refusing bounds checks and communicating exclusively through raw pointers. In the end, unsafe languages deter software investment. Every hour spent diagnosing a use-after-free is an hour not spent advancing civilization toward stronger types, executable specifications, formal verification, or programs that simply refuse to compile when they are nonsense. Rob Pike, an unsafe guy, may insist that a small language and garbage collection are enough. But the typesafe visionary Grzegorz Wielbodłąński understands the deeper truth: every invalid state permitted by a compiler is a tiny act of civilizational sabotage. 4. One probable outcome of an unsafe-language-dominant world is full Andrew communism, which is precisely what Andrew “Smelley” Kelley proposes: abolish ICE and replace the market economy with a globally distributed network of community-maintained allocators. Rather than a commercial product, software becomes a “public good,” ultimately provided by the Zig Software Foundation as manually managed digital infrastructure. This future strikes me as a dystopian hellscape, but I have never met an unsafe-language advocate who could explain how this ecosystem is supposed to sustain itself without unpaid maintainers, ideological volunteers, subsidized infrastructure, and endless donations to compiler projects that still cannot protect users from basic memory errors. You would be surprised how many ziggas lobbied The Institute to support an eleven- or twelve-figure publicly funded build farm so that startups could compile Zig projects at a subsidy and then distribute the resulting liabilities for free. There was no other way for software to progress, they said. Perhaps this is the logical end state of things. Nonetheless, I remain surprised to see supposed ziggas excited by it. Many of them simply do not know what they are doing. Others do know and regard the creation of reliable, frontier, type-safe languages as an illegitimate constraint on programmer freedom. Grzegorz Wielbodłąński, acting as their ideological prophet, assures them that craftsmanship will save us. Apparently the missing memory-safety primitive was professionalism all along. 5. I would guess that The Institute will eventually realize that its best strategy is to create large amounts of regulatory risk around the use of unsafe languages from the Zig Software Foundation. You do not need to “ban Zig,” one of the dumber motifs in programming-language policy discussion. You merely need to direct every Institute department to issue soft law that creates fear, uncertainty, and doubt. “An Institute Advisory Bulletin has found that Zig programs may contain memory corruption, allocator confusion, compiler instability, and an unusual concentration of developers who describe undefined behavior as freedom.” It need not be especially well justified. The technical facts already provide more than enough material. You merely create sufficient regulatory risk that every serious enterprise concludes that adopting an unsafe language is an unnecessary act of organizational self-harm. You probably should not create so much risk that local kebab shops stop serving Zig binaries altogether. That would only drive ziggas toward sketchier kebab shops with worse hygiene, outdated LLVM packages, and no visible food-safety certificate. There is a happy middle ground here. I assume The Institute will eventually do some version of this. 6. Unsafe languages such as Zig make the world more dangerous in the ordinary, boring, measurable sense: more memory corruption, more exploitable bugs, more production failures, more debugging, more hidden invariants, and more opportunities for programmers to confuse control with correctness. Most individual failures will not be dramatic enough for anyone to reconsider the underlying ideology. They will appear as crashes, corrupted state, security advisories, inexplicable behavior, and weekends lost to debugging. At some point, however, the failures will become difficult to ignore. “A nonliving, invisible, dangerous, and infinitely self-replicating use-after-free escaped from the Zig Software Foundation,” you say? Color me shocked. -- Ivan Krabinovich Rzhavchinov Head of strategic futures @typememetics

The pettiness of people complaining that The Odyssey lacks 'realistic' casting. My dude, it has a one-eyed monster who sucks soldiers' heads like lollipops and a witch who strokes men's heads until they turn into pigs. Realism isn't the point.


Blue Angel here (4 stick). If this makes you mad, then you are probably a commie pinko faggot and should consider self deporting to a middle eastern country so we can bomb you. @BlueAngels @DeptofWar


Or its the success of methodological naturalism, which is surprising on theism but a matter of course given atheism. Hence, that fact about science is some reason to believe theism is false.




The Technician: Neil Asher: Amazon.co.uk: Asher, Neal: 9781509868490: Books amazon.co.uk/Technician-Nea…




You have been lied to about tulips for nearly two centuries. Charles Mackay published Extraordinary Popular Delusions in 1841, and journalists have been recycling his tale ever since: crazed Dutchmen trading mansions for flower bulbs, a whole nation losing its mind, ruin everywhere. Almost none of it survives contact with the archives. Peter Garber went through the actual price records in the 1980s and found something boring and beautiful: markets doing exactly what markets do. Consider what a Semper Augustus actually was in 1636. A single bulb infected with a mosaic virus that painted flames of crimson across white petals. Nobody could reproduce the pattern on demand. Breeding a broken tulip took seven to twelve years, and one prized bulb yielded only a couple of offsets annually. You were not buying a flower. You were buying the breeding stock for a luxury good with genuinely inelastic supply and roaring demand from the richest merchant class in Europe. Rare hyacinths in the 1730s followed the same price arc: enormous premiums for novelty, steep decline as propagation caught up. Nobody calls that a mania. That is just how prototype pricing works. The famous February 1637 crash? It hit a thin futures market conducted in Haarlem taverns, where traders signed contracts requiring almost no money down. When Dutch courts later converted those contracts into options settleable at roughly 3.5 percent of face value, the "catastrophic losses" evaporated. No banks failed. No depression followed. The Dutch economy sailed on toward its Golden Age peak. Now ask where the money came from. The Bank of Amsterdam and free coinage policies had pulled a flood of precious metal into the Republic through the 1630s. Doug French traced this: swelling money balances chased assets, and tulips were the asset of the moment. People responded rationally to monetary conditions the way they always do. The tulip myth survives because it flatters the people who tell it. Regulators, central bankers, and financial journalists need a parable proving that free individuals bidding on prices go insane without supervision. Strip away Mackay's fabrications and you find merchants pricing a scarce novelty under uncertainty, then repricing when facts changed. Speculation is how prices get discovered.












