This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-26
Channels
- # aws (1)
- # beginners (15)
- # boot (30)
- # cider (13)
- # cljsrn (16)
- # clojure (458)
- # clojure-dev (15)
- # clojure-france (131)
- # clojure-greece (124)
- # clojure-korea (2)
- # clojure-spec (42)
- # clojure-uk (115)
- # clojure-ukraine (1)
- # clojurescript (103)
- # component (18)
- # cryogen (1)
- # datomic (4)
- # dirac (3)
- # figwheel (1)
- # funcool (13)
- # hoplon (60)
- # luminus (2)
- # off-topic (2)
- # om (28)
- # onyx (45)
- # parinfer (28)
- # pedestal (1)
- # proton (23)
- # re-frame (18)
- # reagent (36)
- # ring (1)
- # ring-swagger (5)
- # untangled (13)
- # vim (9)
I am also fighting those kind of UX designs.. Pretty annoying sometimes 😞
Yeah basically..
Do you guys have plans for a server rendering story btw? Was wondering about that because it seems a pretty good idea for a full stack framework
@mitchelkuijpers i would think someone else would write it, heck hasnt @anmonteiro already written it?
https://github.com/ladderlife/cellophane https://github.com/omcljs/om/pull/764 https://anmonteiro.com/2016/09/om-next-server-side-rendering/
apparently it’s already in om!
our SPAs are not directly accessible as websites, so I don't care about search engine indexing, and the load speed is fast enough from a single js file. Just doesn't make sense to allocate cycles to it