This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-21
Channels
- # announcements (17)
- # babashka (2)
- # beginners (51)
- # calva (14)
- # clojure (30)
- # clojure-europe (12)
- # clojure-uk (3)
- # clojurescript (22)
- # cursive (10)
- # defnpodcast (1)
- # etaoin (1)
- # fulcro (7)
- # graalvm-mobile (3)
- # music (1)
- # obb (4)
- # podcasts-discuss (1)
- # sci (2)
- # shadow-cljs (37)
- # spacemacs (3)
- # xtdb (16)
Back to work soon, I wonder if it will be like this... https://superrare.com/artwork-v2/feedback-system-34773 😂
Today I'm writing Clojurescript but it's slowly dawning on me that I now need to understand typescript as well as JavaScript and react. The abstraction has sprung another leak ;-)
To more fully use ClojureScript, the assumed constraint I struggle to overcome is the lack of ClojureScript (or Clojure common) libraries, mitigating the need to reach for JavaScript libraries. Although there are notable exceptions, it does feel that ClojureScript interop with JavaScript makes ClojureScript far more complex, where as Clojure interop with Java makes Java less complex
I totally agree with your complexity and I come down on the side of the UI being more complex than server devs like to admit and JS just being more random than Java. Maintaining an interop lib over JS is inviting 🤕 🤕 🤕
And the response to that complexity for many is TypeScript. Which just adds to the complexity of using ClojureScript 😞