andrewducker: (Vaudeville for the next five miles)
[personal profile] andrewducker
Following yesterday's illness, I was vaguely hoping that he would stay asleep through the night. Alas:

12:05
"I need a wee"
Took him to the toilet.
"Daddy, my tummy hurts"
Gave him some medicine
"Do you want to be in pyjamas or just straight back to bed?"
"Back to bed"
And then he closed his eyes.

12:20
Thundering footsteps "Daddy, I feel sick"
Told him to go to the toilet. Kept him company, got him a bucket.
He wasn't sick.
Persuaded him to take the bucket to bed.
Sat on the floor next to his bed until he closed his eyes.

12:35
More thundering steps
"Daddy, my arm and leg hurt"
By the time I'd found him medicine he was asleep again.
But woke up again and let me give him some Calpol.

03:30
"I'm hungry" (not surprising as he didn't eat yesterday)
We agreed on cream cheese crackers.
He ate ⅘ of the cracker and drank some juice and passed out again.

06:30
"I checked the light coming under the curtain and it's morning time"
I told him to go play games on the Switch downstairs.
Fifteen minutes later I could still hear him wandering about and I hadn't heard any game noises.
Went to check on him and he told him that he'd found various points around the house where the floor isn't flat.
Got him settled with the Switch, and then went back to bed and stared vacantly at my phone for an hour, before getting up to face the day.

LotusNotes

2026-03-14 00:00
[syndicated profile] computer_rip_feed

I tend to focus on the origin of the computer within the military. Particularly in the early days of digital computing, the military was a key customer, and fundamental concepts of modern computing arose in universities and laboratories serving military contracts. Of course, the war would not last forever, and computing had applications in so many other fields—fields that, nonetheless, started out as beneficiaries of military largesse.

Consider education. The Second World War had a profound impact on higher education in the US. The GI bill made college newly affordable to veterans, who in the 1950s made up a large portion of the population. That was only the tip of the iceberg, though: military planners perceived the allied victory as a result of technical and industrial excellence. Many of the most decisive innovations of the war—radar and radionavigation, scientific management and operations research, nuclear weapons—had originated in academic research laboratories at the nation's most prestigious universities. Many of those universities, MIT, Stanford, University of California, created subsidiaries and spinoffs that act as major defense contractors to this day.

Educational institutions bent themselves, to some degree, to the needs of the military. The relationship was not at all one-sided. Besides direct funding for defense-oriented research, in the runup to the Cold War the military started to shower money on education itself. Research contracts from uniformed services and grant programs from the young DoD supported all kinds of educational programs. For the military, there were two general goals: first, it was assumed that R&D in civilian education would lead to findings that directly improved the military's own educational system. Weapons and tactics of war were increasingly technical, even computer controlled, and the military was acutely aware that training a large number of 18-year-old enlistees to operate complex equipment according to tactical doctrine under pressure was, well, to call it a challenge would be an understatement.

Second, the nation's ranks of academics made up something like a military auxiliary. The Civil Air Patrol built up a base of trained pilots, in case there was ever a need to quickly expand the Air Force. By the same logic, university programs in management, sciences, and education itself produced a corps of well-educated people who would form the staff of the next era of secret military laboratories. Well, that's not exactly how it turned out, with the Cold War's radical turn to privatization, but it was an idea, anyway.

That spirit of military-academic collaboration is how a group of researchers, mostly physicists, at the University of Illinois found themselves with military funding to develop a system called "Programmed Logic for Automatic Teaching Operations," or PLATO. With its origins in the late 1950s, and heyday in the 1970s, PLATO is usually considered the first effort in computerized teaching. It's a fascinating sibling to other large-scale computer systems of the time, like those in air traffic control. There are many similarities: PLATO struggled with connecting terminals and computers over a large area, before "the Internet" was even an idea. It had to display graphics, a very primitive computer capability at the time but one that was thought to be vital for classroom demonstrations. The system supported many simultaneous users, and had to process data in real-time to synchronize their various workspaces.

There were also important differences. Unlike SAGE and the 9020, unlike business accounting and tabulation systems, unlike almost every computer application yet devised, PLATO was designed for user-facilitated content.

Reflecting its origins among academic physicists, PLATO heavily emphasized collaboration. Many of the earlier, 1960s-era PLATO developments focused on simplifying the development of learning modules so that teachers could create interactive PLATO courses with less specialized computer training. By the 1970s, as PLATO terminals were increasingly installed in schools and other institutions in Illinois, the emphasis on collaboration turned towards communication. If learning modules were easy for teachers to develop, the students should also be able to use the system to create their own coursework and study materials. Researchers and other academic users had a similar desire for a computer system where they could keep notes, write reports, and stay in touch with their colleagues.

PLATO did not prove an enduring success—despite a decades-long effort toward commercialization, it was expensive and the actual benefits of computer-aided teaching remained unproven1. Few PLATO systems ever escaped the University of Illinois and its network of satellite delivery locations. Follow-on projects fizzled out and, despite PLATO's incredible ascent from a 1960 concept to an elaborate 1970s multi-user interactive system, PLATO spent the 1980s in decline. No one thinks about PLATO very much any more, which is unfortunate, because it is one of those remarkable, isolated moments in history, a sort of conceptual singularity, in which a project with limited real success incubates so many concepts that it sets the course of history afterwards.

When you look at our modern computers, smartphones and social media and Farmville and so on, it's hard to find a single thing that isn't somehow derived from PLATO. Through PLATO's 1970s NSF funding and resulting interaction with other NSF efforts, it is my opinion that PLATO is probably a more important precursor to the modern internet than ARPANET and NSFNET. Not so much in a technical way; PLATO was closely tied to a mainframe-terminal architecture that would not have likely lead to our flexible packet-routing internet architecture. Rather, in a vibes way. PLATO was a large-area, networked computer system that emphasized posting things and looking at things other people had posted. It offered math lessons, but it also offered games.

Perhaps most importantly, it had notes.

PLATO's developers at the Computer-Based Education Research Lab of the University of Illinois had long had a simple way of communicating with each other, by editing a series of lessons titled "notes1" through "notes19." While functional, it was imperfect: Google Wave had not yet appeared to tell us that everyone being able to edit everything is good actually, so the complete lack of access controls, or formatting, or really organization of any kind was making the "notes" lessons a headache as the system gained users. In 1972, the PLATO IV terminal, new funding, and new backend computers had PLATO growing fast. There was an obvious need for a better version of the notes lessons.

Through the machinations of academia, the task of building a better "notes" file fell on two high-school students, on their summer break from the University of Illinois-affiliated laboratory high school. Using PLATO's native TUTOR programming language and facilities intended for exams and course discussions, Dave Woolley and Kim Mast wrote a lesson called "=notes=". The =notes= lesson was originally intended for system announcements, trouble reports, and communications between PLATO's operators. Soon, though, it was doing far more.

PLATO's notes were not the first implementation of a computer-based discussion board. Similar capabilities had been implemented by ARPANET users at least a couple of years earlier. It was also not the first email system, and indeed, was not email at all: notes only offered public posts. PLATO didn't gain a private messaging capability at all until a year later. The notes lesson wasn't even the only message board on PLATO, although it was the most sophisticated.

What stood out about notes is that it was popular. Everyone used it. By 1976, the notes lesson had evolved into a generalized application that allowed any PLATO user to create and manage their own notes file. That management included access controls and capabilities we might now call moderation. It was one of the most popular applications on all of PLATO, and that was against the competition of the several notable early video games created there.

Brian Dear, author of "The Friendly Orange Glow," a book on PLATO, argues that the notes lesson's peculiar history as a public messaging system that came before a private one had a critical impact on PLATO's users and culture. Communications on PLATO were "public-first." While a "private notes" feature was added later, users were already in the habit of doing things in the open. This sense of community, of close collaboration with some and passive awareness of others, must be a cultural precursor to the BBSs of the early internet and the social networks of today.

But that's not even what I'm here to talk about. During the late '70s, there was something else going on at the University of Illinois: future Microsoft CTO Ray Ozzie was working on his undergraduate in CS, a large part of which involved PLATO. After his graduation in 1979, he worked for Data General, manufacturer of a popular series of minicomputers, where he reported to Jonathan Sachs. After Data General, he did a stint at Software Arts, the development firm behind VisiCalc. He must have stayed in touch with Jonathan Sachs, though, who in 1982 had left Data General to found his own company: Lotus Development.

Lotus is widely remembered for Lotus 1-2-3, the hit spreadsheet application that displaced VisiCalc as possibly the most important software package in all of personal computing. Lotus's two founders were Sachs and Mitchell Kapor, both of whom had connections to Data General and Software Arts, in an era in which blockbuster software products often came from companies founded by a few entrepreneurial employees of the incumbent that was on its way out. And, indeed, they stuck to the familiar recruiting strategy: Ray Ozzie, of similar employment background, joined Lotus in the early '80s as a developer on their complete office suite, Lotus Symphony.

Lotus 1-2-3 was one of the most successful software products ever, but the frontier of office computing was quickly expanding to word processing and presentations. Far from our modern monoculture of Google Docs and Microsoft Office still kind of hanging on I guess, the productivity software market was extremely competitive in the 1980s and just about every Independent Software Vendor had some kind of productivity or office suite under development. The vast majority of these were commercial failures, and Lotus Symphony was no different 2. It is fascinating to consider that Symphony included an (apparently mediocre) desktop database/rapid application development tool called FORMS. Desktop databases were once considered table stakes for productivity suites, but are now almost completely forgotten, recast as expensive and standalone SaaS offerings like AirTable. But I digress...

By 1985, Lotus had acquired VisiCorp and consolidated its dominance in PC spreadsheets. Despite its overwhelming success in spreadsheets, Lotus struggled elsewhere: not just Symphony and Jazz but standalone word processor Manuscript and modeling-oriented spreadsheet Improv were often technically impressive but were also consistently poor sellers. I think that part of the problem is that the people at Lotus were a little too smart. This is best exemplified by their unsuccessful "personal information management" or PIM product (this is the same general category as Microsoft Outlook and Mozilla Thunderbird, although historically PIMs were less email-centric and more focused on calendars and contacts).

Lotus Agenda was marketed as a PIM, but unlike other contenders of the era, it came without a fixed schema into which the user inserted data. Instead, it behaved more like a very simple desktop database, with the user entering data into spreadsheet-like tables however they wanted and then defining views based on column and row filters. The result was highly generalized, able to fit just about any use case with sufficient time and effort. It also did very little to help: you started with a blank grid, left to your own devices. It reminds me of modern PIM-adjacent offerings like Emacs org mode or Obsidian that attract a fervent following of dedicated users who ascribe some sort of life-changing experience to them, while the other 99% of us launch the software and then wonder what we are supposed to do. Lotus Agenda, for its part, reportedly had a similar cult fame.

I imagine that Lotus's difficulty entering new markets must have encouraged them to get creative. They had quite a few products, many of them the subject of awards or technical papers or patents, no lack of engineering capability. What they seemed short on was vision and marketing. They had not quite figured out what customers wanted, or at least what customers wanted that was different from what their competitors already offered. I suppose they were willing to take a bet, as long as the risk could be adequately controlled.

In 1984, Ray Ozzie left Lotus to found a new company called Iris Associates. Like Software Arts developer-publisher relationship with VisiCorp, Iris Associates was an independent company but was contractually obligated to offer exclusive publishing rights on its products to Lotus Development. In exchange, the first few years of Iris's operation were funded by a substantial investment from Lotus. Ozzie, now in control of his own kingdom, quickly hired three other University of Illinois alums—people he knew from his time working on PLATO.

It's not clear to me if this was the original goal of Iris Associates or if it became the goal as a result of their experience with PLATO. However it happened, Iris Associates spent about the next five years building a version of PLATO's =notes= lesson that could run on a network of Windows PCs. Through their publishing arrangement with Lotus, this would come to be known as Lotus Notes.

Lotus Notes is one of the most famous, or infamous, examples of "groupware." Groupware is a hard concept to put your finger on, in good part because of its history. The whole thing, as a category, is easily traceable to Douglas Engelbart's work on Human Augmentation at SRI—work that, like PLATO, failed to gain market adoption but was nonetheless tremendously influential on the larger art. Human augmentation is the core idea in groupware, also called computer-supported cooperative work (CSCW). These were lofty academic ideas around the ways that computers could augment the social processes behind most productive work; they were ideas that grew and forked like branches from the middle of the 20th century to today. Many of those branches withered and died, others flourished before some sort of rotting disease set in (looking at you, Sharepoint). The result is that "groupware" meant different things at different times, and today is so non-specific that everything from enterprise business process automation platforms to slightly dressed-up webmail are lumped together.

In the days of Iris Associates, groupware meant something like this: software that assisted humans in communicating, collaborating, and tracking and executing processes. In practical terms, this meant core PIM applications like email and calendaring, but also included collaborative editing, workflow automation, document and policy management, and all kinds of other core business needs that involved more than one person. It's hard to apply a definition of groupware to Lotus Notes because Lotus Notes was one of the major products that originally defined the category, so its capabilities and limitations have become part of the background.

Lotus was under development from roughly 1984 (founding of Iris) to 1989 (first commercial release). The time period also put Lotus Notes in another category, although this one even more tenuous: network operating systems. Novell NetWare, for example, hit the scene in 1983. Network operating systems revolved mostly around file and printer sharing, but most gained some form of email. Lotus Notes had substantial overlap with network operating system features, but ran on Windows, making it an important step in the decline of fully integrated network products like NetWare in favor of application software on Windows which, more and more with each Windows release, used underlying operating system capabilities instead of implementing a complete application-specific network stack. Novell would go in a similar direction, with GroupWise, part of a wild industry restructuring during the 1990s.

It's hard to put a finger on what exactly Lotus Notes was from a modern perspective because the software itself was highly generalized. Wikipedia puts it like this: "Notes and Domino is a cross-platform, distributed document-oriented NoSQL database and messaging framework and rapid application development environment that includes pre-built applications like email, calendar, etc." Let's set aside for the moment the matter of Domino, which we have not introduced, and focus on the parts like "distributed document-oriented NoSQL database" and "messaging framework" which are strange ways to describe a groupware package but actually a very logical way to describe a rapid application development product—mentioned here as just one of the things that Lotus Notes is. I suppose that's a bit of synecdoche.

Like Lotus Agenda before it, Lotus Notes was something of a blank canvas that could be configured, customized, and designed to meet virtually any need. Unlike Lotus Agenda, they had learned a lesson about onboarding and Lotus Notes came out of the box with a set of familiar groupware features. What set Notes apart from other implementations of email, for example, is that Notes email was just another set of views and logic built on a common database. It was a custom application like the others, just one already provided as a sample.

Much of the strangeness of Lotus Notes reflects its origins in PLATO. Most of the microcomputer network products of the 1980s were built around peer-to-peer networking, the idea that multiple small computers could communicate with each other directly (NetWare, for example, used a peer-to-peer architecture despite the fact that certain machines were usually clearly logical servers). That was the hot new thing in the '80s, but PLATO was not of the '80s, it was of the '60s. PLATO wasn't even really a client-server architecture: it was a terminal-computer architecture, in which individual PLATO terminals interacted with one of multiple (mostly DEC) mainframe or midsize computers that ran the actual logic.

PLATO wasn't just multi-user, though, it was multi-computer. To form one integrated system out of multiple independent sets of computers and terminals, PLATO replicated all of the user data between the computers. Lotus Notes inherited the same approach: data was stored in a database, and communicated between users by replicating that database between machines.

Everything in Lotus Notes is a note, and a database is a collection of notes that are identified by unique IDs. When a note is updated, that note is replicated to other copies of the database. Over time, the obvious performance and reliability problems with this architecture became apparent and the replication process became a lot more sophisticated, but it always worked on this simple logical model of updating the local database and then replicating it to others.

And that was about it—the database full of notes was all there ever was to Lotus Notes. That and an incredible amount of functionality exposed to the user by the fact that notes could incorporate simple scripts, arbitrary programs, workflow rules, and entire GUI layouts. Lotus Notes did not differentiate between "user data" and "program data" at a low level, and indeed users could edit views, write scripts, and build entire applications on top of Lotus Notes that replicated to other users just like an email.

The kind of freedom that Lotus Notes gave its users was incredibly empowering, but also a bit of a nightmare for usability. I am reminded of the early object-oriented work, like Smalltalk, much of which came from a similar milieu of SRI and Xerox-inspired applied computing research. If everything is a note, then you can use the tools for manipulating notes to create anything. The Lotus Notes data model was extremely flexible, about as close to completely schema-less as practical, but it still offered indexing and full text search. There wasn't much that you couldn't shove into Lotus Notes if you tried, and for businesses that adopted it wholesale, it could expand in scope until it took over everything. Not just email and calendars but enterprise resource planning!

Early versions of Lotus Notes, before the IBM acquisition, allowed for programming using either an expression language very similar to Lotus 1-2-3 spreadsheet formulas (and called, sensibly, Formula) or an imperative language very similar to Visual Basic (called LotusScript). Using a tool called Designer, it was possible to visually edit GUI interfaces like forms and reports. These were backed by a Notes-specific query language, although later versions of Notes also gained an SQL compatibility layer and some options for interoperating directly with relational databases.

Because of the example of PLATO, Notes was architected around a client-server model. The client, generally called Lotus Notes, partially replicated the database to allow the user to view and edit notes. The server, which came to be called Domino, kept a complete copy of the database and executed enough of its logic to handle access controls. Like PLATO's replicated model, though, it was not expected that there be a single, central server. Many Domino servers could share the same database, and replicated changes among themselves. This architecture was very convenient for the era's business deployments, where each office location would have a local area network but network connections between sites were expensive and comparatively slow. Domino servers had the effect of consolidating user activity into a reduced volume of replication traffic, and when inter-office network links were lost the office still functioned normally, albeit as an island.

Despite its origins as a product explicitly for Windows, Notes maintained a degree of cross-platform capability. Domino was available for several platforms and the Lotus Notes client was available for pretty much anything. The simplicity of the Formula and LotusScript languages did a lot to simplify porting, although the system itself was originally written in C++. That all started to change when Lotus rolled in Iris and shortly after, in 1995, merged into IBM.

Lotus Notes is hard to write about because of the naming. The curious decision to call the server (which was, originally, called Lotus Notes Server) Domino already complicates the situation, and that itself appears to be a result of IBM's unique product vision. The IBM renaming churn went on for the whole span that Lotus operated under IBM, meaning that whether you call it "Notes" or "Lotus Notes" or "IBM Notes" or even refer to the entire thing as "Domino," you're probably correct for some point in the history. Modern IBM documents use elegant language like "the Notes and Domino product family." I have opted to just stick to Notes.

IBM was tremendously invested in the development of client-server microcomputer applications in the 1990s, unsurprisingly since they were the closest match to IBM's traditional strength in mainframe systems. The acquisition of Lotus was, no doubt, intended to advance that focus: Lotus Notes must have been one of the most prominent client-server products of the Windows '95 era. Its architecture, something like a "thin client" system that was derived from its mainframe precursor, felt akin to IBM's block terminals and generally fit well with IBM's approach to microcomputer applications (small client, big backend).

IBM was also investing in another project that fit their client-server vision: Java. Java was originally designed for embedded applications (interactive television!), but by its first official release in 1996 it had grown into more of a general purpose business application platform. The Microsoft .NET platform is a good later comparable, starting out where Java ended up. The "standard edition" and "enterprise edition" split of Java, and web service platform concept developing around them, fit client-server applications well. Java was widely seen as an easier, more productive language than C++. Best of all, Java's origins as a portable language to run on lightweight, embedded VMS made it a perfect fit for software that would need to run on a variety of different clients.


I put a lot of time into writing this, and I hope that you enjoy reading it. If you can spare a few dollars, consider supporting me on ko-fi. You'll receive an occasional extra, subscribers-only post, and defray the costs of providing artisanal, hand-built world wide web directly from Albuquerque, New Mexico.


Lotus Notes 1 through 3 had been iterative improvements, from 1989 to 1993, adding features and fixing defects. With Lotus Notes 4, spanning 1996 to 1999, IBM Lotus Development started on a wholesale port to Java. Java was added as a native scripting language, alongside Formula and LotusScript, and many newer Lotus Notes features were "Java first." The Java-ization of Lotus Notes could be said to have completed in 2008, when the Lotus Notes client was completely replaced with a full-Java implementation based on Eclipse 3.

Alongside the new world of the object-oriented user interface, IBM also adapted Lotus Notes to the web. Version 4 introduced a very simple web interface where users could view static notes through a web browser, and IBM added an SMTP bridge for interoperation with other email systems.

At the dawn of the 2000s, Lotus Notes' technical leadership had eroded. The state of the art in GUI applications was far more advanced, and Microsoft had invested in their own groupware products (Exchange and Sharepoint). As part of the Windows Server offering, the Microsoft products were better integrated into the Windows desktop experience. IBM's investment in web technologies had lagged, so while Sharepoint was never exactly a hot rod, it was easier to interact with than Lotus Notes.

Still, development continued apace. IBM retired the Lotus branding around 2002, decisively folding IBM Notes and IBM Domino into Big Blue. Domino Web Access provided a web interface by 2002, although it was limited and not much different from what we would now consider mere webmail. IBM introduced SameTime, an instant messaging system that integrated with Lotus Notes. QuickPlace, similarly, was a web-based file/document management system that integrated with Lotus Notes as well. Both of these were even initially Lotus-branded, although IBM dropped that practice a few years later (and, for some reason, renamed QuickPlace to Quickr. It was a time).

When we talk about Java and the web, you might remember something, perhaps with a shudder: applets. In 2008, IBM introduced XPages. XPages were basically Java Server Faces components that ran on Domino server. They interacted directly with the Notes database and were, in some ways, just web-based versions of Notes forms. You even edited them using Domino Designer, the IDE for "serious" Notes development. Unfortunately, XPages hewed too close to JSF and remained a separate platform from Notes itself. You could not simply view existing Notes forms via XPages, or even readily port Notes interfaces to XPages format. If you wanted to support both the desktop and web experience, as most businesses would around 2010, you tended to end up writing things twice. Next thing you know, you're only really actively maintaining the web version, and then you might as well be on Sharepoint which was then well established.

To me, the most captivating part of Lotus Notes is its decline. In the mid '90s, Lotus Notes was the dominant groupware platform by a wide margin—Forbes put Lotus Notes market share at 64% in 1995. In 1997, they had fallen to 47%. A 2008 survey put Lotus Notes at 10%. Considering the long cycles and sheer staying power of enterprise software, that was a remarkable fall—all the more so considering that at that peak, IBM spent over $3 billion to get their hands on it.

Admittedly, IBM buying a popular software product at great expense and running it into the ground is an old story. But there's another major player here too: Microsoft was at their best. The vast majority of Lotus Notes' users went directly to Microsoft Exchange, which besides its higher level of integration with Windows (both at a technical and sales level) was also agreed to be more performant and easier to maintain. I would wager that Microsoft was at their peak engineering competence in the early '00s, and they had a considerable late-mover advantage over software that carried all the baggage of predating open-standards TCP/IP networking. NetWare went into a precipitous slide for the same reason.

Standards themselves are another important part of the story. Early email systems were all proprietary, and weren't necessarily networked systems at all—the first email implementations just stored mail on the single machine that all of the users accessed via terminal. Lotus Notes having a completely proprietary implementation of email didn't stand out in that world. When Microsoft first launched Exchange, it had the same limitations. That changed fast, albeit more by accident than intention. ITU X.400 had been expected to provide the standards for email on the public internet, replacing the hodgepodge of proprietary and network-specific open standards. Instead, X.400 failed to do much of anything at all—but not before it became the basis of Microsoft Exchange.

Exchange ended up in sort of a standards purgatory, an implementation of an open standard that died before Exchange could even launch. Exchange's X.400 capabilities became a proprietary standard of unusual origin, and most of industry and academia opted to follow the NSF example and adopt the older and simpler SMTP. Microsoft apparently understood that interoperability would be critical for the future of email, so Exchange was marketed from the very start as a multi-protocol system that could speak SMTP as fluently as anything else. That wasn't ever 100% true, but it was the idea that mattered. Lotus Notes had SMTP support but it was lagging behind, Exchange was the future focused on interoperation.

The web story was almost exactly the same. That's not to say that Exchange had a good version of a web interface, Microsoft has famously struggled with messes like Outlook Web Access. But they were still more agile than IBM, and their complete vertical control of the desktop experience meant that their weird proprietary web technology (ActiveX) fared better than IBM's weird proprietary web technology (a confusing tangle of Notes browser plugins and Java applets). Besides, Lotus's web features were apparently separately licensed at great cost. Microsoft wasn't cheap but, in this case, they were the budget option.

Last of all is the elephant in the room. It is hard, today, to explain exactly what Lotus Notes was. That's not a recent problem. In 1998, Forbes wrote:

Even before IBM arrived, Notes' identity had been blurred; it's no clearer now. First the software was marketed as a system to make it easy for a widely dispersed group of employees to work together editing a document or managing a project. Then Notes was redefined as a tool for building customized collaborative applications. Now Lotus seems to be playing up the E-mail function in Notes and positioning it as a replacement for cc:Mail. The latter was once a leader in its field but is now suffering a slow death.

cc:Mail! That's a whole different article. So let's stick to the point: the fact that Lotus Notes sort of defined a product category became a liability as other vendors muscled in with more targeted, more narrowly focused, and more obviously useful competition. Lotus Notes started to sound like Zombocom: You can do anything! Microsoft was just selling email and calendar. Notes' large scope was a problem for the user experience as well; besides the fact that the Notes client looked and felt dated by the '00s, the generality and depth of its capabilities meant that it was also just plain hard to use.

In 2018, IBM sold what remained of Lotus Development to an Indian software company called HCL. HCL is a classic IT consulting firm, with a portfolio that spans "Industry 4.0" to "SAP consulting." They acquired Lotus as part of a bundle of IBM castoffs: some of you might remember BigFix. Lotus Notes is now HCL Notes, and as far as I can tell HCL intends to just enjoy the revenue as long as legacy customers will pay them to keep Notes running.

That's another part of the allure of Lotus Notes: it might be the most legacy of legacy software. I have never worked at an organization that was using Lotus Notes, but everywhere I've worked that wasn't a startup had a powerful institutional memory of back when, in the Lotus Notes Times. Some people remembered it fondly, most people remembered it hatefully, but they all remembered it.

Will GMail ever inspire such emotion?

  1. The more things change, the more they stay the same...

  2. Lotus Symphony was Lotus's office suite for DOS, they also developed an office suite for MacOS called Lotus Jazz. You can appreciate the theme consistency of the names, but it quickly becomes confusing: Lotus was acquired by IBM in 1995, and became another division of a company that also offered a software engineering collaboration platform called Rational Jazz. You might get excited and think that perhaps one lead to the other or something, but this appears to be pure coincidence.

  3. At the time, Eclipse was being positioned as a more general framework for GUI software. In practice it didn't take off for anything besides other IDEs, but there was a brief heyday of Eclipse Framework productivity tools. Think of the days when the Flickr Uploadr was XUL-based and pretty much Firefox in a slim trenchcoat. But for Eclipse. This is actually very interesting because, in a parallel to Lotus Notes, Eclipse was architecturally inspired by IBM's block-based mainframe terminals, informed by research work with Smalltalk.

[syndicated profile] scalziwhatever_feed

Posted by John Scalzi

I didn’t get a shot when I got in — I was busy doing other things and then I was busy taking a nap — but here’s one to make up for the lapse. I’m in toen for the Tucson Book Festival, and if you come to it tomorrow (Sunday) I will have two panels and two signings. Come on down! And wear a hat, they’re having a lot of sun here.

— JS

[syndicated profile] cks_techblog_feed

Posted by cks

Via Filippo Valsorda, I recently heard about a proposal to add dependency cooldowns to Go. The general idea of dependency cooldowns is to make it so that people don't immediately update to new versions of dependencies; instead, you wait some amount of time for people to inspect the new version and so on (either through automated tooling or manual work). Since one of Go's famous features is 'minimum version selection', you might think that a cooldown would be unnecessary, since people have to manually update the version of dependencies anyway and don't automatically get them.

Unfortunately, this is not the actual observed reality. In the actual observed reality, people update dependency versions fast enough to catch out other people who change what a particular version is of a module they publish. This seems to be in part from things like 'Dependabot' automatically cruising around looking for version updates, but in general it seems clear that some amount of people will update to new versions of dependencies the moment those new versions become visible to them. And if a dependency is used widely enough, through random chance there's pretty much always going to be a developer somewhere who is running 'go list -m -u all' right after a new version of the package is released. So I feel that some sort of a cooldown would be useful in practice, even with Go's other protections.

I follow the VCS repositories of a fair number of Go projects, and a lot of their dependency updates are automated, through things like Dependabot. If these things supported dependency cooldowns and if people turned that on, we might get a lot of the benefit without Go's own mechanisms having to add code to support this. On the other hand, not everyone uses Dependabot or equivalent features (especially if people migrate away from Github, as some are) and there's always going to be people checking and doing dependency updates by hand. To support them, we need assistance from tooling.

(In theory this tooling assistance could be showing how old a version is then leaving it up to people to notice and decide, but in practice I feel that's abrogating responsibilities. We've seen that show before; easy support and defaults matter.)

While I don't have any strong or well informed opinions on how this should be implemented in Go, I do feel that both defaults and avoiding mistakes are important. This biases me towards, say, a setting for this in your go.mod, because then that way it's automatically persistent and everyone who works on your project gets it applied automatically, unlike (for example) an environment variable that you have to make sure everyone has set.

(This elaborates on some badly phrased thoughts I posted on the Fediverse.)

zoo!

2026-03-14 22:49
kaberett: Trans symbol with Swiss Army knife tools at other positions around the central circle. (Default)
[personal profile] kaberett

highlights included:

otherwise everything is still Migraine World Summit (though I have once again learned a useful thing today! neck pain can be a prodrome symptom!) and Special Interest.

The TBOTE Project

2026-03-14 22:12
[syndicated profile] jwz_blog_feed

Posted by jwz

This is some boss-level forensic accounting demonstrating that Facebook secretly wrote and is shepherding the various "age verification" bills.

Age Verification Lobbying: Dark Money, Model Legislation & Institutional Capture:

How corporate lobbying, think tank infrastructure, competing model legislation, and obscured funding networks are shaping age verification policy across 45 states and Congress.

This investigation documents a national lobbying operation spanning corporate spending, think tank infrastructure, dark money networks, and competing model legislation templates. Meta spent a record $26.3 million on federal lobbying in 2025, deployed 86+ lobbyists across 45 states, and covertly funded a group called the Digital Childhood Alliance (DCA) to advocate for the App Store Accountability Act (ASAA). But the operation extends beyond Meta. [...]

This investigation traced funding flows across five confirmed channels, analyzed $2.0 billion in dark money grants, searched 59,736 DAF recipients, parsed LD-2 filings, and mapped campaign contributions across four states to document the operation.

Previously, previously.

[syndicated profile] jwz_blog_feed

Posted by jwz

AI job losses free up time for unemployed mobs to burn down tech CEO's houses

"Getting laid off without warning from my copywriting job has done wonders for my work-life-bloodthirsty mob balance," reports Taylor Grayden, 35, of Vancouver. "Back when I had a job I never would've had the free time to organize an unruly rabble and march towards the beach house of (Open AI CEO) Sam Altman. But now I'm getting so much more violent retribution accomplished in a day." [...]

"I felt so lost after I was let go at my analytics firm so my whole department could be replaced by Claude AI," explains Sarah Brightwell, 42, of Kingston, ON. "But then I started learning how to use AI as a tool -- specifically for planning a multi-week siege of the sprawling compound of Anthropic CEO Dario Amodei."

"Granted, the attack plans Claude spit out were full of hallucinations, but it got the ball rolling for me to organize my fellow unemployed humans and get marching," Brightwell adds, tightening the bolts on her homemade trebuchet. "After all, AI can't throw a molotov cocktail!" [...]

"Sure, we probably could have avoided this if we'd accompanied our artificial intelligence products with any kind of workable universal basic income system," explains Altman from one of his currently-burning $12.8 million San Francisco homes. "But I'd still rather die with all this money."

Previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously.

vivdunstan: The 15th Doc swirling round on the dance floor in his kilt (ncuti gatwa)
[personal profile] vivdunstan
"The Importance of Being Earnest" of course, starring Ncuti Gatwa. Which is currently free to stream online via YouTube until March 18th.

I hadn't realised before starting to watch it that Julian Bleach (Davros) is in it too, and also Richard Cant ("Blink"). I knew Sharon D Clarke (Grace, Thirteenth Doctor era) played Lady Bracknell. Oh and Ronkẹ Adékọluẹ́jọ́, who plays Gwendolen, also appeared in a couple of Twelfth Doctor TV stories. Ncuti Gatwa's main co-star Hugh Skinner hasn't been on TV Who, but has appeared in Big Finish audios. Oh and Amanda Lawrence (Doomfinger in "The Shakespeare Code") is also in it!

I've watched the first half of the play tonight and will watch the rest tomorrow or the next day. Very much enjoying it.

[syndicated profile] jwz_blog_feed

Posted by jwz

Last night at DNA Lounge, a room full of people chanted "No AI" along with Anton Corazza's song of the same name. The kids might be alright!

Rustage has entered the chat:

Previously, previously, previously.

Antimatter Truckers

2026-03-14 18:32
[syndicated profile] jwz_blog_feed

Posted by jwz

Swiss remake of The Wages of Fear:

The reality is reassuringly mundane. Antimatter emitters are readily available at supermarkets in the form of bananas, which emit antiparticles through the radioactive decay of potassium. Sadly, they have limited value for understanding the universe. The device on Cern's truck will carry about 1,000 antimatter particles, weighing about a billionth of a trillionth of a gram. Should the containment fail, and the antimatter make contact with normal matter, the resulting pulse of energy would be so feeble, the load doesn't even warrant a radioactive label.

Previously, previously, previously, previously, previously, previously, previously.

Demo station

2026-03-14 18:15
[syndicated profile] jwz_blog_feed

Posted by jwz

Since we had dozens of video game demo stations at our various GDC events this week, I snuck an XScreenSaver kiosk into the mix. I'm not sure anyone noticed it.
[syndicated profile] jwz_blog_feed

Posted by jwz

"What is DEI?"
"Feeeeeeeeemales."
Oh no. Anyway

On Friday, government lawyers in the lawsuit filed a court record which said they asked the plaintiffs to remove the videos "from the internet due to concerns that the publication of the videos could subject the witnesses and their family members to undue harassment and reputational harm." The filing then said that Fox specifically "has been subject to harassment and has received a number of death threats since the videos and video clips were publicized and circulated."

Internet Archive; torrent magnet link (only 5 seeders!)

Previously, previously, previously, previously, previously, previously.

LLM time

2026-03-14 13:33
graydon2: (Default)
[personal profile] graydon2
Note: this is not a thinkpiece and there is no need to debate it or repost it or comment about it. It offers no conclusions and takes no sides besides the one I've already admitted publicly (a reluctant but fatalistic willingness to use LLMs day-to-day, because they seem to work). It's mostly just a journal entry noting the occurrence of a significant change in the nature of my profession. I've turned off comments as I do usually for "things people are likely to heckle me about pointlessly anyways" because I'm tired and don't have patience for that.

With that out of the way: 2025 (particularly near the end of it) and early 2026 have been, for my corner of the software industry, extremely unusual times.

LLMs turned a corner. I'm not sure how else to put it. If you are not interacting with them yet in your day job, you are perhaps lucky, perhaps unlucky, I'm not sure how to judge that but you are definitely operating in some level of ignorance of what has occurred. You may be seeing the 2nd order effects and hiding. You may be telling yourself nothing's changed and it's all just smoke and mirrors, a marketing campaign by con artists aimed at the gullible. I wish it was. But as far as I can tell this is not so: LLMs really, really turned a corner.

Their capabilities expanded a lot. Coding capability seemed like the first bump (especially around the late fall / early winter: the opus 4.5 / gemini 3 / gpt 5.2 series). But it was quickly clear that the capability also extended to something much worse: vulnerability hunting. They can break software even better than they can write it -- I guess because "you only need to be right sometimes" with vulnerability seeking -- and "breaking" has even more people eager for the new capability.

The change has felt, to me, very sudden and very severe. In a matter of months a lot of people I know personally switched from "playing around seeing what I can do" to "I literally never write code by hand anymore" to "my boss is asking whether I can write 100x more code per day and/or firing me" to "help help my team is under attack by hundreds of new security vulnerabilities and can barely keep up".

I still write some code, but less and less, and more of it is around the margins: touchups, sketches of APIs and data structures, subtle stuff it's easy to be subtly-wrong about, or perhaps LLM-supervisory bits. Because the LLM really does often write the main logic as well as I would at this point, and faster, and more persistently. And also I'm now busy responding to all the damn vulnerabilities. There is an arms race, and I'm now plainly in it.

This is the fastest and most violent change to working conditions and assumptions I've witnessed in my career, including the arrival of the internet and open source and distributed version control and cloud computing and all of that. Nothing else is in the same ballpark.

Software projects have tried to adapt. Some are trying to embrace the tools, some are firmly rejecting them. Some have closed their issue trackers to new submissions which were all slop. Some maintainers have quit, some contributors have been banned, some dependencies have been rolled back or severed, some forks are emerging. A lot of people are re-evaluating (and some rebuilding) their entire software stacks. A lot of people are debating licenses again, with even more fury than they did during the drafting of GPLv3.

Thinkpieces on this event proliferated, many very sour. People wrote about mourning their loss of identity as programmers. People wrote about fear for their loss of jobs. People wrote a lot about their personal disgust with the slop, their fury at the billionaires, their sense that all this is part of of the fascist turn of America. The level of anger in the community of programmers is unlike anything I've ever seen before. People are making lists of who's been infected by the menace and who's still clean. The community is tearing itself apart. Professional and volunteer relationships ended, friendships lost, battle lines drawn.

I'm not writing this to come to any particular conclusion, just to note that it's happened, that it's a set of events that I've experienced as they're happening. This is a journal and sometimes all I can do with it is log events. I don't know how this is going to end, or what to make of it all, I really don't. It's sort of interesting, deeply confusing, sometimes sort of fun, mostly sort of horrifying, sort of miserable. The unit economics of making and breaking software in 2026 are completely different than they were in 2025. More than anything, it's just weird.

This time next year we could all be out of work, or dead from a nuclear war, or even-more-burnt-out from sustained 100x higher velocity of code and vulnerabilities with teams of adversarial LLMs, or .. the whole thing could collapse because maybe, just maybe, it really is "all just a bubble" pushed by VCs on credulous rubes like myself, and it'll vanish like a bad dream. I'm not presently betting on that, but I couldn't have predicted this year, so I'm not going to make any predictions about the next.

I guess I'm sorry to anyone who thinks I'm infected, or facilitating the fascists, or whatever. I'm just trying to adapt. I hope you can see me as a human again someday. I miss the past too. I don't see a way to go back to it, but I'd like it too if there were one.

Weekend catchup

2026-03-14 20:32
mtbc: maze L (green-white)
[personal profile] mtbc
Our weekends typically involve a Saturday of errands, today's were car-based: returns and purchases at IKEA, deposits and withdrawals at the container we still rent (plus first carrying stuff down to the car), also stops at Asda, Matthew's, Primark, Boots. We came away from Asda with plenty of must-sell-today discount fish and meat, R. cooked us some for our evening meal. The stop at Matthew's was because we wanted some Southeast Asian rice, they have the more Eastern products; our local Foodasia has plenty of other rice but is rather more South Asian. Basically, our neighborhood is much more South Asian, the East Asian stuff is over on the other side of the city. Among all this, we were lucky with the soccer: we passed near a stadium but not when everybody was entering or leaving.

Our Sunday can be varied: we may go out somewhere more pleasant, like the beach (cold though they are here) or the park, where L. our dog can run around. I may have something else going on that day, like seeing family in Dundee. Tomorrow, I hope is like last weekend: I will stay home and catch up on all manner of non-work things. Though, some Sundays when I'm home, I am just tired and don't do much. I plan to at least get to open and file pending mail, file this year's FBAR with FinCEN, etc. That doesn't sound like much but, beyond work and necessary chores, it seems that it's difficult for me to have the energy to do much else. R. is very understanding of how we both have difficulty making time to get done all we feel we should or want. Like that stuff in the container, we need to do a proper sorting: we won't soon plausibly afford to live anywhere we can store it all.
mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)
[staff profile] mark posting in [site community profile] dw_maintenance

