There is no reliable evidence that generative AI is either killing or saving Raku. Raku development is continuing, and developers have begun building AI-related tools in its ecosystem. But available figures do not show whether AI has changed Raku adoption, contributions, or project outcomes. The most accurate answer is that AI is present around Raku, while its effect on the language remains unmeasured.
What the evidence says about Raku today
Raku is still being developed. The Rakudo project, which describes Rakudo as an implementation of Raku, lists Rakudo #196 in August 2026. Its release notes include RakuAST fixes and code-generation improvements. The release implements Raku specification versions 6.c and 6.d, with 6.d as the default unless a version pragma selects 6.c. See Rakudo’s release history.
As an Amazon Associate I earn from qualifying purchases.
That is evidence of ongoing compiler work—not proof that the language is growing, or that AI has caused a revival. A release establishes that maintainers are shipping changes; it does not by itself tell us how many people use Raku, how many new projects choose it, or whether AI has altered those trends.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Where AI has entered the Raku ecosystem
A 2025 ecosystem roundup published by Planet Raku highlights two AI-related projects. AI::Gator is described as an AI generic assistant with a tool-oriented REPL. LLM::Graph is intended to schedule and combine LLM generation steps. These examples show that Raku developers are experimenting with AI-connected software. They do not establish how widely either project is used, how reliably it works, or whether it improves development outcomes. Read Planet Raku.
The same roundup reports substantial package activity: 503 modules were updated or first released in 2025, 2,431 modules were installable by name with zef, and the Raku Ecosystem Archive contained 13,808 module versions. Those counts describe releases and availability—not the number of active Raku developers, the health of every module, or AI’s effect on the ecosystem.
Why broad AI coding growth does not answer the Raku question
GitHub’s 2024 Octoverse report counted 137,000 public generative AI projects on GitHub, a 98% year-over-year increase, and said more than one million maintainers, teachers, and students had used Copilot for free. These are platform-wide figures. They do not identify Raku’s share of those projects or show that AI tools produce good Raku code. Read GitHub’s 2024 Octoverse report.
GitHub’s 2025 report says TypeScript overtook Python and JavaScript in August 2025 to become the most-used language on GitHub, and discusses AI-assisted coding’s influence on developer-tooling decisions. That reflects activity and choices on GitHub, not a measured decline or increase in Raku attributable to AI. Read GitHub’s 2025 Octoverse report.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What would count as evidence that AI is helping or harming Raku?
To answer the question confidently, someone would need to measure Raku-specific outcomes over time and distinguish AI’s contribution from other factors. Useful evidence would include:
- Whether AI use changes the number or quality of Raku contributions, maintenance response times, or completed project work.
- Whether people using coding assistants can generate, understand, and test correct Raku code more effectively than comparable developers not using them.
- Whether AI-related errors, maintenance costs, or reduced demand for human Raku expertise offset any productivity gains.
- Whether changes in Raku adoption can be linked to AI rather than to unrelated shifts in developer interest, tooling, or language needs.
The available sources do not provide a representative, Raku-specific assessment of these outcomes. A community discussion about attracting more Raku coders included an informal poll with 12 votes from 760 views; its author described it as a self-selected sample. That is not enough to infer community-wide attitudes or measure AI’s impact. See the discussion and poll.
How to assess an AI coding assistant for Raku
There is no comparative evaluation here that establishes which assistants handle Raku well. If you are considering one, judge it on the work you actually need done rather than assuming broad coding benchmarks transfer to Raku:
- Syntax and idioms: Does it produce valid Raku and use language features appropriately?
- Current behavior: Can you check its suggestions against your installed Rakudo version and run tests, rather than relying on a confident explanation?
- Raku-specific features: Does it handle grammars and Raku’s multi-paradigm constructs correctly in your examples?
- Workflow fit: Does it work with your editor and development process without adding friction?
- Evidence quality: Are claims about Raku performance backed by independent, reproducible tests, or only by broad language claims?
These are evaluation criteria, not findings that any particular tool passes them. Treat generated code as a proposal to inspect and test.
What Raku’s governance can—and cannot—tell us
The Raku community describes a seven-person Steering Council responsible for language, compiler, and ecosystem quality and stability, as well as making contribution and learning accessible, inclusive, and sustainable. That provides context about how the community approaches stewardship. It is not evidence that AI has improved or weakened Raku’s prospects. Read the Raku community’s involvement overview.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
