This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-02
Channels
- # announcements (3)
- # aws (8)
- # babashka (87)
- # babashka-sci-dev (3)
- # beginners (34)
- # calva (35)
- # clerk (2)
- # clj-commons (47)
- # cljdoc (10)
- # cljs-dev (21)
- # clojure (19)
- # clojure-android (1)
- # clojure-austin (2)
- # clojure-europe (30)
- # clojure-nl (1)
- # clojure-norway (67)
- # clojure-uk (9)
- # clojuredesign-podcast (7)
- # clojurescript (24)
- # code-reviews (20)
- # cursive (6)
- # datomic (12)
- # emacs (14)
- # events (1)
- # fulcro (7)
- # gratitude (1)
- # hoplon (8)
- # hyperfiddle (23)
- # juxt (22)
- # meander (11)
- # nyc (3)
- # overtone (2)
- # podcasts-discuss (1)
- # reagent (3)
- # releases (1)
- # sci (27)
- # shadow-cljs (73)
- # squint (4)
- # thejaloniki (3)
- # xtdb (7)
What are the implications of the Sci build of Hoplon?
using Hoplon and/or javelin in Nbb scripts in Node.js context (cmd line, repl)?
Use in Scittle web page as drop in without cljs pre-compile (also allowing runtime eval of hoplon code, for userland extension)?
Embedding hoplon in custom sci runtime.
The implication of the SCI config in sci.configs for hoplon is that SCI-based projects could potentially add Hoplon without any further configuration. This is just one such example: https://babashka.org/sci.configs/?gist=e83da19df3d2739861334171779f79d5 Anyone can make their own projects with SCI. If hoplon/javelin will be added to nbb/scittle is based on frequent requests, I'm not usually adding anything without getting requests for those since I can't possible add the whole CLJS ecosystem This is why I made a plugin system for scittle such that you can make your own version of scittle with your favorite libraries mixed in. This is a demo with datascript which isn't in the normal scittle distribution https://github.com/babashka/scittle/tree/main/plugins/demo Hoplon users can make their own scittle + hoplon this way
👍 Thanks for clarifying, and for this work. Hoplon on was my first Web framework, and it’s cool to see it getting more care recently!
@U09D96P9B Are you still using it? Or what are you currently using? I’ve been all-in with reagent and re-frame, but I’m keeping an eye on hoplon as a possibility for an upcoming project.
I haven’t been using it actively. I have it going on a side project I want to update soon. For a while there was some build anxiety, but that’s being resolved now by @U05094X3J . I’ve mostly been doing backend work, and never went down the React/Reagent rabbit hole. I currently want to continue avoiding the reported complexity of React ecosystem, though it does seem to be the most supported path. I have a new project with Biff that I’m trying out. Biff uses HTMX, but can swap in cljs as needed, so I may migrate to that. The Dumdom project also has an interesting alternative take, but does not cover reactive state in iteself. I have been fascinted by Kenny Tilton’s work on #matrix , and was re-assured by him of some of Hoplon’s architectural progressiveness when he pointed out the importance of “fine-grained reactivity” (reactive rules on attributes, not just whole components), and that Hoplon supports this. I am also eager to try out Electric as a full-stack reactive ui framework. My previous Hoplon project was client side only.