Living With Legacy Code

on YouTube ↗35m

" summary

Hiccup implements pre-compilation 10–20x faster by turning literal Hiccup vectors into strings, but that forces a raw-string vs escaped distinction (1.0 insecure by default, 2.0 returns raw strings) and hits a Java method instruction limit for large templates. Ring faces a naming choice: keep legacy unnamespaced keys for compatibility or switch to namespaced keys for clarity; websockets are added using a compromise to avoid breaking users. Renaming an artifact group (medley → dev.weave.medley) permanently breaks dependency resolution: artifact group rename breaks dependency resolution.

AI-written summary · about

" chapters (8)

1. 0:00Introduction and context
2. 1:41Origins of Compojure and Ring
3. 3:55Hiccup pre-compilation
4. 9:16Leaky abstractions in Hiccup
5. 14:48Lessons from API delays
6. 16:57Evolving the Ring library
7. 24:57Artifact naming and Medley
8. 31:09Conclusion and takeaways

" related talks

• 01h 01mGuide to Destroying Codebases the Demise of Clever CodeGabor Varadi · Android Worldwide 2022
• 21m50 Shades of LegacyGregorio Kusowski · Berlin Buzzwords 2019
• 43mPatterns of Legacy DisplacementRob Horn, Ian Cartwright · GOTO Copenhagen 2022
• 28mThe Fellowship of the StringJacques Favreau · CascadiaJS 2021
• 54mThe Future of the Past – Legacy Will Stay With UsCarola Lilienthal · iSAQB Software Architecture Gathering – Digital 2021
• 32mClojure, Java 9, and YouToby Crawley · Clojure/west 2017
• 48mLegacy, for lack of a better word, is goodUberto Barbini · Voxxed Days Bucharest 2018
• 01h 11mClean Coders Hate What Happens to Your Code When You Use These Enterprise Programming TricksKevlin Henney · NDC London 2017