@dnolen: ok thanks. I’ll keep that in mind.

is it possible to use something like radium with om, so that I can keep my component styles inline?

thinking about a new namespace that provides the bootstrapped functionality

will probably provide analyze, emit, eval, and some basic compiler environment constructors

all of these will be based on strings

load-file or something like it will be bindable thing

thinking everything should probably be async, so file loading is possible in all contexts

less concerned about awkwardness of async due to core.async

(go (let [result (<! (eval-chan "(+ 1 2)"))] (js/alert result)))

feedback on this welcome which is why I’m mentioning here it

ideas for what this namespace would be called also welcome

relevant tickets http://dev.clojure.org/jira/browse/CLJS-1336, http://dev.clojure.org/jira/browse/CLJS-1337

@dnolen: why string based eval?

I like painting bikesheds. How about strap?

@jonas: because there no such thing as files or any kind of standard I/O in JavaScript?

pkobrien: candidate one

cljs.cljs? I like the idea of using async throughout.

@dnolen: I was thinking eval should be form based (no IO) as in clj

This part is the most fun. I love naming things. Domain names, modules, repos.

@jonas oops, right sorry just wasn’t clear about that

@dnolen: Here's one ripe with subtlety: affirm

analyze (string), eval (form), emit(AST -> string)

dnolen: that makes sense

@dnolen: I wonder how much emit could be modelled on http://clojure.github.io/clojure/clojure.core-api.html#clojure.core/compile

since compile <-> emit is kind of the same thing here

@jonas: anything that relies on I/O is out of scope for what I’d like to implement

I/O is something for other people to sort out

ok, since there’s no standard to rely on

@wildermuthn: yeah thought about that too :)

Weird file name cljs/cljs.cljs heh

Might be a bit too cute

cljs.meta-circular, cljs.meta ?

My hunch is that the fact that it's meta-circular matters more to you, @dnolen than it does to people who'll end up using it. Besides, cljs.meta is a really special namespace — we might want to save it for some sort of giant space laser that connects a REPL to the metaverse computer.

Personally, I'm fond of strap or bootstrap

cljs.self ?

Maybe self?

HA!

whoa

Um.. Hi @magnars. Feel like playing the lottery?

ergo

nice!

I think we blew our chances

cljs.this, cljs.that hah

@magnars: ha, thought about that one too.

I do quite like it.

:thumbsup: to self

self is pretty cool

@ivanreese and I blew our chances at a winning lottery ticket for self, so it must be. 😇

Agreed

And it's not like anyone is going to be implementing a Self compiler in CLJS, right?

Because that might inspire someone to create a JS compiler in CLJS.. and then.. a CLJS compiler in CLJS..

Which would be ridiculous.

So after watching dnolen's om.next video, and a few talks on falcor & relay, I think I "get it" in regards to querying the server for data, but I'm uncertain what an idiomatic way of sending requests to the server to update data would look like. Are there any existing ideas of what this will look like? I think that is what was being referred to by the first To Do item at https://youtu.be/ByNs9TG30E8?t=1862 ?

@shofetim: it’s not something that is done explicitly same as Relay

it's something handled under the covers by whatever store you plug in.

Are there any existing demo stores?

The stores will be plug-able in om.next?

(Sever side it will, but it seems like this has to be client side?)

There’s a demo store here: https://github.com/omcljs/om/blob/master/src/om/next/stores.cljs

@shofetim: they already are pluggable, but there needs to be more baking.

@angusiguess: @dnolen Thank you, that puts me on the right track.

I’m a bit heads down with bootstrapping and getting that into a release, once that’s out of the way Om Next will get fully baked at a fast clip

Thank you. I've used om and like it, but Om Next looks like what I've been searching for, for the last 3-4 yrs, and I concur that the ideas are just not present in academia.

cljs.inception (idea stolen from Chrome devtools inception)

cljs.to-be-or-not-to-be

cljs.gerund

lol

cljs.ouroboros cljs.<-

cljs.<!

+1 for cljs.inception (assuming we get unlimited votes)

cljs.go

doh! we already have that in core.async

cljs.begin

cljs.therefor-I-am

Yes, cljs.descartes has a nice ring

cljs.I-compile-therefor-I-am seemed too long

cljs.bootlace

hi, does destructing a vector in cljs differ from how it is done in clojure ?

cljs.jscl

I’ve got this simple bit of cljs - in advanced mode this throws a RangeError: Maximum call stack size exceeded

https://www.refheap.com/106291

said bit of cljs ^

with :optimization :none, this goes through just fine.

what’s going on ?

and this is what I did in the console: https://www.refheap.com/106292

even if I avoid destructuring and use (nth coll 1), it falls apart. any ideas ?

cljs.jot-clips-recur

More serious: cljs.script