For "discovering namespaces of (unloaded) dependencies". As they mentioned, I extract that information from the JAR files. With Emacs/Cider it's quite convenient: `cider-open-classpath-entry` -> quickly filter the dependency and open it -> you will see the content of the JAR file including the clojure files which you can simply open; typically there's also a README file that you can examine. It works really well for things like compojure. It can be used for java dependencies as well but all you get is a list of class files (you could disassemble those but that's rarely useful).
About the formatting-friendly (comment... ) block (th-cam.com/video/gIoadGfm5T8/w-d-xo.html ): another tip is to end it with *e, the symbol which names the last thrown Exception. I personally do it this way, because for some reason inspecting the last thrown Exception is something I need to do quite frequently ;)
54:17 about the name of this "interactive comment" pattern. I realized that the theoretical foundation of this thing might be "The Explicit-Control Evaluator" from SICP 2e Sec 5.4, because exactly what you do is to manually control the evaluator to interprete your source codes beyond the normal opearations of Clojure automatic tool chain. Oh my JVM, the lisp machines are back. Hence, the title may also be dubbed "Turning JVM(or node) into a Modern Lisp Machine".
Also in Sec5.4.1, one can read "The central element in the evaluator is the sequence of instructions beginning at eval-dispatch. " And I can see VSCode is the GUI for this eval-dispatch, while emacs could be the TUI.
Thanks Sean for being such a pillar of the community. Love your work!
For "discovering namespaces of (unloaded) dependencies". As they mentioned, I extract that information from the JAR files. With Emacs/Cider it's quite convenient: `cider-open-classpath-entry` -> quickly filter the dependency and open it -> you will see the content of the JAR file including the clojure files which you can simply open; typically there's also a README file that you can examine. It works really well for things like compojure. It can be used for java dependencies as well but all you get is a list of class files (you could disassemble those but that's rarely useful).
There are so many invaluable tips here. Thank you very much to all the contributors.
About the formatting-friendly (comment... ) block (th-cam.com/video/gIoadGfm5T8/w-d-xo.html ): another tip is to end it with *e, the symbol which names the last thrown Exception. I personally do it this way, because for some reason inspecting the last thrown Exception is something I need to do quite frequently ;)
Is there a short expression for that `doto tap>` trick at @39:05 in a thread-last macro? I don't want to write ` ((fn [x] (tap> x) x))`all the time.
54:17 about the name of this "interactive comment" pattern. I realized that the theoretical foundation of this thing might be "The Explicit-Control Evaluator" from SICP 2e Sec 5.4, because exactly what you do is to manually control the evaluator to interprete your source codes beyond the normal opearations of Clojure automatic tool chain. Oh my JVM, the lisp machines are back. Hence, the title may also be dubbed "Turning JVM(or node) into a Modern Lisp Machine".
Rickey also mentioned once the reason why JVM support is better than CLR is because of the meta programming support of JVM.
Also in Sec5.4.1, one can read "The central element in the evaluator is the sequence of instructions beginning at eval-dispatch. " And I can see VSCode is the GUI for this eval-dispatch, while emacs could be the TUI.
Can you share your local aliases and .clojure stuff. To learn more about clojure cli configuration you are using?
in the description it has his GitHub, the conf should be there
Oh my God..... I'm switching to clojure
Can you remaster the audio,it is horrible to listen.