IdeaWell

Project ideas from Hacker News discussions.

jj – the CLI for Jujutsu

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Git compatibility & safemigration

“There's one other reason you should be interested in giving jj a try: it has a git compatible backend, and so you can use jj on your own, without requiring anyone else you're working with to convert too. This means that there's no real downside to giving it a shot; if it's not for you, you're not giving up all of the history you wrote with it, and can go right back to git with no issues.” — dgb23
“You can take a git repo, try jj for a while, and if you decide to go back, you don't lose anything.” — maleldil

2. Distinct commit workflow > “One aspect of it I dislike is edits to files are automatically committed, so you need to defensively create empty new commits for your changes.” — tom_alexander

“jj new simply means 'create a new commit [ontop of ]' – you don't have to describe it immediately.” — saghm

3. Skepticism about a new VCS > “git is good enough, and is the global standard. We don't need more new VCS.” — aftbit

“I used jj… did not find it all that much better than git.” — BeetleB

🚀 Project Ideas

Generating project ideas…

[JjLite]

Summary

  • A git‑compatible wrapper that lets teams use jj’s clean commit workflow without abandoning their existing git repositories.
  • Eliminates submodule friction and provides visual conflict‑resolution, lowering the adoption barrier.

Details

Key Value
Target Audience Developers and small teams wanting a smoother VCS experience while staying on git back‑ends
Core Feature CLI/GUI that translates common git commands to jj equivalents, adds guided staging and submodule‑aware changeets
Tech Stack Rust (jj core), Electron/React for UI, SQLite for metadata storage
Difficulty Medium
Monetization Revenue-ready: $5 per user per month for team plans

Notes

  • HN users repeatedly cite “submodules aren’t supported” and “mixing git/jj is risky” – JjLite solves both while preserving full git history.
  • The project would spark discussion about whether a thin UI layer is enough to make jj mainstream.

[RepoStacker]

Summary

  • Treats a set of git repositories as a single logical stack, enabling atomic commits that span multiple repos.
  • Provides a unified code‑review view that shows only changes since the last review across all repos.

Details

Key Value
Target Audience Open‑source maintainers, monorepo teams, and cross‑project developers
Core Feature CLI/GUI that syncs multiple repos, creates stacked pull‑requests, auto‑generates incremental diffs, and supports partial clones
Tech Stack Go (sync engine), Node.js + React for UI, PostgreSQL for state tracking
Difficulty High
Monetization Revenue-ready: $12 per repo per month, free tier up to 3 repos

Notes

  • Commenters lament the lack of native multi‑repo handling and “changes‑since‑review” features; RepoStacker directly addresses these pain points.
  • Could generate strong community interest and discussions about standardizing stack‑based PR workflows.

[ReviewPulse]

Summary

  • A SaaS that indexes git repositories and visualizes “changes since last review” for each pull request, eliminating full‑diff churn after force pushes.
  • Offers an API for bots and AI agents to fetch only new changes, improving review efficiency.

Details

Key Value
Target Audience Code reviewers, maintainers, and CI pipelines seeking incremental review workflows
Core Feature Web service that tracks repository states, UI showing delta between two commits, and API for incremental change retrieval
Tech Stack Python (FastAPI) backend, Redis cache, React frontend, Docker deployment
Difficulty Medium
Monetization Revenue-ready: $0.01 per 1k API calls, free tier 10k calls/month

Notes

  • HN discussions highlight frustration with losing review context on force‑pushes; ReviewPulse restores that context instantly.
  • The service could be a catalyst for debate on AI‑assisted code review tooling.

Read Later