This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-12
Channels
- # arachne (1)
- # aws (2)
- # beginners (123)
- # boot (22)
- # boot-dev (8)
- # chestnut (3)
- # cider (38)
- # clara (36)
- # cljs-dev (148)
- # clojars (2)
- # clojure (76)
- # clojure-austin (2)
- # clojure-greece (1)
- # clojure-italy (6)
- # clojure-russia (5)
- # clojure-spec (8)
- # clojure-uk (65)
- # clojurescript (45)
- # core-async (38)
- # cursive (9)
- # data-science (5)
- # datomic (28)
- # docs (1)
- # emacs (2)
- # fulcro (34)
- # hoplon (18)
- # jobs-discuss (7)
- # keechma (8)
- # lumo (5)
- # om (3)
- # onyx (31)
- # parinfer (1)
- # pedestal (1)
- # re-frame (20)
- # reagent (5)
- # ring-swagger (16)
- # shadow-cljs (56)
- # spacemacs (11)
- # specter (8)
- # sql (5)
- # unrepl (29)
- # yada (6)
I'm doing Lunch-and-Learn sessions at work teaching Clojure(Script). So far we've done a lot of Clojure, and the team is interested. Now I want to move into "full-stack". Any suggestions on step-by-step tutorials with re-frame front-end, Clojure back-end and push from the back-end to the front-end? I've looked for some time now, and I haven't found much. Thanks!
luminus will give you a simple working app, backed by, say, postgres More of a template than a step by step
Thanks mikethompson, that's what I've found. It's kind of frustrating to talk about how great Clojure(Script) is, and not find any straight forward way to get into Full-Stack š¬
hi guys i saw @danielcomptonās question about graphql and what the experience is like. at my job we recently introduced it and are still spreading it through the application. is here a good place to discuss?
the day8 devs were looking for war stories about introducing graphql, i thought i'd catch them here (maybe another day)
@oliy iām interested in hearing about your experience, maybe to keep on topic can put it in #graphql ?
Well, a graphql discussion that included its use with re-frame
would be interesting here even š (opinion)
We are using it with re-frame, I wrote a couple of libraries to help ease the transition
@oliy thanks! While we are interested in the positives, its probably the negatives/difficulties that we're most interested in because they are under-documented. As RH says: > Programmers know the benefits of everything and the tradeoffs of nothing. Early on with a technology, there's often breathless praise about the benefits, but very little about the tradeoffs or problems, because: - no one knows them yet, too early in the adoption process - it isn't cool to talk badly about the new thing you love - survivor bias - only those that principally see benefits (and not tradeoffs) decided to proceed to use the technology - it depends on your terms of reference. "problems" compared to what? You have to know at least one other approach well, to criticise the new approach. It requires a lot of experience and it is a difficult piece to write. (And thankless, because everyone wants to write the breathless excitement piece)
And yet the piece which explores the issues/problems of a new technology (in a balanced way) is absolutely gold.
@mikethompson that was well said. That should be recorded somewhere š
I like the breakdown of why it is often the case that things are presented/written about benefits
Thanks. Although, I'm thinking of writing a piece on the downside of ever trying to be wise. I'll contrast it to the alternative "over-confident bluster", which, frankly, is probably a superior technology for use on the Internet. :-)