Conversation

Notices

1. Embed this notice
   Boosty Collins (ieure@retro.social)'s status on Thursday, 04-Jan-2024 02:30:34 JST Boosty Collins

   Me: I'd like to add a macro to this Clojure project.
   Kondo: Absolutely not. Fuck you

   • Embed this notice
     tech? no! man, see... (technomancy@icosahedron.website)'s status on Thursday, 04-Jan-2024 02:30:32 JST tech? no! man, see...

     in reply to

     @ieure did you see my post from the other day about how static analysis is inherently in tension with Clojure's macros? https://technomancy.us/200

   • Embed this notice
     Boosty Collins (ieure@retro.social)'s status on Thursday, 04-Jan-2024 02:30:33 JST Boosty Collins

     in reply to

     clj-kondo has never, not even once, sparked anything other than deep annoyance for me.

   • Embed this notice
     tech? no! man, see... (technomancy@icosahedron.website)'s status on Thursday, 04-Jan-2024 03:04:39 JST tech? no! man, see...

     in reply to

     @ieure I think that's an oversimplification; Clojure's macros cause problems because they're allowed to Fire the Missiles; you can build a macro system like Fennel which defaults to being static-analysis-friendly without opening up a can of worms around safety if the macros default to being pure functions

   • Embed this notice
     Boosty Collins (ieure@retro.social)'s status on Thursday, 04-Jan-2024 03:04:41 JST Boosty Collins

     in reply to

     • tech? no! man, see...

     @technomancy No, but I already agree. Static analysis of a dynamic language is not the right approach.