2 ms·

I just cant imagine anything vibe coded being maintained for more than a few months. The moment random bugs start hitting and fixing the bugs starts breaking o

I just cant imagine anything vibe coded being maintained for more than a few months. The moment random bugs start hitting and fixing the bugs starts breaking other things, no one is going to want to contribute. Its all going to devolve into a slop fest that takes more and more effort to make incremental progress

rayiner 12d ago
Have you looked at the code before rendering judgment? It seems pretty readable and well-structured: https://github.com/eval-exec/neomacs/tree/main/crates/neomacs-display-runtime/src https://github.com/eval-exec/neomacs/tree/main/crates/neomac... Emacs, meanwhile, has a 50,000 line file that contains its display and redisplay logic: https://github.com/emacs-mirror/emacs/blob/master/src/xdisp.c https://github.com/emacs-mirror/emacs/blob/master/src/xdisp..... (It's actually a pretty readable well-commented file all things considered, but famously difficult to hack on.)
- bitwize 11d ago
  That's descended from its terminal escape-sequence optimizer, the bit of code that transforms one screen state into another screen state in the least number of terminal commands possible. (That display code was later updated to support graphical output like X11 by treating it as sort of a special case of a terminal.) I think I'd rather have that than the state of the art in "modern" TUIs, which is to do the opposite and treat the terminal as a special case of React canvas, redrawing the whole damn thing every time there is a keystroke or other action by you or the program. You can see Claude Code redraw itself all the time; it's maddening. And the program would absolutely be unusable on, say, a 9600bps connection, whereas Emacs could still get by on that. This is from the company that retains the best and brightest programmers, and will have self-improving runaway genius AI by Christmas, for realsies this time.
micromacrofoot 12d ago
human code gets that way too, it just takes longer

rayiner 12d ago

Have you looked at the code before rendering judgment? It seems pretty readable and well-structured: https://github.com/eval-exec/neomacs/tree/main/crates/neomacs-display-runtime/src https://github.com/eval-exec/neomacs/tree/main/crates/neomac... Emacs, meanwhile, has a 50,000 line file that contains its display and redisplay logic: https://github.com/emacs-mirror/emacs/blob/master/src/xdisp.c https://github.com/emacs-mirror/emacs/blob/master/src/xdisp..... (It's actually a pretty readable well-commented file all things considered, but famously difficult to hack on.)

bitwize 11d ago
That's descended from its terminal escape-sequence optimizer, the bit of code that transforms one screen state into another screen state in the least number of terminal commands possible. (That display code was later updated to support graphical output like X11 by treating it as sort of a special case of a terminal.) I think I'd rather have that than the state of the art in "modern" TUIs, which is to do the opposite and treat the terminal as a special case of React canvas, redrawing the whole damn thing every time there is a keystroke or other action by you or the program. You can see Claude Code redraw itself all the time; it's maddening. And the program would absolutely be unusable on, say, a 9600bps connection, whereas Emacs could still get by on that. This is from the company that retains the best and brightest programmers, and will have self-improving runaway genius AI by Christmas, for realsies this time.

micromacrofoot 12d ago

human code gets that way too, it just takes longer