FRfreetonik·Oct 18, 2025Submission
Edge: Modal terminal-based text editor for GNU/Linux
3 points · Open discussionalefore
edge
C++2020–2025
alefore / edge
edge
Edge - a text editor
3Distinct people
19Mentions
0Explicit recommenders
88GitHub stars
What to know before exploring
What it is
Edge - a text editor
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- alefore/weblog · linked in 4 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:58 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year19 dated mentions
Observed mentions: 2020-03-24 18:12:12 UTC to 2025-10-18 16:40:55 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 2 | 1 |
What Hacker News says
3 sourcesFor what it's worth it, I'm still developing and using exclusively my own text-based editor/IDE: https://github.com/alefore/edge
I wrote recently a bit about my conclusions after ten years of developing it: https://github.com/alefore/weblog/blob/master/edge/README.md
In IDEs we had 30 years ago and lost (2023)Show HN: Duende: Web UX for guiding Gemini as it improves your source code
I wrote a simple web UX in Python/JavaScript that spawns a conversation with Google Gemini with MCP commands that let it work on a specific coding task that you specify: http://github.com/alefore/duende
The UX lets you observe the conversation and provide guidance (e.g. "don't implement Foo through Bar, that's suboptimal; instead …").
It supports a `--review` mode, where once the main conversation says "I'm done with the task", various "evaluation" conversations are spawned, each focusing on reviewing the change from a very specific angle (e.g. "does it introduce useless comments?"). In the future, I'm considering adding other workflows.
I've used it mostly to develop itself (I started with a super rudimentary manual implementation and then mostly used Duende to extend its own implementation) as well as (with moderate success) to add a fe
Read the rest
w new features to [my C++ text editor](http://github.com/alefore/edge).
It's been a lot of fun. I'm still developing my intuitions for what works and what doesn't, but I've already had plenty of experiences where I've been WOW'ed by what LLMs can already accomplish (as well as, to be honest, plenty of very disappointing cases where it struggles significantly on tasks that I expected would have been trivial). It's a learning experience, seeing things like how to avoid hallucinations; developing an intuition for how much to break down large tasks into smaller ones; or knowing when to abort a conversation and restart it with an improved prompt (vs continue to steer it in the right direction).
I think investing up-front in setting up a good context (e.g., good validation logic, useful constant contexts, a good set of "review evaluators" that can push-back against sloppy code) can go a long way to increase the odds of success.
It has changed my perception on the applicability of AI for developing software. While I've reviewed all the outputs (and often rewrite parts of them manually), I'm already incorporating it into (some parts) of my development life-cycle.
I have many ideas for improvements, but figured I'd share this early and ask for feedback. Hopefully others find it interesting; would love to hear your thoughts.