BRbrudgers·Feb 5, 2025
related project (probably), https://github.com/crazywolf132/evo
with some related comments, https://news.ycombinator.com/item?id=42787371
In Sage: Burning Away Git Complexitybinbandit
evo
Go2025–2025
binbandit / evo · Archived
evo
Version control that works the way you think
5Distinct people
5Mentions
0Explicit recommenders
231GitHub stars
What to know before exploring
What it is
Version control that works the way you think
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
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 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 day5 dated mentions
Observed mentions: 2025-01-22 01:02:57 UTC to 2025-02-05 19:25:50 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 |
|---|---|---|---|---|---|
| Jan 22 | 2025-01-22 00:00:00 UTC | 2025-01-23 00:00:00 UTC | 4 | 1 | 3 |
| Jan 23 | 2025-01-23 00:00:00 UTC | 2025-01-24 00:00:00 UTC | 0 | 0 | 0 |
| Jan 24 | 2025-01-24 00:00:00 UTC | 2025-01-25 00:00:00 UTC | 0 | 0 | 0 |
| Jan 25 | 2025-01-25 00:00:00 UTC | 2025-01-26 00:00:00 UTC | 0 | 0 | 0 |
| Jan 26 | 2025-01-26 00:00:00 UTC | 2025-01-27 00:00:00 UTC | 0 | 0 | 0 |
| Jan 27 | 2025-01-27 00:00:00 UTC | 2025-01-28 00:00:00 UTC | 0 | 0 | 0 |
| Jan 28 | 2025-01-28 00:00:00 UTC | 2025-01-29 00:00:00 UTC | 0 | 0 | 0 |
| Jan 29 | 2025-01-29 00:00:00 UTC | 2025-01-30 00:00:00 UTC | 0 | 0 | 0 |
| Jan 30 | 2025-01-30 00:00:00 UTC | 2025-01-31 00:00:00 UTC | 0 | 0 | 0 |
| Jan 31 | 2025-01-31 00:00:00 UTC | 2025-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 1 | 2025-02-01 00:00:00 UTC | 2025-02-02 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2 | 2025-02-02 00:00:00 UTC | 2025-02-03 00:00:00 UTC | 0 | 0 | 0 |
| Feb 3 | 2025-02-03 00:00:00 UTC | 2025-02-04 00:00:00 UTC | 0 | 0 | 0 |
| Feb 4 | 2025-02-04 00:00:00 UTC | 2025-02-05 00:00:00 UTC | 0 | 0 | 0 |
| Feb 5 | 2025-02-05 00:00:00 UTC | 2025-02-06 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
5 sourcesHe made a fix in https://github.com/crazywolf132/evo/commit/2452bec536d9b4d60... but he converted the indentation at the same time, and does not PRs at all. It's dangerous amateur stuff.
In Evo: Version control that works the way you thinkThanks for the heads up, there are indeed incredibly bad things in that project as linked by the top comment (with the simple word "bruh...") : https://github.com/crazywolf132/evo/blob/15d2ec6e821ef221961...
It is scary that someone can say it is "encrypting" a private key by applying a simple XOR.
Also :
"File-Based Index: We track file hashes in a small JSON index instead of re-hashing everything on every commit or switch. This makes commits and merges faster because Evo only re-hashes files if it notices a changed modtime"
Using modtime is not a good idea at all, this is very telling about how much author knows about different workflow. For those who don't know : you can have remotely mounted files where your machine and the server time is different (happens to me and realized that makefile is modtime based and it creates problem), als
Read the rest
o obviously clock can change and you do not want your version control system to be blind on changed file, ever.
"evo workspace merge" maps[0] to "git merge"
[0]: https://github.com/crazywolf132/evo/blob/main/docs/migration...
In Evo: Version control that works the way you thinkEvo: Version control that works the way you think
44 points · Open discussion