Very good as always. One interesting tidbit about metadata is that is preserves equality. So the number 1 with some metadata is equal to the number 1 with some other metadata.
Awesome video! I found Metadata and Dynamic Vars section especially useful. And a comment, for the -main function, I was thinking that was, to match java function in the generated class. Surprised it's just a convention to make it unique. I find it an odd design decision honestly, complexity for a no good reward, not quite Clojure style
Short, sweet, useful. Very nice, Daniel ^meta is very interesting. I always wondered about that and what uses it can be put to. Please give us a Patreon link to support these awesome Clojure run-downs
As someone who doesn't use Clojure I found this to be a good and helpful overview. I have a suggestion about your `times-fn` example at 6:40. Instead of `(times-fn 1 2 3)` use something different like `(times-fn 2 3 4)` to make the parameter usage clearer because both 2*3 and 1*2*3 equal 6.
There are lots of apps built in Clojure. Not nearly as many as some other languages but still a lot. Dont just use Clojure to use it. See if it at actually has benefits that other languages might not offer. At my company we use Clojure for a bunch of different microservices because repl development makes them quick and easy to test and Clojure is quite performant
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
Just started a job using Clojure after a few years with Python, thank you for being a great help!
Congrats on the new job! 🤘
Very good as always.
One interesting tidbit about metadata is that is preserves equality. So the number 1 with some metadata is equal to the number 1 with some other metadata.
Thats interesting! Thanks :)
Awesome video! I found Metadata and Dynamic Vars section especially useful.
And a comment, for the -main function, I was thinking that was, to match java function in the generated class. Surprised it's just a convention to make it unique. I find it an odd design decision honestly, complexity for a no good reward, not quite Clojure style
Your intro is great !!!
Finally some logic explanations!
Short, sweet, useful.
Very nice, Daniel
^meta is very interesting. I always wondered about that and what uses it can be put to.
Please give us a Patreon link to support these awesome Clojure run-downs
Thanks a lot Peter! Patreon... Maybe one day :p
realy like your style~
Thanks!
The section where you talked about the keyword :this gave me JavaScript PTSD.
😂 this isnt worth it
As someone who doesn't use Clojure I found this to be a good and helpful overview.
I have a suggestion about your `times-fn` example at 6:40. Instead of `(times-fn 1 2 3)` use something different like `(times-fn 2 3 4)` to make the parameter usage clearer because both 2*3 and 1*2*3 equal 6.
Oh yeah :) good point!
Why there is no sound effect in my lein when I typed "on the code again"?
lol!
The "-" actually means something. Read the gen-class docstring.
Is Clojure used in any new projects? My concern is that I can't professionally request this language to any client.
There are lots of apps built in Clojure. Not nearly as many as some other languages but still a lot. Dont just use Clojure to use it. See if it at actually has benefits that other languages might not offer. At my company we use Clojure for a bunch of different microservices because repl development makes them quick and easy to test and Clojure is quite performant
.toUpperCase is not a function, try evaluating it by itself.
I think I didnt make myself clear. Its a method on available on strings