Om Next - David Nolen

Channel:ClojureTV · Length:46:18 · Published:2015-07-07 · Views:44348

Watch on YouTube

Summary

David Nolen presents Om Next, the redesign of the ClojureScript Om library, drawing on Relay, Netflix's JSONGraph and Datomic. He covers the tradeoffs in handling the client-server boundary over immutable data.

Why HN recommends it

HN commenters recommend it as the lead ClojureScript developer's own account of Om's evolution, one-way data flow and single-state design.

David Nolen does a great job talking about the trade offs and the evolution of everything in this talk — HN, 2015

Functional programming · Web development · Software architecture & design

Subtitles (excerpt)

um om next uh so uh this talk is about M um uh but it's it's actually there are much bigger ideas than M uh if you're not using M um hopefully there's a lot of things you can take away uh I think uh the way that we design applications uh specifically how we design applications that involve clients remote clients mobile clients you get radically simpler uh and so even if you don't decide to use z uh I think there a lot of ideas you can take away uh I can't spend too much time on how M works today uh because there's just too much stuff to cover but that's okay um again there there there are principles at play here that are much broader than oh specifically okay so the story so far um it's been 16 months since 's first released uh there are tons of users there's large projects I've seen projects with like you know 10 to 20,000 lines of code of closure script which is a lot of closure script so it's it's doing well um you know the one of the big Ideas though wasn't just to get people to adopt oh right that's om was is as much an idea as it was a library um it was to demonstrate to sort of the closure and closure script community at large that there was a more idiomatic approach to uh user interface development um that it was possible to do

On Hacker News

I have nothing to say on Lein vs Boot, but I'm a long-term emacers with > 10 years and I can't endorse Cursive strongly enough. I've got easily at least 1k hours in my .emacs.d. Suffice it to say, it takes a lot to take away from Emacs/SLIME. Never bought into the Textmate hype during the Ruby days, or the SublimeText hype subsequently because Emacs already had all that functionality if not out o… — iheartmemcache, 2015-12
Sorry if it wasn't apparent but I agree / advocate strongly for what you mention, and we use that model at my company. If you look at how Om evolved though, it started out with that simple model of passing the state object down to child components. Then cursors were implemented to make it easier to pass around parts of your global state without having components needing to know everything. GraphQ… — lsdafjklsd, 2015-08
> ...but right now we're focusing on building stuff instead of playing with languages Which is exactly what's so compelling with regard to ClojureScript and say Om or any one of the React wrappers out there: you guys already use Clojure and ClojureScript and its libraries are incredibly pragmatic and designed for "real work". CoffeeScript would seem more like language play than ClojureScript, but… — llambda, 2015-09
Any idea why they decided to use string-based queries for GraphQL? I feel something that can be composed programmatically without having to deal with string concatenation like Falcor's queries or the Datomic Pull syntax proposed in Om Next [1] could be more flexible and robust. I may be missing something. [1] [VIDEO] — lewisl9029, 2015-08

Related videos