Live data from Hacker News

Try Clojure

tryclojure.org

401–404 of 404 posts

Re: Try Clojure

#401

Earlier quoted context omitted.

And if you do need to touch Java for reasons Clojure doesn’t impose, the interoperability story is really good. I’ve done this with internal libraries - it’s easy to get them pulled into a Clojure code base, wrap them in such a way that the ergonomics of the rest of your code aren’t ruined, and still treat them as a first class citizen for stuff like your build system, artifact stores, etc.

Clojure 1.12 (which is nearly done) is going to add a bunch of interop support - method values, array class syntax, Clojure fn -> Java functional interface conversion, stream support, etc.

Yes — and thank you for this work! Java functional interfaces were the only thing I was wishing for in the Clojure/JVM story. They will help me simplify code that interfaces with FoundationDB.

Re: Try Clojure

#402
post #396

Earlier quoted context omitted.

> I believe that your interpretation of what’s actually happening is what’s baloney. I'm actually quoting Prof Andrew Appel of Princeton: https://www.cs.princeton.edu/~appel/papers/ssafun.pdf You seem to think that functional programming and in-place updates are mutually exclusive. This is not the case, e.g. Haskell supports mutation as a tracked and controlled side-effect. It can even give static guarantees that a f…

I don’t really care which functional programming advocate you’re quoting. They’re all liars when they make these claims. You can say SSA, static guarantees, internal mutability, blah blah blah all you want. When third party, not specifically chosen anecdotes to make FP look good, measurements stack up to the claims, we can have a better conversation. It’s not looking good though, cause these claims of “actually, Hask…

[deleted]

Re: Try Clojure

#403

Earlier quoted context omitted.

the tooling is the reason i gave up when i was interested in learning clojure. everywhere pretty much said that emacs was the "correct" editor to use for clojure, i tried it out for a bit but ultimately learning a new language and a new editor at the same time was just too big of an ask. i tried calva with vscode afterwards but it was basically the same thing, calva has paredit which overrides the keyboard navigation…

Wow. I'm the creator of Calva and I can tell you that I do not have an opinion on how to use it. I would never say something like that, and now I wonder what I could have said that was interpreted this way... By default Calva Paredit overrides three or so keyboard shortcuts. This is to help the users to not accidentally delete brackets, which in turn keeps the support questions down about broken Clojure code. I have…

i'm pretty sure this is the thread i saw, but at the time it hadn't been closed yet: https://github.com/BetterThanTomorrow/calva-paredit/issues/1...

if there's now a way to disable paredit entirely then i might check it out again some time in the bear future

Re: Try Clojure

#404
post #38

That's a great introduction, but... how to do an if statement would've been cool to add in the tutorial.

What is this "statement" you speak of? (if (= 2 2) :OK :nope)

see, that was missing from the tutorial, or did I miss it? :ok and :nope - are those valid keywords or functions?
Post reply on HN