Good luck with discoverability. You'll be competing with the Zen browser.
post
What’s wrong with zedless or gram that you did this?
Nothing wrong with them! But since I want to build another tool on top of it (for fiction/novel outlining and writing) I figured this was a good exercise to become familiar with the codebase. And since I still do some Rust development, having control over both my IDE and my writing software seemed an added benefit :)
I tried gram, and it was rife with bugs. Couldn't recall the specifics. Interested in zedless, however.
Hasn't had an update in nearly a year, according to their github. Bit disappointing.
Because it's on Codeberg now. Last updated 22 hours ago. Version 2.2.0 was released 3 days ago.
Does it qualify as cognitive dissonance maintaining a fork of a partially vibe-coded product to remove vibe-coding tooling because you hate vibe-coding?
What's the plan for ongoing maintenance?
Aren’t all of these features able to be disabled in zed itself? If so what does a fork offer me instead?
Yeah, if you don't mind the UI clutter/teasers, it doesn't make much of a difference. For now, the most noticeable difference is that the default layout is more old-school, with the project layout and the git panel on the left-hand side again, though even without this fork you can configure it to be like that too.
Wish you all the luck. Wondering: why not “ship” a configuration? All AI features and layout can be configured through JSON afaik.
Thanks!
As for the motivation of the fork, basically two reasons:
- Even though you can disable AI features and configure the layout, the teasers and some UI elements remain as they try to draw you in.
- I want to use their UI framework and editor for a different project too, so I want to be able to start that from a trimmed down base anyway.
all 18 comments