This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-15
Channels
- # announcements (13)
- # aws (6)
- # babashka (23)
- # babashka-sci-dev (6)
- # beginners (64)
- # calva (110)
- # cider (25)
- # cljs-dev (5)
- # cljsrn (8)
- # clojars (5)
- # clojure (20)
- # clojure-austin (1)
- # clojure-europe (77)
- # clojure-nl (1)
- # clojure-uk (3)
- # clojurescript (14)
- # cursive (7)
- # datahike (9)
- # datomic (13)
- # eastwood (15)
- # emacs (14)
- # figwheel-main (1)
- # fulcro (8)
- # graalvm-mobile (2)
- # graphql (2)
- # honeysql (2)
- # hyperfiddle (2)
- # introduce-yourself (4)
- # jobs (4)
- # joyride (4)
- # leiningen (4)
- # lsp (8)
- # minecraft (8)
- # off-topic (11)
- # polylith (18)
- # rdf (2)
- # reagent (3)
- # reitit (4)
- # remote-jobs (1)
- # shadow-cljs (39)
- # specter (7)
- # xtdb (3)
Would there be an advantage of using GraalVM on Android versus just using the Android runtime and converting the Java classes generated by Clojure AOT to DEX? I read that the Clojure startup time is bad on Android, but all the information I found about that is at least several years old, and the Android Runtime seems to have AOT compilation now. Using the Android runtime would allow you to use the Android API directly and write UI views in Clojure.
Are there any recent example projects that go the AOT to DEX route? It was my impression that the differences with the android runtime were problematic, but I'm not sure about specifics and can't find any good resources. I know that graalvm binaries might have some favorable attributes for running on mobile devices: • faster startup • lower memory footprint