I don't see a reason why it wouldn't work, but I don't recommend it

@carocad ^^

two reasons: I feel that component is overengineered for frontend use, and ClojureScript is inherently async (you need to build up state as data comes in)

I think it imposes the wrong structure on an async app

@pesterhazy thanks for the feedback. I dont have much frontend experience, which is why I am asking. However when I see the current template my skin shivers from the spaguetti I see in a near future 😕

IMO better to build up some spaghetti, then refactor

you have no way of knowing what exactly you'll need - only the path your development takes you can tell

chances of guessing the right abstraction up front are not great

based on that argument the opposite is also true 😉. I mean the current templates already have an abstraction up front. https://clojurians.slack.com/archives/C0E1SN0NM/p1510665326000061

i made an app-context builder which is async and cljs compatible @pesterhazy @carocad https://github.com/employeerepublic/deferst

(i only made it cljs compatible recently though, so it hasn't seen heavy cljs use yet - it's had very heavy clj use and will be getting a lot of cljs use soon)

@mccraigmccraig thanks for the recommendation. I will check it out