I will admit that I don't like vibecoded things, but perhaps I must stomach that AI will be writing a lot in this brave new era.
However, when the commit history has stuff like
v0.5.0: native backends, software renderer, text input, IME
Co-authored-by: Claude <[email protected]>
Co-authored-by: Codex <[email protected]>
Co-authored-by: Composer <[email protected]>
Co-authored-by: Cursor Grok 4.5 <[email protected]>
377 files changed
Lines changed: 62423 additions & 2871 deletions
it's very hard. These “change the entire world” commits make for a history that is impractical to follow for a human, and therefore of little interest to me.This is a publish-only mirror repo.
The commit history is the publish history, not the work history.
I think a challenge for a vibe coded library to gain adoption is if there is a lack of human time investment in its creation, how do we know there will be investment in its maintenance?