I actually agree with this. I don't think Relay will overweight REST.
On Monday, February 9, 2015 at 5:00:41 PM UTC+2, marc fawzi wrote:
As an engineer, you have to make compromises. You can't cover all edge cases
and scenarios. It's more likely that your system will fail because it's too
I’m working on an Om application that includes a music browser and player with
a simple artist - albums - songs hierarchy. When a user is viewing an artist
section I layout all the artist’s albums and songs hierarchically and this
works great since there is basically a 1-to-1 correspondence
We have node cli templates, is there a lein template somewhere for a cljs app
targeting nashorn/rhino as a runtime?
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
I required something like this as well and made it by directly uploading to S3
with some minimal server side component.
Wrote two posts about it:
http://www.martinklepsch.org/posts/using-coreasync-and-transducers-for-direct-s3-upload.html
Not that I'm aware of. I'm also happy to take ClojureScript patches
supporting the :main pattern for these.
David
On Sun, Feb 15, 2015 at 10:39 AM, Ivan L ivan.laza...@gmail.com wrote:
We have node cli templates, is there a lein template somewhere for a cljs
app targeting nashorn/rhino as a
If they were changing, you could implement your own reference system, where you
have one stateful lookup map that you make globally available via a ref cursor.
Instead of the actual changing values, you'd use lookup keys in your rendered
cursors. Changes to values in the stateful lookup map
My approach to this stuff is to think in terms of state and derived state.
I have a few helpers to facilitate implementing that which amounts to
- Use an atom for state
- Use a function to derive state
- Use a simple cache to reduce load of derivation in render loop
- Hack deref to
The problem is `download` property that gets munged in advanced
compilation.
You can use `aset` to prevent it from being munged:
(aset lnk download filename)
or alternatively provide extern file to tell Closure compiler not to munge
it:
function HTMLLinkElement() {}
