Thomas Heller

You should also consider the approach chosen by `om.dom` (and others) where you'd write `(dom/div nil "foo")` instead of `[:div {} "foo"]`. The `dom/*` functions can directly create a `ReactElement`...

{} is a constant and doesn't allocate.

Yes, you are doing an unfair comparison. 13+14 call a function which allocates a new map 1000 times. The app-16 doesnt do that.

I have a use case where HTTP/2 support would be very useful. There are several HTTP server instances `shadow-cljs` (build tool for CLJS). All for development purposes. One for each...

I've been thinking about similar things recently regarding my own experimental react-less [framework](https://github.com/thheller/shadow-experiments) and I'm somewhat at the same point you were at years ago. Currently I'm also choosing the...

I do agree that having the `:re-frame.core/event-id` in the map itself is very useful at times, even if just for debugging purposes. A quick `dissoc` (or helper fn) for cases...

@mike-thompson-day8 funny enough thats the same issue I'm currently mulling over in my framework. I actually want events themselves to be "declarative" when defining the DOM. So instead of ```clojure...

Yeah, I played with SharedWorkers but given their state I opted not to use them for the UI. IMHO the neo.mjs takes this way too far too. First of all...

@mainej events are always dispatched to the component first. If that component does not handle the event it keeps going up the component tree to the root. The event handler...

Please verify that you are actually starting the shadow-cljs version you think you are starting. `2.16.+` should defintely have the fixed version and not attempt to connect to `localhost`. You...