This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-09-09
Channels
- # admin-announcements (23)
- # beginners (7)
- # boot (6)
- # clara (1)
- # cljs-dev (2)
- # clojure (89)
- # clojure-argentina (1)
- # clojure-australia (5)
- # clojure-brasil (4)
- # clojure-denmark (2)
- # clojure-france (1)
- # clojure-italy (1)
- # clojure-japan (9)
- # clojure-nl (13)
- # clojure-russia (1)
- # clojurescript (248)
- # clojurex (3)
- # clojutre (3)
- # core-async (2)
- # datomic (6)
- # devcards (19)
- # devops (1)
- # events (1)
- # funcool (9)
- # hoplon (74)
- # ldnclj (53)
- # melbourne (3)
- # off-topic (25)
- # onyx (36)
- # reagent (8)
@onetom: would you mind outlining the differences between boot-reload and figwheel and what exactly you mean by losing state in an issue? "* figwheel -> https://github.com/adzerk-oss/boot-reload It's not as smart as figwheel because u can lose state, but it's mostly enough. We are actually quite fine with reloading the page manually most of the time."
@martinklepsch: i can't because i just remember vaguely that boot-reload was simpler and doesn't handle the reload with such granularity as figwheel. it was a conversation on irc with micha. i might remember wrong. tell me more and i will correct what i said.
I haven't used figwheel in a long time so my picture might be inaccurate but the fundamental reloading works as I remember it from figwheel. Css reloading is even simpler. I rarely reload pages.
Figwheel has more bells and whistles but the core functionality should be very similar
Anyway not meant as critique, I think we should steal more things for, figwheel but usually don't get around using it 😝