Happy Saturday!

I'm going to be doing a little maintenance today. It will likely cause a tiny interruption of service (specifically for www.dreamwidth.org) on the order of 2-3 minutes while some settings propagate. If you're on a journal page, that should still work throughout!

If it doesn't work, the rollback plan is pretty quick, I'm just toggling a setting on how traffic gets to the site. I'll update this post if something goes wrong, but don't anticipate any interruption to be longer than 10 minutes even in a rollback situation.

poached eggs

2026-03-14 18:54
fanf: (Default)
[personal profile] fanf

https://dotat.at/@/2026-03-14-eggs.html

A few weeks ago I was enjoying a couple of boiled eggs

(in the shell, with plenty of salt and pepper, and buttery fingers of toast to dunk into the runny yolk)

and pondering how fiddly it is to cut off one end of the shell after boiling compared to eating a poached egg. And I was annoyed because (I thought) I didn't know how to poach eggs.

Read more... )

Photo cross-post

2026-03-14 12:33
andrewducker: (Default)
[personal profile] andrewducker


The first time Gideon fell asleep in front of the toilet we moved him to a comfy chair. From where he woke up still feeling sick and Jane found him lying on the floor with a bucket he'd found and relocated him back to the toilet, where he then fell asleep again.

I missed all of this because I had passed out in bed feeling rubbish. I did wake up to various noises, but each time I did I tried to open my eyelids, failed, and fell back to sleep again. Thankfully Jane isn't feeling as bad as me, and Sophia was off having a play date at the other end of the street.

