วีดีโอ

I've been interested in learning Clojure for some time but have struggled with adapting to the repl based environment and slow start up times from the JVM. Babashka has been a gateway drug for me into the Clojure world and I'm grateful for the work borkdude has done to make it more accessible to beginners like me

5:50 that is also what the so called property-based testing (PBT) is about.

Clojurescript should change direction and follow this guy. As of now clojurescript is pretty useless coz it doesn't support ES6 property and interop with existing js libraries is a nightmare. Clojurescript is a stupid failure because it can't make use of the js ecosystem natively. Someone should fire the clojurescript leadership team for heaven's sake.

I wonder, if the reason for Java UI libraries being slow is actually JNI. In this case, HumbleUI will hit the same limitations eventually. Notice, that so far we have either native code desktop frameworks (like QT) or Browsers/Electron where the interpreter calls built-in functions to update an intermediate representation which is then again processed by native code.

A tool emitting modern readable Javascript code from Clojure? Awesome!

>focus on data privacy 😂 nice joke

TIL Vite is pronounced "veet", it's French for "fast"

Racket is the Lisp/Clojure-like language which is tailor made for creating DSL's. They call it the Language-Oriented Programming Language.

Repl is Life, I will give a try om humbleui

I know nothing about Java and barely anything about Clojure, but this is too cool! I'm going to try and build a simple gui I need in Clojure instead of slapping it together in PySimpleGUI

Awesome 😎

I love repl

can't wait to try it. anyone have a link to a sample app?

Love how you did the slide deck in Humble UI itself, and becomes apparent only halfway in the talk! :-D

A few months ago I developed an internal app using HumbleUI. It was really easy and the results were great. A fantastic experience then, and it's only improved since.

The squint compiler output size is awesome! I'll finally be able to the Codingame seasonal challenges using Clojure (sending the compiled JS to their platform, cause their support for Clojure is terrible)

Awesome, thanks for this talk.

This is one of the best design talks I have ever listened to. I was thinking for very long time about why constraints let someone produce better programs. The relationship between constraints and better predictions is an invaluable insight.

This is really good. It reminded me of when I was learning BASIC back in the 1980s - so much of that was about doing type-in programs that someone else had written, usually with some bugs, usually a game. It's tried & tested!

Great video, but I would add a correction on re-frame regarding 26:32. As you said, the reason you do that encapsulation in Java is because you want to ensure the state of the class is private, and you do this by ensuring that it is only accessible through methods, so that state updates are controlled. The alternative is that multiple classes can access and write to the fields directly, which means you have shared mutable state and the obvious dangers that go with that. In re-frame, this is not even a possibility because you never access state directly. The unidirectional data flow, going from view -> event generation -> state change -> updated view, does the same thing as encapsulation. It ensures that state updates are controlled because the only way to modify state is to fire events and have re-frame itself coordinate the actual changes. It's identical to the reducer model of Redux, where you end up collecting state changes and applying them at the same time. I know it "feels" or "seems" like you are modifying state directly, but this is the reason you have to write subscriptions and events and so forth. It's so that the architecture can handle this for you in the background.

Thanks for this talk, although at minute sixteen the code seems only half visible

Great!

This is beautiful. The talk is easy to follow and mind-blowing, especially graph reconnecting and connecting two different graphs part. And the questions from audiences are also helpful, indicate they already had some insight on GraphQL already.

I love Mr Batsov's presentations and work, he's a true soldier!

Excellent talk

Nice talk! Cleared the clouds in my mind about some of these things. Unit testing inherently is more *white box* than system testing, which is ultimately what we want. We wanna answer the question, "does the software do what we want for the business?", and system tests are also far less brittle. My belief in example based unit tests has lowered. Dev-time instrumentation and automatic checking of function specs mostly obviates the need for example based unit tests.

Amazing talk

This was one of the best talks i ever watched

The slides: speakerdeck.com/phillipmates/how-we-test-at-nubank-dcd-2018

Very usefull! Thank you! I wished there was also a bit about how to use clojure REPL with Java apps

Awesome talk and presentation Phillip! Working with 'flow' integration tests is really easy and gives a nice code coverage. Great to see these test libraries as open source.

Hello! if you like to see the sources from this presentation, check it at: github.com/wilkerlucio/clojure-days-clojure-graph-presentation/blob/master/src/clojure_graphs_presentation_demo/indexes.clj

"all or nothing" is what author of mount mentioned. He told mount is a library while component is a framework. So it may be easier to start using mount in existing app.

I wonder if NomNom is still staying on Clojure. :)

Does anybody have a link to the integrant talk he mentions?

Just enlightening!!! Thank you!

Very interesting talk, especially the rebuke of this tendency to represent all data in 2D frames instead of representing the data how it wants to be represented, as structured and possibly nested collections. Funnily enough it reminds me of Hadley Wickham's recent talk where he seems excited about the idea of representing nested structures inside data frames in R. I will look into Huri more. I hope some more infrastructure comes to Clojure, we need an Rstudio clone, statistics, machine learning, visualisation libraries or ports, and functionality like knitr to build automated report workflows, and we need it to be easy: install clojure, install the IDE, everything integrated, and that's it. Then it takes off.

Slides are here bit.ly/onyx-clojure