Continued support of Convex Ents

[GodGardensGuns]

Given this note from the Convex Ents official docs:

Ents is in maintenance mode. We're open to taking PRs, and will make sure it doesn't break. There will not be active feature development from the Convex team.

What's the roadmap for using Ents with better-convex? Will they be phased out eventually? The better-convex docs make it clear that using Ents is optional but at the same time, they imply that the Ents integration is superior or for advanced users vs. vanilla Convex.

[zbeyens]

Ents is superior for DX and ergonomics - it results in much less boilerplate.

"Maintenance mode" doesn't mean abandoned - it means the API is stable. For a data layer, stability is actually a feature.

Most importantly: no lock-in. You can use ctx.table (Ents) and ctx.db (native) in parallel, in the same codebase, even in the same function. If Convex ever ships native relationship support that supersedes Ents, we will follow that direction.

That said, better-convex philosophy is to not reinvent the wheel - and neither ctx.db nor ctx.table quite pass that test. I want something closer to Drizzle or Prisma ergonomics. This would be the next major feature for our roadmap.