So far nobody has actually thrown up. Fingers crossed that continues.
Original is here on Pixelfed.scot.

james_davis_nicoll: (Default)
[personal profile] james_davis_nicoll


Seven books new to me: four fantasies, one science fantasy, one science fiction, and I am not sure how to categorize the Shepard. At least three are series books.

Books Received, March 7 — March 13


Poll #34364 Books Received, March 7 — March 13
Open to: Registered Users, detailed results viewable to: All, participants: 28


Which of these look interesting?

View Answers

The Lion and the Deathless Dark by Carissa Broadbent (July 2026)
4 (14.3%)

Teach Me to Prey by Jenni Howell (December 2026)
0 (0.0%)

Heart of Thieves by Jessica S. Olson (September 2026)
0 (0.0%)

The Dagger in Vichy by Alastair Reynolds (October 2025)
12 (42.9%)

Crows and Silences by Lucius Shepard (December 2024)
9 (32.1%)

Engines of Reason by Adrian Tchaikovsky (September 2026)
12 (42.9%)

The Heart of the Reproach by Adrian Tchaikovsky (July 2025)
10 (35.7%)

Some other option (see comments)
0 (0.0%)

Cats!
22 (78.6%)

[syndicated profile] schneier_no_tracking_feed

Posted by B. Schneier

