This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-03
Channels
- # announcements (1)
- # babashka (22)
- # beginners (176)
- # calva (10)
- # cider (4)
- # circleci (5)
- # cljsrn (20)
- # clojure (28)
- # clojure-europe (11)
- # clojure-italy (5)
- # clojure-nl (5)
- # clojure-spec (1)
- # clojure-sweden (2)
- # clojure-uk (29)
- # clojuredesign-podcast (4)
- # clojurescript (38)
- # code-reviews (25)
- # conjure (1)
- # core-typed (1)
- # data-science (16)
- # datomic (23)
- # figwheel-main (16)
- # fulcro (48)
- # helix (9)
- # jobs (3)
- # juxt (5)
- # kaocha (17)
- # malli (19)
- # mount (9)
- # nrepl (4)
- # off-topic (35)
- # pathom (7)
- # re-frame (28)
- # reagent (26)
- # reitit (1)
- # releases (1)
- # remote-jobs (5)
- # sci (6)
- # shadow-cljs (36)
- # spacemacs (3)
- # sql (8)
- # tools-deps (13)
- # unrepl (1)
- # vim (4)
- # xtdb (8)
Mornin'!
I use them too, they are certainly great - esp as I can eval forms inside of them, in the repl, to try out stuff π
Yeah, I was pleased to see someone had written that up.
my RCB's contain next.jdbc invocations pumping in some data and looking at the results π
My RCB's contain all sorts of stuff. I just committed a big data migration that was written and tested entirely via RDD using RCB's. And I left the whole thing in when the PR went up for review so my colleague could see how I'd evolved the solution and how I'd "tested" it in the REPL.
I used Spec to generate random test data to populate 10,000 rows in each of three tables to act as a test bed for the migration. All in the RCB.
You know what - that's what I do too. I test out stuff in my repl inside rcbs, backed by a few unit tests, and I'm happy to believe that it'll work. I love the rapid feedback.
(s/exercise ::some-spec 10000)
π
Spec is soooo useful for extended example testing!
Laters...
I don't think that's a helpful way to put it, but I agree with the point - my first programming course at university was functional programming in haskell
What surprised me about clojure when I started looking into it was how few language constructs there are. Some basic data types + standard lib and then bit later atoms/refs + async + protocols . It is funny now looking at Kotlin and other languages and see how many keywords and concepts there are to learn.
I would guess most people learning Kotlin will already have paid a lot of the cost of learning it by becoming familiar with Java
Yeah, I have been using Java for a few years but am now predominantly using Kotlin at work thatβs why I used it as an example. I feel the same about C#, Haskell, Typescript and other.
There does seem to be some pain with learning Kotlin - as clunky as it is, I think I'm pretty good at functional-style programming with Java streams (after some horrible first attempts), and then the Kotlin equivalent requires learning a whole new set of functions
Nothing in particular, just a lack of familiarity with what's available, and the best way of doing things
morning