An anonymous reader quotes a report from TorrentFreak: A Vietnamese court has sentenced 14 people who worked on the pirate football streaming site Bun Cha TV, handing out the first prison terms we've seen since the country's piracy crackdown began earlier this year. [...] Four defendants, including the heads of the content, programming and operations teams, were sentenced to 12 months in prison. Five others received ten months, and two were sentenced to eight months. Notably, three of the site's commentators were not sent to prison. Their ten-month sentences were suspended. All 14 defendants reportedly admitted the charges and cooperated with the authorities. According to investigators, Bun Cha TV streamed more than 150,000 sports matches and it allegedly made more than 20 billion dong, roughly $760,000, in illegal profits from betting and gambling ads.

The verdict reports don't mention a total. Instead, they list illegal gains per person or team. The leader of the content team allegedly gained more than 430 million dong, while commentators made from more than 31 million to more than 480 million dong each. The verdict was picked up by Rouse, the law firm that represents the Motion Picture Association in Vietnam. In an article headlined "Strong Vietnam criminal penalties," published on Lexology on November 3, the firm calls the ruling another victory for Vietnam's IP landscape.

"The defendants were all sentenced to terms of 8-12 months in prison," Rouse writes. While Rouse is correct on the length of the terms, it doesn't mention that three of the sentences were suspended. Instead, Rouse stresses that the ruling is part of a tougher enforcement trend. "This ruling reflects a shift in enforcement strategy by Vietnamese authorities, who are increasingly moving past preliminary domain blocking to deliver criminal convictions against the operators of commercial-scale piracy rings," the firm notes. "This perhaps reflects the strength of the national crackdown following the USTR pressure in May," the firm adds. According to the indictment, Bui Ba Hien, who runs a company called S24, allegedly directed employees and collaborators to build and operate Bun Cha TV. However, Hien is not among the 14 defendants named in reports, which also do not identify the affected rightsholders.

"Interestingly, in September, Bac Ninh police issued a wanted notice for a man of the same name, Bui Ba Hien, CEO of esports company Box Vietnam," reports TorrentFreak. "This person is also charged under the same copyright statute."

An anonymous reader quotes a report from VentureBeat: Researchers from the Massachusetts Institute of Technology (MIT) Computer Science & Artificial Intelligence Laboratory (CSAIL) reported today that they used OpenAI's GPT-6 Astra language model to raise a small, open source Qwen model's math score roughly sixfold by directly editing its weights -- the numerical parameters that govern its behavior. Rikiya Takehi, Jayden Teoh, Alex Zhang and Omar Khattab described their work in a research blog post published November 2. They call the approach "weight-space programming" and tested Astra's ability to interpret and alter networks without using conventional training procedures to generate the edits.

In the strongest language-model example, Astra's intervention raised Qwen3.5-0.8B's MATH-500 score from 7.9% to 48.1% while touching approximately 0.016% of its weights. The improvement came primarily from correcting repetitive reasoning—a distinction that shaped both the technical findings and the debate over their implications. Their experiments explored a broader possibility: AI systems that inspect, repair and construct other neural networks by working directly on their internal machinery. "This is cool as heck!" wrote Yuchen Jin, a technical staffer at Databricks and former co-founder and CTO of Hyperbolic Labs who was unaffiliated with the research, on X. "Imagine using a large LLM to directly edit a smaller model's weights and dramatically improve its capabilities. It's like gene editing for neural networks. Even cooler than distillation!"

Voyage AI staff researcher Chandan Singh, formerly of Microsoft AI, also reacted to the findings: "For anyone questioning whether this post is overhyped, I think they are actually *underselling* the approach."

According to 404 Media, Proton CEO Andy Yen is aggressively pushing AI adoption while fostering what workers describe as a culture of fear that discourages raising security concerns or challenging leadership. The investigation is based on interviews with eight current and one former Proton employees, as well as internal Slack chats, meeting recordings, and an AI manifesto written by the company's CTO. Longtime Slashdot reader devnulljapan summarizes the findings: Engineers at Proton, which makes the encrypted email service Proton Mail and a suite of privacy- and security-focused products, including an encrypted drive service, an authenticator app, and a password manager, are being pushed to "stop lovingly handcrafting all our code and use AI more." Workers describe an environment where employees have genuine concerns about security or being asked to develop security products with AI but feel unable to voice them, lest Yen berates them in front of everyone or threatens their employment at the company. "The CEO is in full AI psychosis and has been for a while now," one of the sources told 404 Media. Yen reportedly dismissed an employee's request for additional security testing before releasing new code, calling it "bullshit and loser thinking" and insisting that "only losers think like that." In a separate exchange over Proton's post-quantum encryption rollout, Yen criticized how the company communicated the feature's limitations and told employees that "perception is more important than truth, the truth doesn't matter if you don't win on perception."