This is a current list of where and when I am scheduled to speak:

The list is maintained on this page.

[syndicated profile] nwhyte_atom_feed

Posted by fromtheheartofeurope

On 28 November 1290, Eleanor of Castile, queen of England, died at the age of roughly 49 in Harby, close to Lincoln. She had been married to Edward I for 36 years, and they had been king and queen for 18 of those years. She was pregnant at least fourteen times, and was survived by five daughters and one son, the future Edward II, who was only six when his mother died.

Her body (well, most of it) was slowly transported to London over twelve days before her funeral at Westminster Abbey on 17 December. Over the next five years, King Edward commissioned monumental crosses to be erected at every town where the funeral procession had stopped for the night. Whether there were eleven or twelve is disputed (see below); what is certain is that only three of the originals now remain, along with a Victorian reconstruction of a fourth that many of you have walked past, probably without realising what it is doing there.

I was at a loose end in London last Sunday, and, inspired by Alice Loxton’s book (again, see below), I decided to rent a car and visit the three remaining original Eleanor crosses. I left the Budget office near Victoria Station at 1045, reached the Northampton cross at 1245, left Northampton (after lunch) at 1415, reached Geddington at 1500, spent twenty to twenty-five minutes there, reached Waltham at about 1720, did not stay long, and had dropped the car back by 1900. So that was more than eight hours on the road, of which about six and a half were driving, for one long stop in Northampton and two short stops at the other two crosses. It was a bit mad, I must admit. But it was worth it.

I started with the cross at Hardingstone near Northampton. It’s easy to get to, as it’s on what is still the main road between London and the town centre. Parking, and then crossing the busy highway, were both exciting experiences. But the cross itself commands its surroundings, and would have dominated the pedestrian, mounted or horse-drawn traveller’s experience of approaching or leaving Northampton in the centuries before the railway or the car. It is about 10 metres tall, but stands on a prominence, somewhat obscured by trees which would not have been there in the 1290s.

My old friend Tommy, who comes from Magherafelt but has been working across the water for many years, happens to live within a stone’s throw of it. We failed to take any selfies together, so you’ll just have to take my word for it that he was there. It’s particularly appropriate to meet an Irish friend at Hardingstone, because according to the royal financial accounts, the sculptures of Eleanor on the Hardingstone cross were created by one William of Ireland between 1292 and 1294. This makes them literally the oldest surviving artworks by any Irish artist whose name is still known today.

Queen Eleanor, regal and unruffled, looks down at passers-by. The northern statue appears least weathered (or perhaps the restoration of the monument in 1713 was more long-lasting here). It’s sobering to think of the Irish sculptor seven centuries ago, pressed to meet a government-imposed deadline, and at the same time trying to preserve a sense of the dead queen’s personality for the ages. And he succeeded.

We went for lunch at the nearby Delapré Abbey (I actually ordered breakfast there, having skipped it earlier due to oversleeping), and I left Tommy to it and proceeded to Geddington Cross, the northernmost of the three survivors, in the middle of a quiet little countryside village. When I was 18, I worked for two months on an archaeology site at Raunds, 20 km away, so it’s a part of the country that I have some vague if increasingly distant experience of.

Geddington is a charming place. If driving to the Cross from the southwest (as I was) you have to brave a ford across the river Ise, the roadbridge being OK for pedestrians but not vehicles. Any objective assessment would rate the Geddington Cross as the best of the three survivors. At 13 metres, it is the tallest of them. It has only three sides, at a triangular junction in the middle of the village, so it is much slimmer than the other two. Eleanor looks sternly down in all three directions. The sculptor here is not known, but is thought to have been local, and unlike the other two crosses the stone was definitely local rather than imported from Normandy. (NB that although the soot and weathering makes Eleanor’s face look a bit skull-like, she’s just in need of a scrub.)

By great good fortune, local guide Kam Caddell was finishing up a tour as I arrived. He pointed out that the cross is rooted in an ancient sacred spring, mounted on pilings that will disintegrate if the water is ever drained. Then he took a few minutes to lead me through the history of Geddington – a major medieval centre of economic and political activity, which however was cut off in the Age of Steam. “If the railway had come to Geddington, we’d be 60,000 people. Instead it went through two tiny little farming villages called Kettering and Corby and everyone forgot this was the center of the Midlands.” You can hear him on this podcast with Alice Loxton, produced by Brigham Young University.

Kam is full of heterodox theories about the Crosses. He doubts that there was ever one at Grantham – the documentation is lacking. He doubts that there is a single original stone left in the cross at Waltham. Most provocatively, he doubts that they ever actually had crosses at the top. The picturesque stump at the top of the Northampton cross is a later addition. There is no room for one atop the Geddington cross. Myself, I kinda wonder why they would have been called “crosses” in that case. But Kam puts his case passionately.

Perhaps it was the long hours of driving, and the light (such as it was) beginning to dwindle, but I was unable to summon much enthusiasm for Waltham Cross, in one of the more godforsaken corners of Essex just outside the M25. Perhaps at a time of week other than Sunday evening, it would not feel like it is sitting at the core of a decaying Home Counties burgh, asserting history despite its neighbours, covered with bird mesh to minimise the amount of poo on the dead queen.

The original statues were also created by a known sculptor, Alexander of Abingdoni. They were moved to Cheshunt Public Library in the 1950s, and are now in the the V&A. The replacements are putting on a stiff upper lip, under the mesh.

Waltham Cross is a depressing place, with St George’s Cross flags drooping from the lamp-posts around the unloved monument to a forgotten foreign royal. I did not stay long.

The last of the Eleanor Crosses was originally erected on a spot now occupied by the equestrian statue of King Charles I on Trafalgar Square – 350 years before King Charles was beheaded, more than half a century before the Battle of Trafalgar after which the square is named. It is still the spot from which distances from and to London are measured. I went and took a couple of photographs on Tuesday (it is not far from my employers’ London office).

Like the other missing crosses, the original was destroyed by anti-monarchist Puritans in the 1640s, 350 years after Eleanor’s death. Unlike the others, the Victorians decided to recreate it in 1864, about 200 metres from where it had originally stood, doing their best to echo the monument originally built near the ċierring, the bend in the river Thames. And they put a railway station beside it. It is blackened with a century and a half of soot now, but if you look for even half a second, you can see the best known work of Thomas Earp – the replica statues of Queen Eleanor in the replica of the old Charing Cross in the station forecourt.

Are the crosses England’s Taj Mahal? Yes and no, I suppose. They are a visible monument constructed at the direct order of the monarch to express his private grief. Many other memorial structures in England are based on the structure of the Eleanor Crosses (though having said that, there are only so many ways to build a tall stone thing). The Albert Memorial, also commemorating a deceased royal consort, was explicitly modelled on the Eleanor Crosses by Gilbert Scott, and boasts a representation of William of Ireland on its frieze, complete with the shadow of the Hardingstone Cross in the background.

Photo taken by me in March last year

We know nothing about William of Ireland except that he was alive and sculpting in the early to mid 1290s. We know more about Eleanor of Castile, and much much more about Edward I (memorably portrayed by Patrick McGoohan in that awful film Braveheart). The crosses were erected on main roads and significant interchanges, so that people would remember Eleanor. People don’t remember her, most of the crosses are lost, and the paths of commerce and politics have diverted to other routes. But 730 years on, an unimaginable length of time, three of the crosses are still there; so I think that as a building project, it counts as a success.

I was inspired to take this journey by reading Eleanor: A 200-Mile Walk in Search of England’s Lost Queen, by Alice Loxton. The second paragraph of its third chapter is:

Your body was laid with feet pointing east and head to the west – the idea being that you were looking east towards Jerusalem and, on the event of Jesus’ second resurrection, the Second Coming, you could easily sit up and watch it all unfold. So everyone in the churchyard was ready to sit up, where theyd be facing the same direction, like theatre stalls. No swivelling required. It’s worth keeping this in mind – if you want to make the front row, make sure you’re buried in the east corner of the churchyard. And make sure your plot isn’t near someone who coughs.

Alice Loxton went the whole hog, recapitulating Eleanor’s funeral procession on foot in December 2024, matching the dates of 734 years earlier to her own progress as far as possible, finding the traces of folklore and history at each stop, and documenting the process with photographs which are integrated nicely into the text. The tone is breezy and breathless, but also respectful of the histories through which she is walking. She is a bit more cheerful than me (on the whole she had better weather than I did last weekend, though she is frank about the days when she did not). The reader will cheer for her when, at the end of the journey, she is admitted to the closed chapel in Westminster Abbey where Eleanor now rests. She also reports on a mural about the history of the crosses in Charing Cross tube station – I must look for it next time I am passing and not in a rush. It’s a book that you could comfortably get for someone with at least a vague interest in English history, whether or not they are particularly interested in the thirteenth century. You can get Eleanor: A 200-Mile Walk in Search of England’s Lost Queen here.

I also managed to get hold of Carsten Dilba’s Memoria Reginae: Das Memorialprogramm für Eleonore von Kastilien, a massive scholarly assembling of everything that is known about the Eleanor Crosses and the other funerary art commissioned in Eleanor’s memory by Edward I, and I have dipped into it for my notes above. The second paragraph of the third chapter has 387 words in the original German with another nine footnotes, so I won’t post it (also I have really only read a few pages so I feel it’s cheating to tick it off my list). The list price is €78, but I was able to get it for €7.80 here.

I hope this will inspire you to go and look at the local equivalent to an Eleanor Cross in your own neighbourhood.

james_davis_nicoll: (Default)
[personal profile] james_davis_nicoll
I know my site is down. Giving it an hour before I pester the host.

Meanwhile Read more... )
vivdunstan: Photo of me from Melrose Grammar School plus NHS thanks (nhs)
[personal profile] vivdunstan
Got to the end of my 4-a-day home blood pressure readings (was filling the complete form, and just had space left to do 2 final readings this morning). My average over the week-ish is coming in at 125/80. That'll do nicely.

I have a cerebrovascular disease, so keeping my blood pressure within safe levels is important. But my readings in the health centre are not reliable due to white coat syndrome. I am happy to check at home.
vivdunstan: A vibrantly coloured comic cover image of Peter Capaldi's Doctor, viewed side on, facing to the left, looking thoughtful (twelfth doctor)
[personal profile] vivdunstan
Recently rewatched this, and enjoyed it again, though perhaps not as much as the first time.

