Arkos.js is Done. And That's Exactly the Point

It's been almost two weeks since v1.7.3-rc. As of writing, there are no changes lined up for v1.7.4-rc.

No bug fixes. No patches. No hotfixes.

And that's not a problem—it's the sign of a framework that has finally, truly, settled.

The Quiet Shift

There was a moment—somewhere between 1.6 and 1.7—when the nature of issues in the Arkos.js tracker changed. The "this doesn't work" reports grew rare. The "this breaks when I do X" tickets stopped coming.

What remained were feature requests. Ideas. "Can this do X too?"

But here's the thing: most of those feature requests weren't bugs or missing essentials. They were divergence points—things that strayed from Arkos's core mission. The team looked at each one and asked: "Does this belong in a framework that exists to make Express + Prisma RESTful APIs effortless?"

More often than not, the answer was no.

The Bic Pen Theory of Software

Think about the humble Bic pen. It's cheap. It works. It does exactly what a pen should do—put ink on paper—and it does that so consistently that no one ever thinks about improving it.

Could you add a stylus tip? A laser pointer? A built-in ruler?

Sure. But then it wouldn't be a Bic pen anymore. It would be something else, probably worse at being a pen, and definitely more expensive.

Express itself followed this trajectory. It's the most-used JavaScript server framework not because it's the flashiest or most innovative, but because it does its job so well that it doesn't need to change. It's the framework equivalent of the Bic pen—perfected through simplicity, not complexity.

Arkos.js is following the same path.

The Road Ahead Is Stable, Not Silent

v2.0 is approaching. v1.10—the first Long-Term Support release with 3 years of bug-fix support—is on the horizon. These aren't the milestones of a dying project. They're the milestones of a finished one.

That's not abandonment. That's responsibility.

The Microservices Question

"I don't want to create a shitty lib without the voice of experience."

That's the honest truth the Arkos team has about microservices support. They haven't spent enough time with messaging architectures (Kafka, RabbitMQ, etc.) to ship something they'd be proud of. And rather than ship something half-baked—something that diverges from the framework's philosophy of simplicity and reliability—they've chosen to ship nothing at all.

That's the opposite of neglect. That's integrity.

What "Done" Actually Means

If "dead" means "not releasing every week with shiny new features that break things," then yes—Arkos is entering its dead phase.

But "dead" is the wrong word. "Complete" is better. "Stable" is accurate. "Done" is the truth.

The framework that started as a single function has grown into something that:

• ✅ Generates full REST APIs from Prisma models
• ✅ Handles authentication, validation, and authorization
• ✅ Serves static files and handles uploads
• ✅ Documents itself via OpenAPI
• ✅ Supports WebSockets via Gateways
• ✅ Is approaching its first LTS release

It keeps getting downloads. It keeps running in production. The maintainer is present, the roadmap is clear, and the community in Mozambique and beyond continues to ship real products with it.

Arkos.js isn't dead. It's done.