"The train is coming, get onboard or get crushed. Don't be the professional fax machine operator in the internet age," Yen wrote to the security Slack channel. "I think by the end of this year most developers stop programming and start writing specs for tests that AI will code and run, to validate AI written code that humans will no longer be able to review. This will be the last year that we hire engineers, and starting next year we hire what we used to call product managers, to build things with AI."

An Anthropic engineering manager says he has stopped using traditional coding interviews because AI can now outperform candidates on the kinds of programming challenges they typically contain. "There's no more point in giving you a little React challenge than there is in quizzing people about assembly; Claude is now better at both," said Felix Rieseberg in a blog post. "Our most impactful builders are successful regardless of how good they are at these tests." The Register reports: "I don't think the coding interview is going to come back," said Rieseberg. "It's easy to get sentimental given how many copies of 'Algorithms and Data Structures' were bought in hopes of unlocking good jobs and a better future -- or how the death of the coding interview is another milestone in software engineering reaching a new level of abstraction."

At the same time, he's not certain what will replace it. "I'm probably not the only manager trying to figure out how to interview for people who build well with AI," Rieseberg wrote. "I haven't quite gotten there yet -- but I'm scanning resumes and portfolios for little prototypes that exhibit taste, empathy, and principled thinking. If you have figured out something better, I'd love to hear how." In a response posted to social media, Jaana Dogan, principal engineer at Google, said: "I'm not doing a ton of coding interviews nowadays but I'd be interested to interview how people use coding agents," she wrote. "That itself gives me more signals about candidates' coding skills."

"We are not seeing tech companies abandon skills assessments widely across the industry -- at least not yet," added Nicole Bachaud, labor economist at ZipRecruiter. "In fact, based on our October 2026 Employer Survey of 1,500 employers, we see the tech industry (Information sector specifically) is actually the most likely to test for skills, with 62.5 percent of employers requiring formal skill tests on initial applications."

"The change at Anthropic might be reflecting a shift away from technical skills towards more human, soft skills," said Bachaud. "As AI becomes fully capable of writing code, tech employers may be pivoting away from rote technical testing and heavily toward human-centric soft skills." She argues that while AI may be able to code well, it can't replace critical thinking. "A staggering 61.5 percent of Information employers now report that 'critical thinking' is a primary skill lacking in today's candidate pool," she said.

"EMACS, the mother of all editors, turns 50!" writes Slashdot reader dr_jerry, sharing a report from MIT Technology Review: Programming used to be a very different experience from the one we know today. In fact, the first programmers didn't write code at all; the six women who worked on the ENIAC, one of the world's first computers, at the University of Pennsylvania in 1946 did it by physically configuring switches, cables, and plugboards.

A few years later, MIT engineers programmed the Whirlwind by punching code onto paper tape that was then loaded into the computer's memory -- making it among the first "stored-program" machines. Later, they and others moved on to punch cards, one for each line of code.

By the early 1960s, programmers with interactive computers could use a "line editor" to type their code on teletypes -- large, noisy keyboard-and-printer machines. They'd type one line of code at a time, and their work would be saved on a spinning hard disk the size of a modern washing machine. But there was still no such thing as the now-familiar full-screen text editors that allow programmers to see and modify many lines at a time on a display.

One of the first such tools, EMACS, turns 50 this year, and it is still widely used. EMACS first ran on the early video terminals at the MIT Artificial Intelligence Laboratory in 1976, but its core concepts were so powerful that it was rewritten for many operating systems in the decades that followed. Apple even distributed it with Mac OS X. Beyond that, the software-sharing community that started around EMACS helped give rise to the modern-day free software movement and the GNU/Linux operating system.

"As of today in systemd Git it's now possible for the systemd programs to be written in the Rust programming language as an alternative to C," reports Phoronix: Core systemd code like the systemd library doesn't yet support Rust code, but for the various systemd programs / leaf components there is now support for using Rust... The new systemd-keyring-setup utility in Rust is used for provisioning keyrings and enrolling X.509 certificates into the kernel's dm-verity / fs-verity / BPF keyrings during the boot process while dealing them afterward. This systemd-keyring-setup code hasn't been merged yet but is expected soon now that the Rust infrastructure has landed. Originally it was all part of a single big commit before being split-up for the Rust enablement, systemd-keyring-setup, and other preparations for this new component.

Systemd developers aren't planning on porting existing C code to Rust, all the Rust code is built with Meson [no Cargo usage], and C linkage only is mandated.

Systemd Rust components come out slightly larger than C with a test program being 32KB compared to 20KB for its C twin. For now at least the systemd Rust support is optional and toggled by the -Drust= Meson option with it being auto by default.

