Dylan, When I have more time I can talk about my experience with Pedestal App on mobile html5 apps, but in short: - Lack of visibility into queue states when things go wrong - Main scheduling loop for go loops use setInterval/setTimeout which introduce latency - Ordering of go loop scheduling is not explicitly controllable - Complex topologies can deadlock (in Pedestal App but that may have been a design flaw) - Syntactic annoyance of adding go loops in Om will-mount for "in-tree" IO - Calling a function at a tag is the simplest expression of an event or rpc - Calling functions allow for synchronous or asynchronous handling w/o go loops which is convenient
Many of these things are no problem on desktop sites, but caused us grief on mobile packaged apps (without JIT) where any performance problems are magnified. I just made derive public with the caveat we're at 0.1 and have ideas to tighten it up internally and api-wise for an 0.2 release in the next month or so. But happy to have you take a peek and comment. The nativestore and deps namespace are the interesting ones, and there is a little figwheel based demo / test app in main. -- 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 "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
