@danielgrosse: using go macro inside component’s render function looks quite crazy to my eye, I would guess during first component render it just puts internal go representation into that hiccup vector, that is why you are seeing numbers

I would write normal component depending on some data and run this go routine outside render function and update data for the component standard way

@darwin Thanks for your advice. I still have to learn many things.

should a simple reagent app (3-4 components, nothing fancy, no routing) compile to a 443K app.js in :advanced compilation mode?

Doesn’t sound right. Could you post your code?

there's what I think the relevant project.clj bits are.

the (poorly-named) :profiles/production entry just brings in the database configuration that needs to go into the WAR file.

strange. i’m not used to the uberjar, but it looks ok otherwise. what happens when you change the top optimizations to :advanced?

when I run outside of :uberjar the whole thing gets split out and I get all the goog files in their own directory.

given that this is a cljs project, what does the uberjar do for you?

the server side is actually where most of the code lives. lots of Java wrapped in clojure, fronted by a cljs UI.

So 443k is the size of the app.js file?

yes. gzipped, 110k.

Oh, is that with an inlined react.js? Or is that external?

inlined. I also mentioned it over on #C03S1L9DN, and @dnolen seemed to think that wasn't crazy big.

If so, that sounds about right.

cool. glad for the sanity check.

I forget that 400K is still a pretty small load for all the js a page needs.

the minified react.js by itself is already ~120k

So if I call a function that derefs my ratom from a component does that cause the calling component to rerender? or is it just if I deref the ratom in the component itself?

If the function that derefs your ratom is called from within the render phase of the component, the component should re-render

ok thanks

Np