This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-26
Channels
- # aws-lambda (15)
- # babashka (7)
- # beginners (124)
- # calva (7)
- # cider (19)
- # clj-kondo (26)
- # clojure (261)
- # clojure-australia (3)
- # clojure-dev (10)
- # clojure-europe (45)
- # clojure-nl (4)
- # clojure-uk (6)
- # clojurescript (10)
- # datomic (7)
- # depstar (7)
- # emacs (11)
- # fulcro (41)
- # graalvm (48)
- # helix (1)
- # honeysql (17)
- # inf-clojure (7)
- # introduce-yourself (3)
- # jackdaw (2)
- # lsp (36)
- # malli (2)
- # meander (2)
- # membrane (1)
- # missionary (11)
- # off-topic (17)
- # pathom (83)
- # polylith (15)
- # re-frame (31)
- # reagent (42)
- # sci (35)
- # shadow-cljs (13)
- # spacemacs (13)
- # sql (19)
- # timbre (3)
- # tools-deps (77)
Sweet! I'm curious if that's going to be possible to have the same UI codebase both for JVM and web
While dart/web is not our primary goal we have designed hashes and bitops to work with uint32s to be safe.
Not sure what that means :) If not dart/web, then what's the main goal if you don't mind sharing details?
I was confused by the fact that you were talking about the JVM and the web. So I assumed Dart VM and the web. :man-shrugging: Primary goal is mobile. Integers don’t behave consistently on mobile and web (mobile you have int64, web you have whatever JS gives you) so we take care to work at the intersection of both even if dart/web isn’t our main goal. (Edited as the message was sent too early.)