Cloudflare reported millions of attempts to exploit two serious PHP flaws this week. The PHP foundation has "no evidence hackers were able to exploit the vulnerabilities before they were disclosed," reports Reuters, but the incident still shows how critical the three-decade-old programming language is.

"Yet the nonprofit foundation that supports PHP, which may underpin up to 70% of sites globally, operates on a shoestring budget." "We have one full-time staff member (that's me) and 14 mostly part-time contractors," Executive Director Elizabeth Barron of the PHP Foundation said via email in an interview on Friday. Board members are unpaid volunteers, and funding comes from donations and grants. The foundation works with outside researchers and companies, including OpenAI and cybersecurity firms Wiz and Calif, to investigate security flaws and coordinate fixes, including Wednesday's patches... "We received no further indication from OpenAI, Wiz or Calif, with whom we're working closely on this issue, regarding any issues on patched systems," she said...

Recent events have shown how heavily companies and governments rely on PHP, Barron said. "Given that reliance, it is clear that PHP is incredibly under-funded."
AI helps researchers find decade-old flaws, but "it is also increasing maintainers' workloads," the article points out. "The PHP project is receiving nearly twice as many proposed code changes as a year ago." But unfortunately, the foundation's executive director says "the number of contributors hasn't doubled," and reviewing contributions and bug reports requires "a massive amount of human input and experience."

Wednesday the foundation said they hope to increase the number of knowledgeable engineers, but also "give the security team the resources it needs. We can only achieve this goal with funding from those who depend on PHP."

Their blog post also acknowledged the first signs of the bug were discovered in 2024, but that work on a fix stalled and restarted repeatedly over months (when there was still no known path to remote code execution): We won't pretend otherwise: the delay was a structural failure, caused by both the security team's decision process and its lack of resources. The security team has since started changing its processes, and that work continues, so that decisions can be made by majority and compromises are encouraged...

The coordinated disclosure of these vulnerabilities worked well until 2 days ahead of the targeted release date. On Tuesday, October 20th, at around 15:00 UTC, the two CVE IDs began circulating on online forums and social media... In response, the PHP project brought its pre-announcement forward [and also the release date for the patch. But as a result of the leak and pre-announcement] one of the security firms that had reported the issues mistakenly published a video. It showed their proof of concept working against a number of targets and revealed a few additional, though limited, details about the vulnerabilities. Copies of the deleted video started circulating on social media soon after. The video contributed to accelerated development of various exploitation proofs of concept, which then increased circulation on October 21st. Mitigation advice we started providing to a few critical infrastructure providers around Oct 20th 23:00 UTC, may have leaked as well. The PHP security team closely monitored and inspected appearing proofs of concept after the leak but did not identify any functional exploits at the time of release/public disclosure.

On October 21st at 07:41 UTC, more than six hours before the coordinated release, Chainguard unilaterally broke the embargo and published built images containing the fix. Like other distributors, Chainguard had received the patch in advance so its users could update the moment the vulnerabilities were disclosed. Any attacker could now study the fix in binary form while every other PHP user was still waiting for the release. This disregarded weeks of work by many parties toward a coordinated disclosure.
But the PHP Foundation also said Wednesday's patch "shows the progress we're making in how PHP security is handled." Once the full impact of the OOM problem was understood in August, the security team, the foundation, and the release managers delivered a fix for this deeply rooted problem across all supported branches, and distributions and LTS vendors received the patch ahead of time so their users can update quickly... We are now prioritizing measures to make sure vulnerabilities that need similarly complex fixes get resolved faster when they are reported in the future.
Thanks to Slashdot reader Mirnotoriety for sharing the news.

BBC technology editor Zoe Kleinman likens the recently discovered PHP security vulnerabilities to an unexploded bomb, writing, "The PHP story feels like the cyber equivalent of an unexploded bomb -- I have never seen such a dramatic, public and global response to a cyber event that hasn't happened yet." Although no successful attacks have been confirmed, the AI-assisted discovery of long-hidden flaws has triggered a worldwide security scramble, with websites taken offline as a precaution and administrators racing to deploy patches before attackers can exploit the vulnerabilities. From the report: The weaknesses found in the PHP programming language, which is used by millions of websites, had been quietly resting there for years and are not easy to exploit. One cyber security researcher told me he'd been up all night trying to do it as an experiment, but it was proving very difficult. [...] It was supposed to be kept quiet until everyone had a chance to fix their sites -- but the news was leaked. From that point the clock started ticking.

As I write this, there are no reports that anyone or anything has succeeded in using the flaws to attack a site. "There's a real dilemma," said Prof Alan Woodward from Surrey University. "How do you alert people they need to be ready, and then that a patch is urgently required, whilst not alerting attackers? Basically you're telling everyone about the problem at the same time and hoping the defenders aren't awake enough to act as soon as the patch is out."

