Fork me on GitHub
#ldnclj
<
2016-01-04
>
agile_geek08:01:07

Morning folks

thomas09:01:18

Morning everyone...

pupeno09:01:44

Good morning.

mccraigmccraig14:01:09

afternoonz y'all

mccraigmccraig14:01:24

@malcolmsparks: i live in the hope that too much programming doesn't cause detached retinae simple_smile

agile_geek14:01:52

@mccraigmccraig: don't think there's a causal relationship?!

malcolmsparks14:01:30

@mccraigmccraig: I don't think it does!

mccraigmccraig14:01:31

(no, there is no causal relationship - there is a causal relationship from being short-sighted though)

agile_geek15:01:14

Hmmm, I started writing code at age 13 and became short-sighted at age 15. However first year of coding was on a teletype outputing on paper so maybe it only took a year of staring at a screen!

jamiei16:01:00

Slightly off topic, but is anyone else struggling to get to grips with om next? I can't really seem to join the dots.

agile_geek16:01:30

I struggled with Om, I haven't had the courage to tackle Om Next yet!

xlevus16:01:57

ReFrame. ezpz :P

jamiei16:01:23

Yeah, I've turned to looking at reagent and re-frame instead..

jamiei16:01:04

On next is exceedingly clever, far too clever for the likes of me simple_smile

agile_geek17:01:42

However, I strongly suspect this is a 'simple, not easy' thing. I.e. in the long run Om (Next) is simpler (less accidental complexity) but not easy? I have no empirical evidence for this however.

agile_geek17:01:40

So (maybe?) anything beyond a trivial app would be worth the investment in Om (Next)?

agile_geek17:01:20

Someone with real world experience of Om (Next) and Reagent/Reframe want to chip in?

mccraigmccraig17:01:33

@agile_geek: i've got lots of re-frame experience now - re-frame is pretty darn simple - it's very easy to grok and to reason about it's behaviour and to inspect what's going on

mccraigmccraig17:01:37

it doesn't help you out with higher-level 'component' like abstractions and code organisation, which can make growing an app from small to medium a bit awkward as you have to figure out your own conventions

jamiei17:01:56

makes sense from what I've read from others

mccraigmccraig17:01:30

there's no great magic required though, and it's by far the nicest ui dev experience i've ever had

jamiei17:01:33

Thanks @mccraigmccraig , will start off with something pretty trivial and see how I get on from there

mccraigmccraig17:01:27

@jamiei: that's the way to go - the examples around are fine to get started... after a while you will find you want to split your subs and handlers and views into separate namespaces, but you kinda need a feel for your app before you figure out how to do that, so no point worrying about it at the start

mccraigmccraig17:01:35

@jamiei: do schema-check your app-db on every update (with a middleware) while developing though - it catches loads of slippery bugs

jamiei17:01:26

@mccraigmccraig: Good advice on the splitting. Sometimes you need to make mistakes before you understand how to split the app properly anyway.

jamiei17:01:00

Also on the schema check, are you using something Schema for that?

mccraigmccraig17:01:59

yeah, i'm using prismatic schema... i've got all my schemas in .cljc files so they get shared between front and back-end

mccraigmccraig17:01:23

and i'm also using schema-coercion with a JSON API, to check and coerce everything coming off the wire, so i get richer datatypes (i.e. #inst, #uuid etc) for almost zero effort

mccraigmccraig17:01:59

(yada also does the reverse on the server-side - the api spec is used to coerce the JSON)

jamiei17:01:05

Ah, very handy

jamiei17:01:22

How have you found yada? I haven't had time to try that yet

mccraigmccraig18:01:18

generally excellent - a few bugs, but @malcolmsparks is quick to assist, and the concept is well thought-out and overall it's been a much easier ride than i expected (to create a fully async server-side)

mccraigmccraig18:01:17

i haven't tried the latest release yet, but i imagine that the ride is only going to get smoother from here on in

glenjamin19:01:16

AIUI Om next is a good solution for the problem of a large app where components have broadly varied data sources

thomas21:01:59

Om Next feels very clever indeed...

thomas21:01:26

but it feels like it addresses problems I don't even know they exist.