The Golden Age style whodunnit aspect is fantastic. Though I found it frustrating that the Doctor already knows about the Foretold, making me feel one step removed from the story at that point. Writing about (fictional) past legendary things can be tricky, but I think a smoother bit of sleight of hand could have improved this. Taking the viewer along with the Doctor on the journey of discovery can be an important element.

I still find the split between the Agatha Christie esque train setting and the futuristic lab to be extremely jarring. This is a longstanding problem I have with Doctor Who stories that have an atmospheric opening setting, sometimes historical, and then relocate to a different much more scifi setting. Think "The Stones of Blood" for example.

Yet there is a good resolution, and the guest cast is strong. Not least Frank Skinner as train chief engineer Perkins, who has an unnerving ambiguity about whether he's an ally or not. Nicely done.
[syndicated profile] cks_techblog_feed

Posted by cks

Back in the old days, search engines mostly crawled your sites with their regular, clearly identifying HTTP User-Agent headers, but once in a while they would switch up to fetching with a browser's User-Agent. What they were trying to detect was if you served one set of content to "Googlebot" but another set of content to "Firefox", and if you did they tended to penalize you; you were supposed to serve the same content to both, not SEO-bait to Googlebot and wall to wall ads to browsers. Googlebot identified itself as a standard courtesy, not so you could handle it differently.

Obviously those days are long over. It's now routine and fully accepted to serve different things to Googlebot and to regular browsers. Generally websites offer Googlebot more access and plain text, and browsers less access (even paywalls) and JavaScript encrusted content (leading to people setting their User-Agent to Googlebot to bypass paywalls). Since people give Googlebot special access, people impersonate it and other well accepted crawlers and other people (like me) block that impersonation.

This is part of an increasingly common general pattern, which is that different HTTP User-Agents get different results for the same URL. Especially, some HTTP User-Agents will get errors, HTTP redirections, or challenge pages, and other User-Agents won't; instead they'll get the real content. What this means in concrete terms is it's increasingly bad to take the results from one HTTP User-Agent and assume they apply for another. This isn't just me and Wandering Thoughts; for example, if a site has a standard configuration of Anubis, having a User-Agent that includes 'Mozilla' will cause you to get a challenge page instead of the actual page (cf).

(One of the amusing effects of this is what it does to 'link previews', which require the website displaying the preview to fetch a copy of the URL from the original site. On the Fediverse, fairly often the link preview I see is just some sort of a challenge page.)

In practice, you're probably reasonably safe if you're doing close variations of what's fundamentally the same distinctive User-Agent. But you're living dangerously if you try this with browser-like User-Agent values, either two different ones or a browser-like User-Agent and a distinctive non-browser one, because those are the ones that are most frequently forged and abused by covert web crawlers and other malware. Everyone who wants to look normal is imitating a browser, which means looking like a browser is a bad idea today.

Unfortunately, however bad an idea it is, people seem to keep trying fetches with multiple User-Agent header values and then taking a result from one User-Agent and using it in the context of another. Especially, feed reader companies seem to do it, first Feedly and now Inoreader.

Hockey hockey hockey

2026-03-14 02:29
rmc28: Rachel in hockey gear on the frozen fen at Upware, near Cambridge (Default)
[personal profile] rmc28

I hadn't been on the ice since last Saturday (Huskies and Women's Blues practices were all Varsity squads only, and Kodiaks practice got cancelled by the rink) but I made it to and through Warbirds practice tonight. It was so worth it. I also got my Varsity notebook from Women's Blues: every team member gets a notebook, and everyone writes a note in every teammate's notebook, and we read them before Varsity to inspire us. Mine was very sweet and I love the team very much for making me welcome.

I need to leave the house in 7.5 hours to get back to the rink for Varsity. I'm playing in alumni game 1, getting cleaned up during alumni game 2, and spending the rest of the day in the scorekeepers box with a rotating cast of some of my favourite people. The three non-alumni games will be livestreamed

  • 14:00 Mixed 2nds (Huskies v Vikings B)
  • 17:00 Women's Blues
  • 20:00 Men's Blues

I also had a little art session this evening before going to the rink, making signs for my Huskies teammates. The sign in Irish may well only be understood by the teammate who got me back into learning Irish this year - our class covered "how to cheer on your sports team" a couple weeks ago and I made careful notes - or maybe it will cause any lurking Gaeilgeoirí in the rink to make themselves known.

Two cardboard signs, hand-lettered to support the Huskies ice hockey team

I think I'm wound down enough to sleep now.

[syndicated profile] acoup_feed

Posted by Bret Devereaux

This is the second part (I, II) of our somewhat silly look about the plausibility of warfare in Frank Herbert’s Dune. Last week, we looked at the system of warfare that is dominant in the setting when the first book opens: warfare among the Great Houses. While I noted some worldbuilding issues I see – some of the physics doesn’t quite work out, I don’t think lasers are satisfactorily dealt with and the implied social system doesn’t seem even remotely stable– we’re going to accept for this part that the system works more or less as Herbert describes it.

The various Houses (Major and Minor) maintain relatively small militaries of trained close-combat fighters who fight using shields. Because shields reduce the effectiveness of ranged combat nearly to zero, this system of warfare dominates among the Great Houses and because untrained, unshielded fighters are so profoundly vulnerable to trained, shielded ones, outside military challenges to this system are generally unsuccessful, enabling the small, closed and mostly hereditary elite with their retinue-armies of shielded fighters to maintain a stranglehold on political and military power. They use that power to run relatively inefficient patrimonial ‘household’ governments over entire planets, siphoning off what little economic production they can – because their administration is so limited – to fund their small armies.

What keeps the armies small is both that the resources of the Great Houses are limited – again, small administrations – but also that the core components of industrial military power in this setting (trained fighters, shields, ornithopters, frigates) are clearly very expensive, both to build and to maintain. And as an aside, because it will be relevant below, it is clear even in the books that wear and tear on shields is a major cost: “The Harkonnens certainly used plenty of shields here, “Hawat said. “They had repair depots in every garrison village, and their accounts show heavy expenditures for shield replacement parts.” (Dune, 88, emphasis mine). In short, these elements of military power represent ongoing expenditures, requiring maintenance and logistics which is going to matter a bit below.

This week we’re going to look at how the Fremen disrupt this system and ask if the Fremen success in doing so seems plausible. We’ll do so generally accepting Herbert’s clear description of the Fremen as superlative warriors, even though long-time readers will know that I find the idea of the Fremen being such superior warriors broadly unlikely. But as we’ll see, even if the Fremen are remarkably skilled warriors, they are unlikely to succeed in their jihad against the society of the Known Universe.

Denis Villeneuve’s adaptation, I think, does a better job than any other at selling the impending horror of the jihad. Indeed, the David Lynch adaptation wholly fails at this, imagining Paul close to an uncomplicated hero, rather than as something approaching a horror villain.
In particular, the reduction of Stilgar from the clever, charismatic, thoughtful figure of the first film to the blind fanatic of the ending scenes of the second film is astoundingly powerful and well-delivered.

But first, as we’re going to cover below, equipping a fighting force with Dune’s version of modern military power – shields, ornithopters and frigates – is expensive. If you want to help me equip a Great House of trained fighters to challenge the Imperium, you can support this project over at Patreon. If you want updates whenever a new post appears or want to hear my more bite-sized musings on history, security affairs and current events, you can follow me on Bluesky (@bretdevereaux.bsky.social). I am also active on Threads (bretdevereaux) and maintain a de minimis presence on Twitter (@bretdevereaux).

Wars of the Fremen

We should start just by outlining exactly what the Fremen do, both what we see in Dune and what we are told about in Dune Messiah.

The Fremen are, at the time Dune begins, the native population of Arrakis and we are told there are about 15 million of them. They maintain some small levels of industry – mostly things which can be rapidly moved – back lack large industrial systems and notably lack the ability to produce any of the elements of industrial military power (shields, aircraft, frigates) essential to the warfare of the Great Houses, though they do at time capture and use this equipment.1 The Fremen are already highly capable warriors, but because they lack these elements of industrial military power – especially shields – it is easy for the militaries of the Great House to oppress them. In particular, the Fremen have no defense against laser weaponry, which is devastating against unshielded opponents.

When Paul arrives, he organizes the Fremen for what is initially a classic protracted war campaign against the Harkonnen occupation, which eventually sufficiently disrupts spice production to bring the emperor himself to Arrakis. The result is something of a science-fiction rerun of Dien Bien Phu: the foreign occupier, convinced that his industrial military renders him unbeatable in a conventional engagement intentionally and arrogantly extends his force into enemy territory only to be cut off and defeated.

A few things make this Fremen success work. First, the Fremen operate from a terrestrial base that their enemies cannot attack effectively (the deep desert). The Fremen also operate with tremendous local knowledge: because they are the indigenous population, it is easy for their agents to infiltrate into the settled zone the Harkonnen control, meaning that the Fremen have good visibility into Harkonnen operations even before their leader becomes a prescient demigod. Perhaps most importantly conditions on Arrakis negate most of the advantages of industrial military power. As Hawat notes, ornithopters suffer substantial wear-and-tear on Arrakis, making it expensive (but not impossible) to maintain large fleets of them; shields too apparently are hard to maintain. The large sandstorms that rage basically anywhere except in the small area protected by the ‘Shield Wall’ mountain range (which is where all of the cities are) can disable shields at almost any scale. But most of all, shields attract and drive mad the large local sandworms, making their use on the ground in the open desert essentially suicide.

Consequently the Fremen able to win in part because they occupy the one place in the whole universe where the military ‘package’ of the Great Houses does not work.

And to be honest, I do not find the way the Fremen win on Arrakis to be wholly implausible. Given their mastery of the local terrain and infiltration of the local population, it makes sense that the Fremen would be very hard to uproot and might steadily bleed an occupying force quite badly over time. At the same time, the idea that Shaddam IV and House Corrino might – somewhat arrogantly – assume they that could safely extend themselves down to the surface is the sort of military error regular armies make all the time. Finally, it also makes sense that the Harkonnen and Corrino armies coming to Arrakis might fail to adapt to Fremen warfare – fail to adapt to warfare without shields, for instance – because they do not perceive their primary security threat to be the Fremen (the Harkonnen, we’re told, consistently underestimate how many Fremen there are). So while they should respond to the Fremen with guns and artillery, it makes sense that initially they respond with the sort of armies that work for all of their other problems: trained melee fighters with shields.

And if – again, we’re accepting this for the sake of argument – if the Fremen are the superior close-combat fighters, the result of that effort might well go this way. Especially with a prescient leader pushing them forward to victory. Crucially, the victory at Arrakeen fundamentally depends on these local factors: Fremen knowledge of terrain enables Paul to mass his forces undetected and observe the Corrino disposition safely and to thus to stage a coordinated surprise attack against his opponents. Sandworms enable him to deliver an attack force rapidly through a sandstorm and the storm itself disables the defender’s shields, enabling him to disable their frigates and also neutralizing much of their airpower. Fremen victory is almost entirely reliant on factors unique to Arrakis.

So that is more or less fine. The problem I have is really with everything that happens next.

While Frank Herbert’s Dune (2000; the sci-fi miniseries) doesn’t engage much with the concept of the jihad, its sequel, Frank Herbert’s Children of Dune (2003), opens its treatment of Dune Messiah with this stark scene of the destruction wrought by the jihad, necessary for understanding the story to come. As always, it is limited by budget, but I think the sequence is effective.

What Happens Next…

I think we should be clear what Dune and especially Dune Messiah lead us to understand comes next to avoid unnecessary wrangling in the comments. While we do not see it, the Fremen wage an absolutely massive, known-universe spanning war in which they conquer thousands of worlds and kill sixty-one billion people (the statistic given in Dune Messiah).

Equally, we are supposed to understand that this result was inevitable. Indeed, this is one of the central themes of Dune, that by the time Paul’s prescience has developed sufficiently for him to understand the road to his Jihad, it is already too late to stop it. As we are told of Paul’s thoughts, “He had thought to ppose the jihad within himself, but the jihad would be. His legions would rage out from Arrakis even without him. They needed only the legend he already had become.” Just after, right before his duel with Feyd, he thinks, “from here, the future will open, the clouds part onto a kind of glory. And if I die here, they’ll say I sacrificed myself that my spirit might lead them. And if I live, they’ll say nothing can oppose Muad’Dib” (Dune 482, emphasis original). The point is the Jihad happens either way.

I want to stress that: even without Paul Atreides’ prescience, the Jihad happens and at the very least burns across the known universe doing massive destruction; in fact, even without Paul the Fremen win.

That position – that the destruction of the Fremen Jihad is not merely possible but inevitable to the point that Paul cannot stop it – puts a very, very high bar on its military plausibility. In particular it rules out any defense that Fremen victory is simply because Paul, as a prescient military leader, can simply pull an endless series of ‘inside straights.’ Remember: the Fremen explicitly still win even in Paul Muad’Dib Atredies is dead at the hands of Feyd Rautha Harkonnen. It is not enough for it to be possible for the Fremen to win, it must be impossible for them to lose.

Now in the thematic world of Dune, that is because military victory is fundamentally a product of the Fremen Mirage: societies have an inherent vitality to them and the Fremen are vital, hardened by the harshness of Arrakis, in a way that the Great Houses are not. In Herbert’s mind, that is enough: the ‘hard men’ created by the ‘hard times’ of Arrakis will inevitably triumph once an event – the emergence of Paul as a heroic figure – spurs them into action. Paul is thus die Weltseele zu Pferde, “the world-spirit on horseback,” the archetypal ‘great man of history’ who embodies supposed historical forces which are larger than him, which act through him and which would act without him.

