News for hackers. Stuff that matters.
Re:Emacs in the Age of Magic by Animats on Wednesday November 11, 2026 @04:21PM (#50458865)
It's a whole new world.

We need to be thinking about modularity with well-defined APIs now, to isolate the chunks created by AI coding. Maintainabilty requires firewalls.

Re:Emacs in the Age of Magic by globular-toast on Wednesday November 11, 2026 @04:50PM (#50459181)
Isn't that just... software engineering?
Re:Emacs in the Age of Magic by bitwize on Wednesday November 11, 2026 @04:55PM (#50459225)
No, it's:

⟩ Refactor these components into standalone modules that communicate across well-defined APIs. Write the API specifications to docs/API.md. Add a note to AGENTS.md instructing agents to preserve the modular seams and focus work on one module at a time.

Re:Emacs in the Age of Magic by Buttons840 on Thursday November 12, 2026 @12:30AM (#50463405)
It's a weird world where we're refactoring everything, but not just using a type system that can enforce those seams and limitations at compile time.
Re:Emacs in the Age of Magic by q4y2u35uk on Thursday November 12, 2026 @01:18AM (#50463690)
We are though. Why do you think Rust has become the defacto standard for vibe-coding? Most vibe coders can't read a line of Rust, but the strong ML-inspired type system, and also having native performance, is why it is the king of the hill right now.
Re:Emacs in the Age of Magic by throwaway27448 on Wednesday November 11, 2026 @05:23PM (#50459590)
[delayed]
Re:Emacs in the Age of Magic by 0xb0565e486 on Wednesday November 11, 2026 @05:59PM (#50460113)
Strong isolation where it matters, completely free otherwise.