No video :(

REPL Driven Development, Clojure's Superpower - Sean Corfield

Подписаться 3,5 тыс.

Просмотров 20 тыс.

50% 1

Everyone talks about REPL driven development (RDD) but what it is really? Why is the Clojure REPL
not like other languages’ REPLs? Can you really develop an application “live”? What about restarts, refreshes? Don’t I need special, magical tooling for this? This talk will show you how fundamental Clojure’s REPL is to development, and how to build a web application, live, from your editor, with no restarts, no refreshes, just simple, basic tooling.
Clojure’s REPL is truly its superpower:it lets you hold your application in your hand, query it, modify it, evolve it, with just a basic set of tools and an understanding of what “REPL-friendly development” means.
Sean Corfield used to build compilers, virtual machines, databases and
telecom systems but eventually got a real job building web
applications. After eight years of ANSI C++ Standardization and a
decade of web development with JVM-based languages, he finally found
his first love again - functional programming - and for the last
decade he has written Clojure almost every day.
github.com/sea...

Опубликовано:

28 авг 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 12

@diegonayalazo Год назад

Thanks Sean for being such a pillar of the community. Love your work!

@mertnuhoglu 3 года назад

There are so many invaluable tips here. Thank you very much to all the contributors.

@JurajMartinka 3 года назад

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).

@valwaeselynck4529 3 года назад

About the formatting-friendly (comment... ) block (ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-gIoadGfm5T8.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 ;)

@3a146 2 месяца назад

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".

@3a146 2 месяца назад

Rickey also mentioned once the reason why JVM support is better than CLR is because of the meta programming support of JVM.

@3a146 2 месяца назад

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.