duke.nvim

Note: This analysis is based entirely on the self-reported, unverified description provided by the author. No third-party data, revenue figures, customer names, or traction metrics are available.

The description states that duke.nvim is a pure Lua plugin for Neovim 0.11 and newer, intended to allow developers to manage Maven, Gradle, and Spring workspaces inside Neovim without leaving the editor.

It supports:

• Creating Maven, Gradle, and Spring Boot projects
• Discovering workspaces without running builds
• Refreshing resolved build information
• Showing dependency drift, ownership, and paths
• Building and applying upgrade plans with conflict protection
• Adding, upgrading, inspecting, and removing dependencies
• Safely creating Maven reactor modules
• Navigating Spring configuration files and generated Java sources

The plugin includes a Project Center that separates fast local inspection from explicit build-backed refreshes. Dependency upgrades are session-scoped plans, allowing users to review changes before applying them.

Inference: The product is described as a Neovim plugin built in Lua using GPT-5.6 via Codex CLI for development assistance.

The author states that the goal was not to recreate an IDE but to give Neovim a focused project and build-model layer, similar to how cargo new and cargo add work in Rust.

It evolved from:

• A project scaffold tool
• Into a safe Java workspace manager

Key claims include:

• The plugin provides a “cargo new plus cargo add feeling for JVM”
• It avoids interrupting the editing flow
• It gives Neovim a focused layer beside tools like nvim-jdtls

Claim: The product is positioned as a lightweight, safe, and integrated tool for Java developers working inside Neovim.

The description does not explicitly name target customers or define an ideal customer profile (ICP). However, it implies:

• Developers using Neovim
• Working with Maven, Gradle, or Spring Boot projects
• Preferring to stay within Neovim for build and project management tasks

Inference: The primary user base likely consists of Java developers who use Neovim as their main editor and want seamless integration with JVM tooling.

There is no evidence in the description regarding:

• Revenue model
• Pricing structure
• Monetization strategy
• Paid features or subscriptions

Not evidenced

The author states that duke.nvim was built using:

• Lua
• Neovim 0.11+
• GPT-5.6 via Codex CLI
• Tools such as Plenary tests, vimdoc, and README synchronization

Key technical decisions mentioned:

• Pure Lua implementation
• No dependency on UI frameworks, JDTLS managers, JDK vendors, or plugin ecosystems
• Session-scoped upgrade plans
• Safety rules to prevent corruption during file changes
• Separation of target Java version from runner JVM version

Inference: The tool is lightweight and designed for developer productivity with strong safety guarantees.

There is no evidence in the description of:

• Users or customer base
• Downloads or usage statistics
• Adoption rate or feedback
• Product maturity beyond initial development

Not evidenced

The description does not mention competitors or direct market comparisons. However, it references:

• Tools like nvim-jdtls
• Rust’s cargo commands as a point of comparison

Inference: The tool competes in the space of developer productivity tools for Neovim and JVM environments, potentially overlapping with IDE-like functionality.

• No external validation or user feedback — all claims are self-reported
• Single-person team — raises questions about scalability and long-term maintenance
• Limited scope: Only supports Maven, Gradle, and Spring; no mention of other build systems
• Dependency on GPT-5.6 — suggests a high level of AI involvement in development, which may not be sustainable or replicable

Inference: The lack of traction, users, or third-party validation makes it difficult to assess commercial viability.

1. Have you received any feedback from other developers using duke.nvim?
2. How do you plan to scale beyond a single developer?
3. Are there any known edge cases or limitations with real-world projects?
4. What is your roadmap for expanding support to other build tools (e.g., Bazel, sbt)?
5. Do you have plans for monetization or commercial partnerships?