But we do know from large web companies like Cloudflare and Palo Alto Networks that millions of attempts have been made. We probably won't know for a while whether it has worked for any criminals, because the companies affected might not be aware yet either. As far as we know the unexploded bomb remains intact for now, and for some experts this is a success. "We've seen how a team of people supported by the large AI company have used AI to find the problem, work for months together to solve it and get everybody ready to be safe and secure," Gina Neff, Professor of Responsible AI at Queen Mary University, told the Today Program on BBC Radio 4. "We have enormous capability to handle these risks."

"PHP disclosed two critical vulnerabilities in their programming language and urged web site operators to immediately apply the fix," writes longtime Slashdot reader smooth wombat. "As a result, government web sites in Europe and elsewhere temporarily went dark on Wednesday as operators worked to protect their systems." The Independent reports: Dane Knecht, the chief technology officer of Web and cloud security firm Cloudflare, said that attacks were emerging and Cloudflare was updating its firewall rules as a stopgap measure. "We are seeing early attacks emerging and are updating mitigations as new vectors show up. This is a STOPGAP only. Patch as soon as PHP releases the update," he said on X.

Officials have said that all PHP versions from PHP 5 onward could be affected, although PHP has not yet disclosed which versions are vulnerable. Special thanks to Slashdot readers Alain Williams and mrspoonsi for sharing this critical PHP security release.

For more details, read the official PHP announcement and guidance on what to do next.

An anonymous reader quotes a report from Ars Technica: Website admins, brace yourselves. Fixes for what are believed to be uncommonly severe vulnerabilities are scheduled to drop in a little more than 12 hours for PHP, a programming language that powers websites and Web applications everywhere. PHP maintainers said Monday that they planned to release patches for two vulnerabilities, both with severity ratings of 9.2 out of a possible 10.

"All PHP users are encouraged to prepare now so they can upgrade as soon as the release is available," the advisory stated. "We reserve the right to release earlier should details of either vulnerability become public, or should evidence of active exploitation appear in the wild." The maintainers published the advisory following the leaking of purported details, which have yet to be confirmed. The report showed a video of an exploit tool dubbed PHP2Shell executing code on webservers running WordPress 7.1.3, MediaWiki 1.46.2, phpBB 3.3.17, Magento 2.4.9, Joomla 6.2.0, Laravel 13.36.0, Laravel 8.83.29, Symphony 8.1.9, Drupal 11.4.10, and WHMCS 9.0.9, all of which use PHP. A video depicting the tool has been reposted here.

Attempts to locate the unconfirmed report were unsuccessful, but security firm watchTowr said it claimed to affect every PHP version from PHP 5, released in 2004, onward. The security firm went on to say it has confirmed that the vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619, are real. Researchers from separate security firm Sansec said they "expect mass attacks to start within 15 minutes of the release." A third security firm, Webfence, also urged admins to prepare now. Huntress has also issued an advisory.

