Fork me on GitHub
#re-frame
<
2018-01-12
>
hairfire04:01:10

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!

mikethompson04:01:36

luminus will give you a simple working app, backed by, say, postgres More of a template than a step by step

hairfire04:01:02

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 šŸ˜¬

oliy13:01:37

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?

gklijs16:01:03

@oliy there is #graphql although it's almost exclusive about lacinia

oliy17:01:16

the day8 devs were looking for war stories about introducing graphql, i thought i'd catch them here (maybe another day)

naomarik17:01:36

@oliy iā€™m interested in hearing about your experience, maybe to keep on topic can put it in #graphql ?

naomarik17:01:53

or can just start a slack thread šŸ™‚

escherize18:01:11

Same here šŸ™‚

mikerod18:01:28

Well, a graphql discussion that included its use with re-frame would be interesting here even šŸ˜› (opinion)

oliy18:01:57

Maybe it's just a blog post I need to write!

oliy18:01:16

We are using it with re-frame, I wrote a couple of libraries to help ease the transition

oliy18:01:14

I think it probably is worthy of a blog post, I'll see if I can find time soon!

mikethompson21:01:32

@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)

mikethompson21:01:19

And yet the piece which explores the issues/problems of a new technology (in a balanced way) is absolutely gold.

mikerod21:01:24

@mikethompson that was well said. That should be recorded somewhere šŸ˜›

mikerod21:01:01

I like the breakdown of why it is often the case that things are presented/written about benefits

mikethompson21:01:01

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. :-)