Except of course the problem is that both the Fremen Mirage and the Great Man Theory of history are, to put it bluntly, rubbish– grand historical narratives which simply do not fit the contours of how history actually works. ‘Hard men’ from ‘hard places’ and ‘hard times’ lose all the time. Societies only seem ‘vital’ or ‘decadent’ when viewed in retrospective through the prism of success or failure that was contingent, not inevitable. History is full of movements and moments which cannot be explained through the agency of ‘great men.’ There is, in fact, no ‘world spirit’ guiding history like an invisible hand, but rather a tremendous number of contingent decisions made by billions of people with agency acting with free will.

So rather than simply assume that because the Fremen are moving with the ‘universe spirit’ of history as it were, that because they are a vital people, because they are ‘hardened’ by Arrakis, that they win by default, we’re going to ask are the Fremen actually likely to win in their Jihad? Remember: the books present this not merely as likely but inevitable. Is it likely?

Oh my, no.

The War With the Great Houses

I think we actually want to think through this conflict in two rough phrases. Initially, the Fremen leaving Arrakis are going to be confronted by the traditional militaries of the Great Houses. We’re never told how many Great Houses there are, but it is clearly quite a lot – the institution still very much exists in God Emperor of Dune despite the fact that we’re told 31 Houses Major (the upper-rank of the Great Houses) had collapsed. The implication is that 31 Houses Major do not represent even a majority. Likewise, the entire political system of the Corrino Imperium only works if the Houses of the Landsraad collectively had more military power than the Corrino Sardaukar, such that the emperor had to keep them divided at all times (and such that, acting collectively, groups of them might force concessions from the emperor). Given that Baron Harkonnen thinks just two legions of Sardaukar could easily overwhelm his entire offensive force of ten legions, the implication has to be that there are quite a few Houses Major with military forces on the scale of House Harkonnen.

In short the Fremen are likely to be faced by many dozens of ‘House armies’ ranging from the high tens of thousands to the low hundreds of thousands, probably collectively representing several million trained fighters with shields (I’d guess a few tens of millions, once Houses Minor are accounted for), ‘thopters,’ frigates and all of the other components of ‘modern’ (for the setting) warfare.

The main advantage the Fremen have – and it is a very significant advantage – is that their control over the Spacing Guild (via control over the spice on Arrakis) means that they can face these forces one-by-one, rather than having to face a large coalition of the Landsraad all collected in a single location. The secondary advantage the Fremen have is that the Great Houses are likely to try to meet them with the same rigid, formulaic armies they have long prepared for use against each other: trained fighters using shields engaging in melee combat. They will probably not be, in the first instance, rapid military innovators – they aren’t set up for that.

But the disadvantages the Fremen face are enormous. First and foremost – and this is going to be central – Fremen manpower is fundamentally brittle. On the one hand, the Fremen do not have a civilian class – all of their people are trained fighters, so basically their entire adult population is available for combat. The problem is that means that there is no underlying ‘peasantry’ as it were to refill the ranks of their losses and the harsh conditions of Arrakis – essential to the entire Fremen thing – are not conducive to a ‘baby boom’ either. Fremen losses will thus be functionally permanent: every Fremen Fedaykin lost is lost forever – a long-term reduction in the total Fremen population and thus available Atreides military force. Meanwhile, Hawat estimates the total Fremen population at roughly 10 million. That represents a fundamentally finite resource which cannot really be replenished: it must provide for offensive forces, for casualties, for garrison forces to hold conquered worlds and with enough left over to maintain both the logistics of the Jihad and the basic rhythms of life in the sietches of Arrakis.

The other major problem the Fremen face is that most of their key advantages evaporate once they are off of Arrakis. Indeed, some invert. The Fremen knowledge of local terrain was crucial to their victory on Arrakis but if anything the Fremen are remarkably badly equipped to understand and fight in other terrains. These are men who cannot conceive of a thing called a ‘sea,’ for instance and one supposes they would not fair well in snow or forest either. Urban terrain is also, crucially, mostly foreign to them. Their mastery of stillsuits, of walking with irregular strides in the desert, of concealment in sand, of the use of sandworms all matter exactly not at all off of Arrakis and in most cases will be active hindrances. At best they will have to face the armies of the Imperium in ‘stand up’ fights, at worst they will be repeatedly ambushed.

What is even worse, the Fremen are stepping into a kind of warfare they are unfamiliar with, for which their society was not designed. Remember: Fremen victory on Arrakis depended on most of the technology of industrial warfare not working there. Sandstorms grounded ornithopters and shields were broadly unusable outside of the towns and villages (and disabled by a sandstorm for the final battle). None of that is true the moment the Fremen step off world.

Worse yet the Fremen supply of industrial ‘firepower’ is fundamentally limited. The Fremen themselves are incapable of manufacturing any of this. One of the sleights of hand here is that while the Fremen disable all of the Harkonnen and Corrino frigates at the opening of their battle at Arrakeen – blasting the noses off – these very ships are handwaved back into functionality for the off-screen Jihad. One wonders how the Fremen – who have never seen this technology before, technology which is built nowhere on Arrakis (we’re told the Harkonnen’s equipment is all off-world import, nothing is manufactured locally) – were able to swiftly repair dozens of high-tech spaceships. Equally, the Fremen lack both the ability to manufacture shields or ornithopters, but also lack the knowledge to maintain shields or ornithopters.

While the Spacing Guild can handle interstellar transport, frigates are going to be a huge limiting factor for the Fremen, as they are required to make the descent from orbit to the surface and are armed warships in their own right. In the books, the Fremen have to damage all of the Corrino ships in order to prevent the emperor’s escape, so their fleet is not immediately ready to fly as here.
I suspect any Fremen campaign would suffer from limited frigates – both for transport and presumably for fighting – through the entirety of it.

They have exactly what they captured from the Harkonnen and Corrino troops and nothing else, with almost no means to repair anything that breaks – this is where my earlier point that shields evidently require a lot of maintenance and replacement matters. While the idea of running an army entirely off of captured weapons is a thing often thought of, functionally no one ever actually makes it work: open the hood on armies claiming to run primarily off of captured equipment and you almost invariably find foreign sponsors providing the bulk of their weapons. The Fremen have no such foreign sponsors – or at least, won’t have them the moment it becomes clear they intend to burn down most of the known universe – so their access to military material is going to be limited.

As a result, the Fremen are going to be a remarkably two-tier force: a small body of troops equipped with looted shields and supported by what aircraft can be maintained, with a larger body of Fremen fighting ‘light’ as they did on Arrakis, but without storms or worms or mastery of local terrain.

On the one hand, the Fremen would presumably be able to outnumber the first individual Great Houses they targeted. Great House armies are small, as we’ve noted, so while the Fremen would have an overall numerical disadvantage (the Imperium has more trained fighters than there are Fremen) locally they would have the advantage, created by their control of the Spacing Guild. It would be less overwhelming than you might first think though, for a fairly simple reason: though the spacing guild is compliant, the Fremen only have the space transports they can capture. Note that the Spacing Guild supplies heighliners, not frigates and the Fremen do not know how to build frigates. So their ground-to-orbit and orbit-to-ground capacity is going to be limited. High – the Harkonnen and Corrino fleets captured on the ground at Arrakeen were large – but limited. Still probably enough to give the Fremen local numerical superiority everywhere they went.

The problem would be attrition: Fremen manpower is brittle. This is made worse by the fact that achieving numerical superiority on multiple fronts – and we’re told this fight encompasses a great many worlds (and planets are big things – most of them do not have all of their major settlements packed in one small area like Arrakis does), so they fight on multiple fronts – would require deploying large numbers of those ‘second tier’ Fremen forces. Those Fremen are going to be lethal in close combat, but extremely vulnerable to the industrialized firepower of the setting: one thing we’re told very clearly is that lasguns are evidently extremely powerful against unshielded enemies.

Meanwhile, as capable as the Fremen are, we also know they are not trained how to fight in shields (it is an entire plot-point in Paul’s duel with Jamis that they do not understand Paul’s slower movements), so once forced by military conditions outside of Arrakis to fight shield-against-shield, some part of the Fremen qualitative edge will be lost even for the ‘first tier’ troops.

And simply put, a few million Fremen is probably not enough to actually sustain that campaign, though I will admit it could end up being borderline, depending on the size of Great House armies and the loss-ratios the Fremen are able to put up. Once you have siphoned off the tens if not hundreds of thousands of soldiers required to garrison worlds that have been taken and accounted for losses fighting technologically superior opponents in unfamiliar terrain, I would guess that Fremen manpower would end up badly overstretched.

Very roughly, we can start with 15 million total Fremen. While Fremen women are trained to fight and Chani is on the front lines, we do not see any other women do so: the Fremen do not employ their womenfolk offensively as fighters, as a rule.2 So accounting for women and children – in a society that we may assume has almost no elderly – that 15 million total Fremen might give us 5 million military aged males available for offensive deployment. Some portion of those will still be needed on Arrakis for spice production, administration and so on, but perhaps it is a small portion.

So perhaps 3 million Fremen available for offensive action off world, of which perhaps only a few hundred thousand can be moved at a time given the limited supply of frigates, charging out into a universe with perhaps something on the order of 15 to 30 million trained fighters. That offensive force will be depleted not only by casualties, but also by the demands of holding and administering captured territory and also that army needs to still exist when the fighting is done, both to deter what Great Houses remain and also to enable the continued existence of the Fremen as a people. If Paul conquers the universe but gets a majority of all military-aged Fremen men (over a decade, so more than one full generational cohort) killed, Atreides rule isn’t going to last very long.

Worse yet (it gets worse) the manpower pool the Great Houses operate from is absolutely vast – there are evidently tens if not hundreds of billions of people in the Faufreluches – so any Great House not entirely wiped out is going to be able to reconstitute fairly rapidly. If you do wipe out a Great House but leave the planet, there are no shortage of richece willing to take their place and then reconstitute a Great House army fairly rapidly. The Fremen are going to be playing whack-a-mole quite a bit, because their opponents have enormous demographic reserves to draw on, while by contrast the Fremen’s own are very limited. Of course the Fremen could start recruiting people out of the faufreluches, but that seems both unlikely (the Fremen do not bother to conceal their contempt for the people of the villages of Arrakis, whose conditions are already much harsher than the average worker in the faufeluches) and would also dull the all-important qualitative edge the Fremen need. So while the perhaps 5 million or so total Fremen military-aged-males is a exhaustible, set resource the 15-30 million Great House fighters is a resource which can be almost endlessly replenished.

It is easy to see the ways this could go wrong. First, the Fremen lack of industrial military power could cause the casualty ratio to turn the wrong way once they are off world. Sure, they have the superior close-combat fighters – we’ve stipulated that – but if you lose half of every attack group to lasguns, hunter-drones or other ranged weapons on the way in (because you haven’t enough shields), the Fremen are simply going to run out of Fremen before they subdue the Great Houses. The other path is one where the campaign sputters: the Fremen win initial (costly) victories due to numbers and mobility advantage but are then forced to dissipate much of their force in garrisons and administration. That in turn enforces something that happens to many great conquering peoples: they become like the regimes they replaced. Fremen leaders with their small military retinues settle down to control and exploit the worlds they garrison while being vassals of the Atreides – in short, they become Great Houses, likely losing whatever distinctiveness kept them militarily superior in the process. In either cause, because the numbers are so lopsided, the loss of momentum for the Fremen probably spells collapse as the balance tips back the other way and the Great Houses, with superior manpower and economic resources, begin whittling down what is left.

In short, Fremen victory against the Great Houses strikes me as possible but implausible, it is an unlikely outcome – one that probably would require a prescient warlord directing everything to perfection in order to win. Which as we’ve noted already, is a failure point for the narrative of the books, which require this war to be a thing that succeeds regardless of if Paul lives or dies.

Of course this assumes broadly that the ‘military resources’ – trained fighters, shields, supplies, frigates and so on – in the ‘system’ remains fairly static: that the Great Houses mostly fight as they have always done, with the weapons they’ve always had. One result of that is that the Fremen never get access to the quantity of weapons to fully modernize their own forces – the Great House armies are, ironically, too small to furnish them enough systems to capture.

Of course those limits might not hold. War is, after all, the land of in extremis. The Fremen assault might be enough to really break the static nature of the faufreluches and unlock a lot more economic potential, which might increase the military resources the Fremen could unlock from captured worlds.

That scenario, it turns out, is both likely and much worse.

Fremen: Total War

First, let us start with the part that this seems likely.

So far we’ve been discussing this as a war between the Fremen and the Great Houses, with the much larger mass of the population left out of it. We’ve done that because I think it is the only version of this war the Fremen could win. But it is also clearly, explicitly not the version of the war that happens.

Again, we’re told in Dune Messiah that the Jihad ends up killing 61 billion people, wipes out forty religions, and sterilized ninety planets.

In short, under Muad’Dib’s leadership the Fremen are not merely waging a war against the noble families of the Great Houses, but rather a war against the people of the Imperium. There is something of an irony that Frank Herbert seems to be clearly thinking in terms of something like the rapid expansion of the Rashidun Caliphate (632-661) here, but the Rashidun caliphs quite deliberately avoided this sort of thing, often offering religious protections to the underlying peoples beneath the empires (Roman and Sassanid) they were attacking to avoid a situation where they faced broad popular resistance. That said, this aspect of Islamic conquest was often not emphasized in the 1960s popular understanding, so Frank Herbert may not have been aware of the degree to which local religions and communities were largely and intentionally left in place during early Islamic expansion.