TechRepublic reports: The TIOBE Index is a monthly indicator of programming-language popularity based on factors including skilled engineers, courses, and third-party vendors. The October 2026 rankings show a largely stable top 10, with R overtaking SQL and Julia returning to the top 20 for the first time in three years. [SQL has risen to #9 from #10 in October of 2025 — back when R ranked only #13.]

Python remains No. 1, followed by C, C++, Java, C#, and JavaScript, while Rust holds its No. 10 position. [A year ago Rust ranked only #16.] Outside the top 10, Julia climbs from No. 21 to No. 18, and TIOBE introduces Mandarin Chinese search terms into its methodology to broaden the index's geographic representation.
Dropping out of the top ten is Go, which fell from #8 in October of 2025 to #11. And Delphi/Object Pascal has plummeted from #9 to #19.

TIOBE CEO Paul Jansen argues that Julia's growing popularity "is largely driven by the demand for modern programming languages that combine high performance with ease of learning, particularly for numerical computing." Python offers an accessible, high-level approach to numerical computing, but performance can become a bottleneck. C++, on the other hand, delivers excellent performance but comes with a steeper learning curve and a lower level of abstraction. Julia aims to bridge this gap by combining the best of both worlds...

Apart from Julia, two other languages are knocking on the door of the TIOBE top 20: Dart and OCaml. Dart jumps from #41 to #27 this month. Thanks to its popular UI toolkit Flutter, Dart has been hovering around the edge of the top 20 for quite some time. OCaml, on the other hand, might come as a surprise. It jumps from #38 to #26 this month, driven in part by its growing use in real-time trading systems and parsing technology.

Long-time Slashdot reader ardiri remembers his days writing applications for the Palm OS. And he's now released approximately 1.5 GB of historical Palm OS development resources, "accumulated during the early days of handheld computing and preserved on hard drive backups for more than 25 years... to preserve the tools and knowledge that helped define an important era of personal computing." The collection includes historical SDKs, developer conference presentations, technical documentation, programming examples, limited source code, and development utilities. (ROM images, commercial applications, and simulator binaries have deliberately been excluded....) Making a broader collection of development resources available to the retrocomputing community, the archive is available at GitHub.com/ardiri/dev-palmos and is intended for historical preservation, education, and research, particularly as enthusiasts continue working to maintain, emulate, and revive the platform... Ardiri has also written an auto-biography and has started explored the engineering principles behind these systems in his books.
And somewhere along the way, Ardiri rediscovered the original source code for "The Palm OS Virus That Never Was — Lost for 25 Years, Found in 2026." Lurking on a CompactFlash card containing files dated June 2001, he found the self-replicating Palm OS virus that he'd developed and tested in June 2001, months before the planned PalmSource developer conference in San Jose. Named 'Virii,' the virus intercepted Palm OS system calls to progressively infect legitimate applications while preserving their original functionality. Infected applications could then spread between handheld devices through infrared beaming, potentially allowing an infection to propagate among hundreds of developers exchanging software at the conference. The virus also included a date-triggered payload designed to interfere with system time reporting between October 23 and 27, 2001, potentially causing erratic clocks, unreliable alarms, and missed appointments.
He promises the functional source code and binaries will remain private.

Linux maintainers "have ruled that people no longer have to declare their LLM usage," reports XDA Developers, "as Torvalds himself calls a ban on AI 'utterly stupid.'" The first part of this story comes via a message sent to the Linux mailing list. It announces one of the major changes decided during the Maintainers Summit on October 8, 2026, in Prague, Czechia, where submissions to the kernel no longer need to use the "Assisted-by" tag... meaning that people can submit AI-generated code without needing to declare it as such.

In some correspondence regarding concern about this new disclosure removal, the creator of Linux, Linus Torvalds, made his thoughts known... [Torvalds] compares an AI ban to getting rid of text editors, as doing so would prove that someone could write a good commit message without making any mistakes. He then rounds off his argument by asking, "Do you not see how UTTERLY STUPID those kinds of rules would be?" and stating that he simply expects the people working on the Linux kernel to "understand what they are doing."
Here's the last line of Torvalds' post. "Quite honestly, in my experience, the people I respect and call intelligent are not the ones that shy away from using new and interesting tools."

In a related story, Torvalds says he's used AI to help him understand patches that were hard to follow. And this week Torvalds even posted an LLM-assisted patch, reports Tom's Hardware: The development branch purports to fix an old issue with massive cache contention when many CPUs are reading the same file — a scenario potentially encountered when using shared libraries, databases, and web servers. Several developers had already made attempts over the years at fixing the issue, all with varied results, none quite ideal as an all-encompassing solution... He's now posted his solution in a development branch, and claims that he's seen a 23x performance improvement in a dedicated synthetic benchmark, though he notes that actual real-world impact will be far less significant, as "no real load" will witness those figures.
Torvalds used Anthropic's Claude Code, reports The New Stack, and "said the assistant wrote the implementation, tests, and initial documentation, and reviewed the code under his direction. He ran the benchmarks himself, despite having previously criticized developers for claiming AI writes 99% of their code." Tuesday Torvalds submitted a 10-patch series.

"Reviewers have since identified a race condition and raised concerns about memory reclamation," adds The New Stack. "Torvalds has handed further development to Kiryl Shutsemau, a Linux kernel developer who previously worked on the same bottleneck."

"Cloudflare has acquired Deno, the company behind the [server-side] JavaScript and TypeScript runtime created by Ryan Dahl, the inventor of Node.js," Forbes reported last week.

But Deno "has no future at Cloudflare, which will maintain the runtime for another year before ending its development," writes The Register. "That's OK with Dahl. 'I am now of the opinion that if you're choosing Node.js for building servers, you're doing it wrong,' Dahl told The Register."

It all started with his team's work on the platform Deno Deploy, "We wanted to make running applications as straightforward as possible," Dahl wrote on the official Deno blog. "But building and operating Deploy also showed us how much complexity remained underneath that developer experience. I wanted to simplify that layer, too." This led to celld. Building on the Cloudflare Workers programming model, celld lets developers build distributed applications from the start while making the system simple to operate. What excites me greatly is that the scaling is built into the programming model, rather than infrastructure each app has to assemble itself.... We want to make this programming model the default way to build servers, whether you run on Cloudflare's network or your own infrastructure.

Joining also means choosing where to focus our effort... Deno will remain open source, and we welcome others who want to continue its development. Deno Deploy will continue operating for six months before shutting down. We will provide migration support for paying customers moving to Cloudflare Workers. [Deno's JSR package registry for JavaScript and TypeScript] will continue operating, with its infrastructure moving to Cloudflare.
Forbes argues that this acquisition of Deno "turns a long-standing objection to Cloudflare Workers, the claim that applications built on it cannot easily leave, into a selling point." For CIOs evaluating serverless and edge platforms, portability now has a concrete answer... Released in August, [celld] is a single Rust binary that runs Workers and Durable Objects across many machines, with object storage as its only external dependency. Operators run multiple celld instances against one storage bucket, and the software handles placement, routing and persistence. Dahl and Belder will now lead an effort to merge celld into workerd and make self-hosting a supported way to run Workers applications. With this, customers can build an application on Cloudflare's network and move it to a private data center without rewriting it.
"With Deno, we improved the experience of writing JavaScript," Dahl argues on the Cloudflare blog, "but we didn't fundamentally change what developers had to assemble around the runtime. The bigger problems are around networked applications: distributing computation, coordinating state, data storage in general, and autoscaling to meet demand..." Could the programming model make partitioning across machines part of the design from the start? The solution clicked into focus when I read about Cloudflare's Durable Objects. It provided a very powerful abstraction: the distributed singleton with a SQLite database. Each Durable Object is like a small, individually addressable server with its own relational database. Its JavaScript execution is single-threaded (which is easy to reason about), it handles WebSockets, and its local SQLite database can be accessed synchronously. By building a chat application using one Durable Object per channel, you have sharded your data and WebSocket connections, and thus made your application scalable... What excites me is the leverage this model gives developers: compute, relational databases, queues, and real-time communication primitives designed for applications distributed across machines.
Now Dahl and 12 of his Deno colleagues "will work to build out Cloudflare's Workers platform," explains The Register, "expanding it for potential open-source use. He feels this approach is the way to go." "Right now, every other server is really operating at the Linux VM layer. That is not what Cloudflare Workers are," he said...

The ever-fickle Dahl first debuted Deno in 2018 as a rewrite of Node. The name 'Deno' is an anagram of Node, and it was Dahl's attempt to fix everything he felt he got wrong with Node — built-in fetch, a permission model, native TypeScript support et al. Sequoia backed Dahl's company for $21 million in 2022, and as of August, Deno amassed 400,000 monthly users. Nonetheless, Node's gravity proved too heavy for Deno to achieve escape velocity.

"What we found over years of working on Deno is that you can't really deviate from Node.js very much," Dahl told The Register. "As we continued to try to get adoption for Deno, we found we had to essentially backpedal on some of the original promises and become more Node compatible over time, and that left us as a kind of an alternative Node.js implementation." Going forward, Cloudflare will supply Deno with bug fixes and security patches for the next year, while Dahl looks for a new home for the MIT-licensed open source project.
Dahl's worked could bring "yet another revolutionary turn for server-side JavaScript," the article argues, "offering a runtime that would require only 300 KB of memory per instance, rather than the hundreds of megabytes now required for Node/Deno. Such savings could quickly add up for a cloud provider, especially one serving the voracious agentic market."

And as Dahl wrote on the Deno blog, "The need for better abstractions is especially acute with AI. Durable Objects bring together capabilities that are particularly useful for agent harnesses: inexpensive, serverless execution, persistent state, WebSockets, and a high-level JavaScript interface. This is what I'm most excited to explore and why celld focuses on Durable Objects."

Anthropic says Claude-generated code has scaled so quickly that its existing Git-based infrastructure could not keep up. In response, the company built a custom centralized source-control system called Scion, along with AI-assisted review and search tools. The Register reports: "In May 2026, Anthropic averaged around 2,500 code changes merged per day; as of September, we merged over 30,000 per day," the biz said in a blog post on Tuesday. "We don't expect this rate of growth to slow down anytime soon; the latent demand for merging code is practically infinite, and every bottleneck we remove immediately leads to a further increase in the amount of code we produce."

After several months of model prompting and five months of migration, the result is a homemade version control system called Scion, a monorepo scheme that sounds a bit like Subversion, Apache's centralized version control system. [...] Scion has been designed to meet the needs of AI agents, so the client leaves much of the work to the server; the source control queries are exposed via API so internal tools can respond without needing a local repo, and there's less synchronization but more need for server speed.

"In Scion, the unit of work is a 'changeset,' an entry in a write-ahead log," Anthropic explains. "A changeset stores most of what you'd expect from a commit in git. But where a git commit stores a pointer to the tree, a changeset stores a list of the files that changed relative to its first parent, along with content-addressed pointers to the compressed file contents in blob storage." [...] Anthropic says its bespoke system isn't right for general use. There will be no open source release. Nonetheless, the company contends that its own code scaling problems will become commonplace in other organizations over the next few months, so it wanted to share its approach -- having ample funding to pay for writing custom infrastructure tools.

An anonymous reader quotes a report from ZDNet: Many open-source developers still dislike AI. The latest example is System76 banning AI-generated content from its COSMIC desktop. At Open Source Summit Europe, Linux creator Linus Torvalds offered a different take: "I actually really like using AI," Torvald told Dirk Hohndel, his good friend and head of Ericsson Software Technology, in their latest discussion. [...] Torvalds said, "I think that you need to be very careful using AI when you're doing something real and important." Torvalds explained he hadn't always felt that way about AI programming. "I used to think it was just not very good -- but now I'm at the point where I actually really like using AI."

"To be fair," he continued, "I don't do a lot of kernel programming. I'm a maintainer. The Linux kernel is a project where other people do the real work, and I act as the collection point. But I still enjoy programming immensely. I think AI is a wonderful tool if you use it correctly and treat it as a tool, and I find it makes programming much more enjoyable." Torvalds recalled, "I started programming in 1981 or so, and back then computers were much simpler, and you could understand what they were doing, and also the programs you compared your own programs to were much simpler."

"It's a different story today," Torvalds said. "The bar in software engineering has grown so high that it's hard to see your own small efforts as worth anything, because you're used to all these polished, professional programs. [...] A lot of people make fun of vibe coding, but I think it's a wonderful way to find joy in programming. It makes you feel like you're doing something relevant. It allows you, as a new programmer, to do things that you would otherwise have a really hard time with."

He continued: "I love the concept of AI as a gateway drug because I was working on my own toy project, the guitar pedal, and I knew what I was doing. I had a user interface that I had written myself in C that was running on a microcontroller that was running on this small screen, and I was like, "This is just stupid. It looks like something from the '80s; I wanted it to look like something from this century. But I don't do Java. I do kernels." "So, I use AI to do the things that I'm bad at," Torvalds went on, "I'd seen all the same YouTube videos you have. Give AI a prompt, and it will do it. So I gave it a prompt, and it did it, and it was horrendous. Then I said, 'Hey, look! I already did this in C. I did it the right way. It's just ugly." Torvalds acknowledged that AI tools are helping identify security vulnerabilities and improve the Linux kernel, but at the cost of overwhelming maintainers with questionable bug reports and superficial fixes. He called some submissions "mindless band-aid kind of patches."

That said, despite AI's growing influence, Torvalds believes Linux's success comes from steady, incremental development rather than sweeping changes. "I'm a big believer in the whole incremental small changes that, over time, turn into big features," he said. The development goal remains "incremental improvement and steady progress all the time."

A study of more than 700 software firms found that AI coding agents significantly increase the amount of code developers produce, but not the amount of software companies actually ship. Ars Technica reports: A recent study (PDF) of actual coding practices across hundreds of firms finds that human code review forms a significant "bottleneck" for the overall efficiency of AI coding tools, resulting in "little evidence that firms increase software output or reduce employment" by using them. Any efficiency increased during the actual coding phase, the study authors find, is "absorbed by downstream constraints in the production process"; as "the code review process significantly increases in length, pull requests are more likely to require revisions, and reviewers leave more comments."

[...] In terms of raw code being produced, the results are clear and stark. The introduction of AI coding agents at a firm leads to a 30 percent increase in total lines of code generated, a 20 percent rise in the number of total commits, and a 23 percent increase in pull requests on average, the researchers write. But all that extra code doesn't translate directly into improved software output on the firm level. On the contrary, the resolution rate for Issues and Epics (i.e. wholesale software features) tracked by tools like Jira did not change in a statistically significant way after AI tools were introduced (the researchers also found no "compositional shift" in the size or complexity of those Jira-tracked issues across the AI introduction).

The reason for that discrepancy can be found directly in the code review process, which takes markedly longer on average after the introduction of AI coding agents. Overall, the average "review process" time between a pull request getting submitted and it being merged into the codebase balloons 49 percent on average after AI agents are introduced. That effect can be seen in more granular data, too, with "the share of pull requests with changes requested nearly doubl[ing], and the number of comments per pull request increas[ing] by 35%" following the AI agent shift, the researchers write.

In response to this change, the researchers found a 14 percent increase in the share of workers performing code reviews after AI agents' introduction. They also write that they "cannot attribute significant employment changes to AI" after looking at total active workers across Jellyfish and cross-referencing with LinkedIn data at those firms. While AI could also theoretically help with this review process, the researchers found that, so far, that impact has been marginal. Although 80 percent of measured firms used some form of AI code review by March 2026, AI agents were only responsible for 23.3 percent of all review comments and 10.8 percent of all pull requests, suggesting humans were still responsible for the vast majority of this work.

The blog It's FOSS reports: You already know that Canonical has been selectively replacing Ubuntu's C-based system components with Rust-written equivalents that don't compromise in terms of functionality, most of the time. Now it looks like the distro's OpenPGP implementation is next, with Sequoia PGP coming preinstalled in Ubuntu 26.10. Canonical wants it to eventually replace GnuPG [the dominant Linux implementation of PGP, written in C] as the default toolchain, though that switch has not happened yet... [The Ubuntu 26.10 release notes say Sequoia PGP's default status will be a future goal...]

[Sequoia PGP] was started in 2017 by three former GnuPG developers who chose to build a new OpenPGP implementation in Rust rather than keep evolving GnuPG's existing codebase. Sequoia PGP is designed as a library that other software can use directly, rather than a standalone command-line tool. sq sits on top of that for encryption, decryption, signing, and key management, and sqv handles signature verification, filling in for gpg and gpgv in GnuPG.

Sequoia also implements RFC 9580, the 2024 revision of the OpenPGP standard, whereas GnuPG has continued from the RFC 4880 branch, pursuing its own newer extensions and the LibrePGP specification rather than adopting RFC 9580 as its primary standard.
From the It's FOSS Weekly newsletter, which also notes that the founder of the It's FOSS blog has also created a Linux-themed game called TUXDLE — a variation on Wordle where all the answers are Linux terms.

OpenAI says an unreleased internal model has produced 372 results that either resolve or make substantial progress on open problems in mathematics and theoretical computer science. The company says almost all were generated by a single AI agent from a single prompt. "This would be a striking difference from OpenAI's earlier blockbuster solution to the Navier-Stokes problem, which was produced through the collective efforts of a 10,000-strong agentic swarm that cost millions of dollars in computing power," reports Scientific American. From the report: OpenAI revealed the results in a GitHub repository at 6 P.M. EDT. The deluge will take mathematicians months to parse through and understand -- including to determine whether the proofs contain novel and important ideas or are mostly mash-ups of existing techniques. But many of the results have already been verified in Lean -- a programming language that validates a proof's logic -- and are therefore all but certain to be correct.

Among the results claimed are a solution to the four-dimensional Kakeya conjecture, improvements on some of the world's most important computer algorithms and actual progress toward math's scariest problem, the Riemann hypothesis.

Python's security developer-in-residence Seth Larson reports from this year's official core developer Python Language Summit: "No one said 'don't do this' last year". After testing the waters at PyCon US 2025, [software engineer] David Hewitt returned to the Python Language Summit asking what Python core developers want from Rust, along with proposed timelines, phases, and success criteria for how the Rust for CPython project might proceed and become a permanent fixture within the CPython project. David is acting as an "ambassador" for the Rust for CPython project team, which is currently led by core developers Kirill Podoprigora and Emma Smith as authors of the Rust for CPython PEP draft. Emma also spoke at PyCon US 2026 about the Rust for CPython project. The team itself is around 60 developers in a Discord channel, among them a "few [Python] core developers" and a "delegation from the Rust project".

The team has experience with previous projects integrating Rust into existing codebases, such as Android and the Linux kernel, and is "excited by the work and keen to support [the project] if we proceed". Showing how adopting Rust may specifically help CPython, David noted how the number of issues labeled with " type-crash" has been steadily rising over time... David explained that Jeff Vander Stoep described Rust in Android as "move fast and fix things", and that "fewer revisions for patches of the same size" was the experience Android has had since adopting Rust....

One of the biggest concerns from a year ago was Rust's lack of platform support compared to CPython, which at the time of writing officially supports 20 different architectures and platforms at either Tier 1, 2, or 3. David shared that Rust's support of different platforms has "widened since last year" and was becoming "less and less of a concern". The proposal would be to ask Python distributors to attempt using the optional Rust support in Python 3.16 (October 2027) and report platform-specific issues upstream in time to be resolved around the Python 3.17 timeline (October 2028)...

[T]he first Rust code to ship in Python would be in Python 3.16 [October 2027], where it would be completely optional, with the existing C code kept as a fallback. The earliest that Rust would become required to build CPython is Python 3.18 in 2029, at least three years away... The Rust for CPython team has selected the zlib module as the first module to be given an optional Rust implementation because they "wanted to achieve a significant improvement" with a "small scope". The proposed Rust implementation will use zlib-rs, which is "heavily tested and used by the Firefox, uv, and Cargo" projects and "faster than zlib and zlib-ng on many platforms".... This small change would have an impact: the zlib compression algorithm is "widely used by Python packaging", meaning that (almost) "every pip install in Python 3.16 will be sped up" if the proposal is accepted.
Thanks to long-time Slashdot reader RoccamOccam for sharing the article.