> * What the Second Ideal of Focus, Flow and Joy Means to Me Relearning Coding: How Coding Mostly Left My Daily Life in 2008, But Came Back in 2016 (or If I Can Learn Clojure, Anyone Can)
> * Why I Love LISPs Now
> * Functional Programming and Immutability (and John Carmack)
> * A Mistake I’ve Been Making Since Grad School, and How I Fixed It: Composability
> * The Epiphany I Had Reading “An Introduction to React in 2019 (For People Who Know Just Enough jQuery To Get By)”
> * What Rich Hickey Says About Simplicity: Where The First Ideal Of Locality and Simplicity Comes From
> * Solving Business Problems, Not Solving Puzzles—Why I Detest Doing Infrastructure Work These Days
> * Lastly, the REPL…the Ultimate in Fast and Fun Feedback Loops!
> * The Amazing Clojure Community, Parting Thoughts, and What I’d Like To Write About in the Future
Gene Kim's Clojure example:
; input is JSON string: "{foo: 2}"
(defn xform [s]
(-> (js/JSON.parse s)
js->clj
(update "foo" + 2)
clj->js
js/JSON.stringify))
#lang racket
(require threading json)
; input is (xform "{\"foo\" : 2 }")
(define (xform s)
(~> s
string->jsexpr
(hash-update 'foo (λ (x) (+ 2 x)))
jsexpr->string)) (require [clojure.data.json :as json])
(defn xform [s]
(-> s
json/read-str
(update "foo" + 2)
json/write-str))
I do prefer the ClojureScript because I don't know how to type "λ" and that seems like a usability handicap. Minor complaint I know.
Might someone who's played with both give me some pro's and con's of Racket vs Clojure?
Could you provide some examples of how exactly does building DSLs come into play here? Or could you at least point me to some blogposts that talk about this matter?
Could you point me in the direction of any good resources, libraries, or communities to dig in further?
A small google will take you to plenty of resources and libraries.
Beating the averages: http://www.paulgraham.com/avg.html
Racket web frameworks: https://github.com/avelino/awesome-racket#web-frameworks
I disagree. I rarely find myself slowed down by the grammar or operator precedence in Java and C#. In C++, only when I have to do something rather esoteric (pointer-to-member, member function template specializations, etc.).
On the other hand, I critically rely on types. The IDE is able to narrow down suggestions about applicable methods to a handful. But since `js->clj` is a function `string -> map` (a very generic signature), there must be hundreds of them with the same signature. Context-sensitive discoverability with the help of IDE becomes nearly useless.
Yes, that's how I learn APIs these days. Types, intellisense + reading the documentation to learn about possible edge cases. I cannot imagine being productive in something like Clojure.
I also find Java 11 + VAVR rather pleasant to work with.
Of many languages I used (dynamically and statically typed) Clojure turned out to be the most productive one for me personally.
Nowadays if I have a problem to solve and not allowed to use Clojure, I would still first prototype it in Clojure and then rewrite it in whatever language. I am still faster that way.
Some people would argue that Lisps are optimized for writing, but are difficult to read and maintain. Although I've experienced that to certain degree with other Lisps, somehow I don't feel that is the case with Clojure.