Either way, it seems almost certain that Paul’s Fremen attempting to extirpate entire religious traditions and sterilize entire worlds, are going to start facing broad popular resistance.

We haven’t seen how Villeneuve will tackle this in his adaptation, but Frank Herbert’s Children of Dune (2003) does have this scene at the beginning which includes forced conversions and executions for those who will not convert. Certainly from Paul’s own description of his jihad – with forty religions wiped out – the implication is that this was a war of forced conversion.

Now obviously the first problem here is that it makes their manpower problem much worse. When the Fremen were just facing the Great Houses, they were outnumbered perhaps 5-to-1, which is quite bad but in the fiction of the setting superior skills can overcome those disadvantages at least some of the time.3 But against a, say, Earth-like planet – of which there must be very many, given that killing 61 billion people did not even cause much of a social collapse in the Imperium – the Fremen might face mass-mobilized armies on just that planet in the high tens of millions. The USSR mobilized an astounding 34.5 million troops during WWII out of a population (pre-war) of about 200 million. Naturally it would be hard to mobilize a whole planet on that basis, but doing so on a modern-Earth-like world would net you around one billion soldiers.

So the idea that the Fremen might find themselves landing forces of, say, 300,000 Fremen warriors (representing basically the maximum carrying capacity of the Corrino and partial-Harkonnen fleets they captured) on a planet only to find themselves facing an opposing force five million or fifty million or five hundred million foes is not out of the question. One of the few ways to force that kind of mobilization from modern societies is to attempt to genocide a population or extirpate their long and sincerely held religion and the Fremen are trying to do both.

Now the Great Houses can control these populations because they maintain local legitimacy, because shield-based fighting gives them a huge advantage against populations that cannot afford shields and because they have demilitarized the lower classes. But the Fremen will have removed all of these factors. The Fremen do not have long-standing local legitimacy – they are a barbarian foreign force trying to take away your religion. They also do not have a shield-based fighting system and lack enough shields to fully equip their force in any case and so take to the field without a technological edge over a mass-mobilizated populace. And worse yet, the very threat they pose is going to push the lower classes to militarize.

Now in pre-industrial societies, this effect was somewhat limited because pre-industrial societies were not capable of fully militarizing their lower classes. But the societies of Dune are post-industrial societies. It may be impossible to provide the high tech instruments of warfare to an entire mass army – not enough shields, ‘thopters and frigates – but it would be trivially easy for these societies to equip the great masses of their population with spears, swords and simple guns.

Ironically, the Fremen would now find themselves immediately caught in the same trap as the Great Houses: trained in a fighting style that emphasizes close combat, they would try to have close-combat mass-battles with huge, unshielded armies of melee combatants, rather than being set up to use their shields to maximum advantage by conducting the fighting at long range.

Facing even relatively modest mass armies would require the Fremen to deploy a lot of their available manpower simply to be able to hold ground on the kind of scale these wars would be fought on, which would make the two-tier structure of their army even more of a liability because it would force them to field those second-tier troops in quantity. And while a Great House might be dumb enough to fight those second-tier unshielded troops in close combat – that being their habit – one imagines a mass army of resistance might approach it differently. After all a mass army is going to look for cheap ways to arm hundreds of thousands or millions of fighters and guns and artillery are relatively cheap compared to shields and ‘thopters. And we know that the basic technology of artillery is not lost, because Vladimir Harkonnen uses it as a surprise tactic against the Atreides.

Heaven help the Fremen if some planet somewhere stumbles on the same idea and expands it out to a fifty-million-soldier army against a largely unshielded, close-combat-based infantry Fremen force. Ask the survivors of the Battle of Omdurman (1898) what happens when the most skilled, motivated, desert-hardened and determined ‘hard men’ attempt to charge machine guns with contact weapons. While the ‘first tier’ Fremen troops with captured shields might still be effective, after their ‘second tier’ supporting units were obliterated they would be horribly outnumbered, easy enough to simply mob down with bayonets.

Even if the Fremen qualitative edge remained intact – perhaps because their opponents continued to operate in the contact-warfare frame rather than rediscovering projectile weapons – the attritional structure of the conflict would become unsustainable pretty quickly. Paul could easily lose half of his entire offensive force fighting a single partially mobilized world of this sort with a 15:1 casualty ratio in his favor.

But there’s an even worse outcome here for the Fremen, especially given the length of the conflict: total economic mobilization. So far we’ve considered worlds with perhaps days or weeks of warning doing panic mobilization while under attack, churning out as many rifles and swords as they can to put together mass armies, relying on the fact that planets are very big and so any conquest would take months if not years.

Paul’s Jihad lasts twelve years, canonically. For a sense of what twelve years is in ‘mobilization time,’ the United States went from producing almost no tanks in 1939, to just 400 in 1940, to 4,052 in 1941 to 24,997 in 1942, to 29,497 in 1943. In 1939, the United States built 5,856 aircraft; by 1944, it was building more than 8,000 aircraft a month.[efn_notes]Statistics via Overy, Why the Allies Won (1995), 331-2.[/efn_note] Again, as we’ve already noted, the only way the small armies of the Imperium make sense with its attested population (which must be more than the 61 billion Paul kills) is if this society is mostly demilitarized. We see plenty of industrial capability – aircraft, space-ships and so on – it is just that these noble houses with their limited administration cannot mobilize that capacity for war.4 The technology and population exists, what is lacking is the administrative capacity and political will to employ it. And while we might imagine that Dune‘s frigates and ornithopters are more complex machines than WWII-era aircraft, tanks and warships, it is equally the case that we’re thinking about the economies of entire planets rather than individual countries.

But for a planet that found itself not immediately under attack but very obviously in the path of Paul’s Jihad – perhaps with a well-entrenched local religion – that calculus is different. Information might spread slowly in the Imperium, but not infinitely slow – at least the elite do seem to have some sense of affairs in distant places. Those richece, perhaps with their nobles or without them, might well opt to do what those noble houses with their tiny, underdeveloped administrations could not: mass mobilize not just people but industry, unlocking the productive capacity of several billion people and turning much of the civilian economy over to a war-footing in a way that the Great Houses, with their small administrations and very limited legitimacy never could. Show the people film-strips of Paul Muad’Dib’s army murdering billions and sterilizing worlds and say, “that is coming here unless you line up to work in the factory churning out ninety thousand ornithopters a year.” Big posters that say, “to keep the Fremen Fedaykin murderers away from Our Holy Sites, we need YOU to hit our target of launching two thousand heavy weapons frigates this year!” Industrial societies engaged in something approach total economic mobilization can produce enormous amounts of destruction very rapidly.

The Fremen Jihad lasts more than long enough for the more populous worlds of the Imperium to adopt this kind of war economy in preparation and the tremendous violence that the Fremen inflict – again, sixty-one billion casualties – are more than enough to motivate a lot of these worlds to do exactly that.

Paul will, in that event, at least be lucky that the Spacing Guild might let him isolate such worlds, although if you are the Spacing Guild (or an anti-Fremen group of smugglers) you might just be willing to roll the dice to see how Paul’s base of power on Arrakis handles the arrival of thousands of frigates with tens of thousands of ‘thopters carrying millions of heavily equipped troops showing up in the skies above Arrakeen.

The Failed Jihad

Now of course the natural response to all of this is that Paul Muad’Dib Atreides can avoid all of these outcomes because he is the Kwisatz Haderach, able to see the present and the future and thus able to anticipate and avoid all of these outcomes, threading the needle of probability perfectly to guide the Jihad to its victorious conclusion.5 And of course we’ve already noted the flaw in this: Dune is explicit that by the time Paul fully grasps his prescience, it is too late to stop the Jihad, which would happen and succeed even if he was dead. Paul is merely the catalyst for what Herbert imagines as historical – nearly ecological – merely the manifestation of the ‘world-spirit’ of the age moving through history. The Jihad would happen without him. Only the catalyst is required; the rest is inevitable.

And it just clearly isn’t. There are, in fact, quite a lot of ways the Jihad could swiftly fail.

And fundamentally that goes to how Frank Herbert’s vision of military power – one shared by quite a lot of people – differs from how military power is actually generated. In Frank Herbert’s vision, military power is a product of the individual capabilities of fighters, which in turn is produced ecologically based on the harshness of the environment they come from. He imagines huge gulfs in capability, where two legions of Sardaukar can easily overpower ten legions of Harkonnen and Fremen in the desert can inflict even more lopsided casualties on Sardaukar.6 There is a direct correlation then between the harshness of a place and the military power it can produce.

And equally, there is a strongly gendered component of this view in Frank Herbert’s writing: militarily effective societies in Dune are masculine in key ways.7 Harsh conditions, for Herbert, produce intensely masculine societies (whereas the decadence of the Imperium is signaled in equally gendered terms: the gay sexual deviant Baron, the genetic eunuch Fenring, the emperor with his household of daughters and his failure of “father-head”-ship), which in turn produce militarily effective ones.

It is not hard to see how intense and pervasive a view of military power that is, how frequently in popular culture ‘manliness’ is presented as the primary source from which military effective flows. This isn’t the place to get into the modern manifestations of this sort of ideological framework, but it is not particularly hard to find recruiting and propaganda videos that attempt to communicate military effectiveness almost purely through gendered visual language of masculine fitness prowess, as if victory belongs to the army that can do the most push-ups. Herbert’s vision is somewhat more sophisticated than this, but only somewhat. It is water drawn from the same well.

And that simply isn’t how military power is actually generated in the real world. Training certainly matters and there are some kinds of fighting – like horseback archery – that almost have to be deeply socially rooted to be effectively trained. Cohesion also certainly matters, but it can be generated quite a few ways and strong cohesion is certainly possible to produce ‘synthetically’ through training and drill. But the strongest armies do not generally come from the harshest places – indeed, the opposite: for most of human history the military advantage has gone to resource-rich places with dense populations. This is obscured somewhat in popular culture because the exceptions to this rule are so striking but they’re striking because they are exceptions.

But especially after the industrial revolution – and Dune is a post-industrial (very post-industrial) universe – military power is largely generated by economies, a brute-force product of the ability of societies to deploy the most men (supported by their agriculture), the most metal, the most explosives and these days the most electronics. Weaker powers can still win by protracting conflicts and focusing on degrading the will of an enemy, but they do this because they are weaker powers who understand that they do not have much of any chance of winning in a direct confrontation. Indeed, the armies that have put the most emphasis on the ‘fighting spirit’ or individual physical superiority of their soldiers have tended to lose modern wars to armies of conscripted farm-boys and shop-keepers backed up by tremendous amounts of modern industrial firepower.

Of course, as Clausewitz reminds us (drink!) war is the realm of the “play of probability and chance” – a contest in which the stronger does not always win. Military strength may be, in modern times, almost entirely the product of industries, economies and demographics (and the first two more than the last one in most cases), but such raw strength is not the only thing that determines the outcome of wars, which equally depend on the strategic importance of the objective, the political will of the two parties and the vagaries of chance that are omnipresent in war (drink again if you got the reference).

None of this makes Dune a bad book or Frank Herbert a bad author – it is a fascinating book that raises these kinds of ideas and questions. But equally precisely because the book’s understanding of where military power comes from derives not from historical facts but from fictional events, it is worth thinking hard about how it imagines this works and if that actually corresponds to historical trends.

In this case, Frank Herbert imagines that ‘historical forces’ have created an effective inevitability that once roused the Fremen, on account of their harsher society, would storm the universe basically regardless of the balance of logistics, military equipment or numbers because the vague ‘hardness’ of their society makes them unbeatable. It makes for a fascinating narrative, but this is not how history works and indeed the wastelands of history are littered with the half-remembered names of a great many peoples who were ‘hard’ and ‘tough’ and ‘aggressive’ and utterly slaughtered or overrun because the ‘wealthy’ ‘decadent’ and ‘unmanly’ societies they fought also had greater numbers and superior weapons.

So to answer the original question: no, one way or another, the Fremen would fail, though they might fail in the most interesting way – failing not by replacing the faufreluches, but by galvanizing them into producing (or reproducing) a different kind of self-governing society that was far better able to mobilize itself and its resources – and capable of far more destructive, horrifying forms of war.

One wonders what the Dune universe’s version – after the collapse of both the faufreluches and the Fremen – of the First World War, a horror-show of industrial warfare on unprecedented scale – would look like.

[syndicated profile] jwz_blog_feed

Posted by jwz

There are a lot of things to be angry about in the world today, but Ticketmaster is always one of them. Spare them a little rage if you have any left to give. When, two years ago, we heard that DOJ was moving forward with their anti-trust suit against Live Nation we all knew it was too good to be true, and, yup, it was too good to be true. The DOJ folded with not even a slap on the wrist.

And because of that, it seems that a number of state attorneys general are considering folding as well. Here's a form from NIVA to help you send your state's attorney general to keep fighting.

Bipartisan group of states refuse to sign settlement between Justice Department and Live Nation:

New York, Arizona, California, Colorado, Connecticut, Illinois, Ohio and Kansas are just a few of the states continuing the lawsuit.

"The settlement recently announced with the U.S. Department of Justice fails to address the monopoly at the center of this case, and would benefit Live Nation at the expense of consumers. We cannot agree to it," New York Attorney General Letitia James said in a statement.

