Clojurians Log v2
hoplon
Hello, I will do a release soon, update the demos/docs to the latest version because of new inference warnings and will finally announce the recent changes on #announcements. I was hoping to get something written about how we got where we are at but this will delay the announcement so I think that should be done later.
Ideas I'm thinking about, related to Hoplon: • Adding a new provider that used the browser apis directly so people could not complain about using goog or jquery. • Allowing multiple providers to be used in the same app (if someone knows if that would be a bad idea please tell me 😅 ). My first idea is having different namespaces for different providers instead of using the current multimethod approach. • Documenting/allowing using Hoplon to get small bits of interactivity as described in https://code.thheller.com/blog/shadow-cljs/2023/07/13/the-lost-arts-of-cljs-frontend.html and other posts in that series. Let me know if someone has other use cases or ideas.
Thank you for chiming in. I agree that Hoplon seems a nice fit for bits of interactivity and I will try to find if what already exists works and create a demo project.
A cell macro rewrite not coupled to clj and with a debug output mode. The clj coupled part is the primary scittle blocker afaik
All the other ideas are great too, rock on 👍
If you are interested in smaller bundle sizes, I recommend making loading clojure.spec optional
since loading it pulls in clojure.spec to production code which isn't optimal
these specifically: https://github.com/hoplon/hoplon/blob/3161c08334a98f258a57eb89b0c4d7d1217b03e2/src/hoplon/core.cljs#L13-L14
The shadow-cljs build report will show you how many kb are added because of loading these namespaces
This is a great idea and should be simple to do 👏
I + hi-lighting the small bits approach. This is probably one of Hoplons relative strengths: not demanding a heavier or more complex stack and bundle, while still being idiomatic cljs (not React semantics, or Squint clj->js transpile, or htmx hypermedia patterns, or more intimate dom api + shadow-cljs knowledge….?) I guess the hardest part for me is maybe understanding and wrangling with the various build and packaging approaches (unless that’s all strictly shadow-cljs territory)
Adzerk had a post a long time ago about emdedd hoplon in a regular page. Not sure if that’s relevant
I remembered this https://clojurians.slack.com/archives/C08BDAPRA/p1685979486521819