Urgent.News

What's breaking now, across thousands of outlets.

Tech

‘Dune: Part Three’ Cowriter Brian K. Vaughan Has a New Comic on the Way

Brian K. Vaughan claims he’s seen Dune: Part Three and it’s “a fucking beautiful movie.”

‘Dune: Part Three’ Cowriter Brian K. Vaughan Has a New Comic on the Way

Brian K. Vaughan, the co-writer of Dune: Part Three, has revealed that he is working on a new comic called Roam, set to release in February of the following year. Roam is a superhero sci-fi series, a departure from Vaughan's previous work, which includes Saga, Y: The Last Man, and Runaways. This new project was born out of a desire to collaborate with Cliff Chiang again, following their successful partnership on Paper Girls, which was adapted into a 2022 Amazon Prime Video series.

Vaughan expressed excitement about Roam, stating that it is "completely unlike anything I've ever done" and that it is "certainly my first true superhero book."

As for his concerns regarding AI's impact on the industry, Vaughan expressed fear and uncertainty. He mentioned that jobs of previsualization and storyboard artists are at risk, and he fears that the future may bring content over bespoke human-made stories. Vaughan also noted his reluctance to write adaptations of his own comics, citing the process as "violence to" his work. Despite this, he remains focused on creating new content, as he believes that there is still a market for human-made stories.

Written by urgent.news from Wired's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at wired.com →

More in Tech

n8n: Get Alerted When an Automation Fails, Before a Client Notices

A silent failure costs more than an error. Say your n8n workflow pulls prices from a sheet every morning, and one run fails on a Monday.

  • Enable "Retry On Fail" on problematic steps to resolve temporary errors.
  • Create an "Error Trigger" workflow to alert on failed automation.
  • Link the error workflow to important workflows as the alert source.

Batch .bat in 2026: Legacy Glue, Not a Personality

I still write .bat files in 2026. I also refuse to build an identity around them. That distinction— legacy glue vs personality —is the retrospective I wish someone had handed me earlier.

  • Author still writes .bat files in 2026 for Windows environments.
  • Batch scripting limited to nontrivial logic and not ideal for team-shared automation.
  • Recommend rewriting complex .bat files in PowerShell, using thin wrappers temporarily.

More from Wednesday 14 October →