The Justice Department and some 40 attorneys general first launched the lawsuit against Live Nation in 2024 under the Biden administration, alleging the concert giant had built an illegal monopoly over live events by controlling ticketing, venues and artist promotion. In effect, they argued, Live Nation had pushed out competitors and locked venues into exclusive arrangements that harmed both artists and fans.

At least the suit gave us some popcorn:

Live Nation Employees Boast About Gouging Fans With Fees:

Baker, who oversees ticketing for Live Nation's venue nation unit, called some increased prices "fucking outrageous," with Weinhold replying that "I have VIP parking up to $250 lol."

"I almost feel bad taking advantage of them," Baker replied.

In another exchange, Baker shared a screenshot of premier parking costs, further stating "robbing them, blind, baby, that's how we do." Later in the exchange, Baker said, "I gouge them on ancil prices to make up for it," referring to extra ancillary fees on more standard tickets.

Satire, but who can tell:

Live Nation restricts ticket buying and selling exclusively to bots:

"Our platform optimizes for multiple devices logged in at once and spamming the queue," notes Live Nation CEO Michael Rapino. "Once ticket sales are live, that's when the bots buy up the max tickets per person until they are all sold out in under 1 minute, though our software engineers are trying to get that down to 30 seconds."

Rapino adds, "Yes artists send out codes and have fan presales, but we always ensure that all of the bots get those too, since it'd be really unfair if these hardworking robots had to wait until general sale day." [...]

The announcement has been met with widespread support from StubHub, Viagogo, and a series of shell companies that, when contacted for comment, all responded within 0.003 seconds with identical statements saying they were "just regular fans."

The list of Live Nation's sins will not be news to anyone who has been following this blog for any length of time:

In Every Language

2026-03-13 16:40
[syndicated profile] waxy_links_feed

Posted by Andy Baio

compare the key images used to illustrate a topic in 300+ different language Wikipedia editions around the world #

miscellany

2026-03-13 22:48
kaberett: Trans symbol with Swiss Army knife tools at other positions around the central circle. (Default)
[personal profile] kaberett

In apparent celebration of Migraine World Summit, I have spent this evening having an unscheduled migraine attack for no obvious reason. I disapprove. (Because I've been doing a lot of audiovisual processing, captions notwithstanding? Because I had my screen much brighter than usual for a while playing a colours game?* Because oven't?)

Nonetheless I have watched and made digital notes on all of 2026 Day 2, watched and made digital notes on 3/4 talks from 2025 Day 2 (which I missed at the time), and made physical notes for 2025 Day 1 and 1/4 of Day 2. I am... sort of catching up.

I am really enjoying my pens. I also find myself with the problem of wanting lots of different notebooks and, also, to keep everything in One Single Solitary Notebook, For Convenience...

* NB I am a rocks nerd. My colour discrimination is ludicrously good. I am sorry that that link is weird and competitive about my ridiculous score, but not sorry enough to provide you with the bare link.

Conditional Impls

2026-03-13 10:28
[syndicated profile] possible_rust_feed

Posted by alilleybrinker

It’s possible in Rust to conditionally implement methods and traits based on the traits implemented by a type’s own type parameters. While this is used extensively in Rust’s standard library, it’s not necessarily obvious that this is possible. In this article I’ll break down what the pattern is, give some examples of its use in the standard library to show why it’s valuable, and explain when you might want to use it.
[syndicated profile] rust_feed

Posted by Ed Page

We would welcome people to try and report issues with the nightly-only cargo -Zbuild-dir-new-layout. While the layout of the build dir is internal-only, many projects need to rely on the unspecified details due to missing features within Cargo. While we've performed a crater run, that won't cover everything and we need help identifying tools and process that rely on the details, reporting issues to these projects so they can update to the new layout or support them both.

How to test this?

With at least nightly 2026-03-10, run your tests, release processes, and anything else that may touch build-dir/target-dir with the -Zbuild-dir-new-layout flag.

For example:

$ cargo test -Zbuild-dir-new-layout

Note: if you see failures, the problem may not be isolated to just -Zbuild-dir-new-layout. With Cargo 1.91, users can separate where to store intermediate build artifacts (build-dir) and final artifacts (still in target-dir). You can verify this by running with only CARGO_BUILD_BUILD_DIR=build set. We are evaluating changing the default for build-dir in #16147.

Outcomes may include:

Known failure modes:

  • Inferring a [[bin]]s path from a [[test]]s path:
  • Build scripts looking up target-dir from their binary or OUT_DIR: see Issue #13663
    • Update current workarounds to support the new layout
  • Looking up user-requested artifacts from rustc, see Issue #13672
    • Update current workarounds to support the new layout

Library support status as of publish time:

What is not changing?

The layout of final artifacts within target dir.

Nesting of build artifacts under the profile and the target tuple, if specified.

What is changing?

We are switching from organizing by content type to scoping the content by the package name and a hash of the build unit and its inputs.

Here is an example of the current layout, assuming you have a package named lib and a package named bin, and both have a build script:

build-dir/
├── CACHEDIR.TAG
└── debug/
    ├── .cargo-lock                       # file lock protecting access to this location
    ├── .fingerprint/                     # build cache tracking
    │   ├── bin-[BUILD_SCRIPT_RUN_HASH]/*
    │   ├── bin-[BUILD_SCRIPT_BIN_HASH]/*
    │   ├── bin-[HASH]/*
    │   ├── lib-[BUILD_SCRIPT_RUN_HASH]/*
    │   ├── lib-[BUILD_SCRIPT_BIN_HASH]/*
    │   └── lib-[HASH]/*
    ├── build/
    │    ├── bin-[BIN_HASH]/*             # build script binary
    │    ├── bin-[RUN_HASH]/out/          # build script run OUT_DIR
    │    ├── bin-[RUN_HASH]/*             # build script run cache
    │    ├── lib-[BIN_HASH]/*             # build script binary
    │    ├── lib-[RUN_HASH]/out/          # build script run OUT_DIR
    │    └── lib-[RUN_HASH]/*             # build script run cache
    ├── deps/
    │   ├── bin-[HASH]*                   # binary and debug information
    │   ├── lib-[HASH]*                   # library and debug information
    │   └── liblib-[HASH]*                # library and debug information
    ├── examples/                         # unused in this case
    └── incremental/...                   # managed by rustc

The proposed layout:

build-dir/
├── CACHEDIR.TAG
└── debug/
    ├── .cargo-lock                       # file lock protecting access to this location
    ├── build/
    │   ├── bin/                          # package name
    │   │   ├── [BUILD_SCRIPT_BIN_HASH]/
    │   │   │   ├── fingerprint/*         # build cache tracking
    │   │   │   └── out/*                 # build script binary
    │   │   ├── [BUILD_SCRIPT_RUN_HASH]/
    │   │   │   ├── fingerprint/*         # build cache tracking
    │   │   │   ├── out/*                 # build script run OUT_DIR
    │   │   │   └── run/*                 # build script run cache
    │   │   └── [HASH]/
    │   │       ├── fingerprint/*         # build cache tracking
    │   │       └── out/*                 # binary and debug information
    │   └── lib/                          # package name
    │       ├── [BUILD_SCRIPT_BIN_HASH]/
    │       │   ├── fingerprint/*         # build cache tracking
    │       │   └── out/*                 # build script binary
    │       ├── [BUILD_SCRIPT_RUN_HASH]/
    │       │   ├── fingerprint/*         # build cache tracking
    │       │   ├── out/*                 # build script run OUT_DIR
    │       │   └── run/*                 # build script run cache
    │       └── [HASH]/
    │           ├── fingerprint/*         # build cache tracking
    │           └── out/*                 # library and debug information
    └── incremental/...                   # managed by rustc

For more information on these Cargo internals, see the mod layout documentation.

Why is this being done?

ranger-ross has worked tirelessly on this as a stepping stone to cross-workspace caching which will be easier when we can track each cacheable unit in a self-contained directory.

This also unblocks work on:

Along the way, we found this helps with:

While the Cargo team does not officially endorse sharing a build-dir across workspaces, that last item should reduce the chance of encountering problems for those who choose to.

Future work

We will use the experience of this layout change to help guide how and when to perform any future layout changes, including:

  • Efforts to reduce path lengths to reduce risks for errors for developers on Windows
  • Experimenting with moving artifacts out of the --profile and --target directories, allowing sharing of more artifacts where possible

In addition to narrowing scope, we did not do all of the layout changes now because some are blocked on the lock change which is blocked on this layout change.

We would also like to work to decouple projects from the unspecified details of build-dir.

[syndicated profile] nwhyte_atom_feed

Posted by fromtheheartofeurope

Second paragraph of third essay (“Ersatz Wines”):

To be a writer is in fact a fairly common ambition – in a recent survey by YouGov, sixty per cent of British adults said that they wanted to become an author, and not as a casual dream but as a wish for a career. An equivalent survey in the United States revealed an even higher rating: eighty-one per cent of adults questioned felt they had a book in them, and that they should or would write it. In the USA there are approximately one-and-a-half million people who run or conduct courses in creative writing, providing tuition for more than twenty million students. The success of book groups and writers’ circles also underlines what a persistent aspiration authorship is for many people. Most of them will inevitably not achieve the dream, although in these days of internet publishing and print-on-demand, many more will do so than would have been able to in the past.

This is a book of non-fiction essays by the late great Christopher Priest, mostly (but not only) about the craft of science fiction and writing, with some autobiography thrown in. The publishers kindly sent me an advance copy in the expectation that I would review it here – normally I reject such requests (I get half a dozen or so every year), but in this case I was more than happy to oblige.

There are 16 pieces in 300-plus pages here, but they vary wildly in length. The longest single piece, a reflection on Christopher Nolan’s film adaptation of his novel The Prestige, is almost a hundred pages. The shortest, about his life in a flat in Harrow from 1969 to 1985, is only four pages long.

Most readers will hope to get insights about Priest’s own career from this collection, and they will not be disappointed. The early autbiographical pieces are fascinating and add to the work of Paul Kincaid. The very first piece, about an unrequited teenage love, is especially moving; it was apparently the last to be written. He writes a lot about other people’s writing, but he also writes a lot about his own, disarmingly frank about the limitations of his analysis.

I don’t know how to write a book. I don’t even know how to write one of my own books.

The key to his own thinking about sf is probably best expressed in “‘It’ Came From Outer Space: The World of Science Fiction 1926-1976 by Lester Del Rey”, which brutally dissects Del Rey’s choices and commentary in a now forgotten anthology (56 ratings on Goodreads, which is close to nothing for a book almost 50 years old). Priest always wanted science fiction to be ambitious and outward-looking; he writes of Del Rey’s

major fallacy… that the creation of the genre magazines by Hugo Gernsback and his imitators in the 1920s and ’30s was a good thing.

He pushes back against narrow interpretations of the genre in several of the other pieces too (most notably in his 2000 Novacon Guest of honour speech) but this is its crispest expression.

He’s very funny about his own early career, though his remarks about Michael Moorcock are pretty salty, to the extent that Nina Allan notes in the foreword that the two of them reconciled at the end. At his very first science fiction convention, he is upstaged by Terry Pratchett:

To my not entirely impartial eyes, Terry seemed to be getting a disproportionate amount of recognition for a single short story, “The Hades Business”, which had appeared in an anthology, having first been published in his school magazine. Terry was then only fifteen years old; he was short and slight, had a mass of bushy dark hair, and spoke in a rather distinctive treble. I, with my writing light hidden under a bushel, could hardly complain that he was getting more attention as a promising young writer than I was, but even so I felt annoyed with him. I privately resolved to outdo him one day, but never in fact did so …

I wrote last year about Priest’s relationship with Doctor Who. One surprise here was a personal reminiscence of Ian Marter, who played Harry Sullivan, and was a neighbour in the Harrow years:

Marter, whom I found pleasant but distinctly odd, once advised me to wax my car because he said it would help strengthen it in the event of a head-on collision (or, presumably, a tree branch falling on it).

The long piece about the filming of The Prestige is interesting even for those (like me) who have not actually seen the film. Although Priest claimed to be fully stiff-upper-lip about it, he was clearly very emotionally invested in his own story and in what was done to it, and the reader will cheer on his behalf when he is generally pleased (to put it mildly) with the result.

It’s (almost) all worth reading. My one reservation is a 2002 piece supporting the conspiracy theory that Rudolf Hess was secretly replaced by a double. Perhaps it’s useful as an illustration of Priest’s interest in doubles and hidden histories, but I think an editorial note should have been added to say that the duplicate Hess theory, improbable in the first place, was conclusively disproved by DNA testing in 2019. Priest also had odd ideas about 9/11, but luckily doesn’t seem to have committed them to writing, or at least not to writing printed here.

But we’re on much more solid ground with the final piece, his Guest of honour speech from the 2005 Worldcon in Glasgow, where he again restated his theory of the genre:

Long ago, I realised that whenever someone says “Science fiction IS”, or “Science fiction SHOULD BE”, I immediately start thinking of exceptions to that rule. Those exceptions are almost invariably stuff I like precisely because it can’t be pinned down. What we call science fiction as a kind of unified lump should consist of a literature of unexpected ideas, found in individual works, written by individual writers in individual ways. The rest is hackwork.

Even those who don’t know Priest’s work will probably enjoy the insights into the creative process that he gives here. For those of us who did know the man and his writing, it’s an essential volume. You can get The Recollections here (starting next month).

March 2026

S M T W T F S
1234567
8910111213 14
15161718192021
22232425262728
293031    

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated 2026-03-15 09:33
Powered by Dreamwidth Studios