I would separate this out into two separate issues; an ismorphic node app and a
unified api. Graphql can help on the later, but it doesn't provide the former.
If you have the former already, switching to Graphql shouldn't be that huge an
effort methinks
M
--
Note that posts from new
Conceptually, my sense is that there's no reason that Relay wouldn't work with
Reagent right out of the box. It may, however, require that you define your
components as React classes. In that case, what you'd have is something that
looks a whole lot like om-next with Relay replacing
You might consider looking at some of the latest stuff happening within the
React and Elm communities with respect to animations. There's an excellent
presentation from React Europe on animations here:
https://www.youtube.com/watch?v=1tavDv5hXpo
One interesting quote from a former Apple UIKit
What problem are you looking to solve here?
My take is that immutability is a design pattern rather than something enforced
by the language constructs. If you want the language constructs to enforce
immutability, Haskell is an excellent choice. Even Elm (a Haskell like
language) treats
@colin Couldn't agree with your comments on remote working more. The challenge
for many early stage companies is that they require incredibly high levels of
communication to be on the same page.
I also think part of the remote/onsite issue is the difference between
efficient and effective.
@Khalid check out
https://github.com/savaki/reagent-nodejs
It's 100% Node/JavaScript, no Nashorn and the majority of the code is used on
both server and client side. I opted to separate the small server/client stubs
into separate directories, but I suppose there's no reason it couldn't be
Double plus plus what @matthew said
M
--
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
Unfortunately, Google's not the only search engine out there. And while they
are dominant, 2/3 of web searches go through them, why should I leave out the
remaining 1/3 because it's more technical challenging? Also, as vertical
search engines become more prominent, why would I want to make
I think maybe the easiest solution is to write simple luggable wrapper to bring
their own router. I would hate to have to bring in an entire framework like
rendr or not be able to use a library just because of my router choice.
M
--
Note that posts from new members are moderated - please be
I briefly tried Clojure on the server side, but I ended up deciding that Node,
despite its immaturity was more comfortable for me. In general, my problems
were:
Developed felt sluggish:
* Very long boot time - cold boot, including cljs compile but not downloads,
compile is over 1min compared
Like I said in the other post, I'm not really keen on using something besides
reagent render pages. Having two ways to render the home page seems like
unhappiness waiting to happen.
Also, having only the home page renderable doesn't give me the SEO benefits I
want. I need the detail pages
Like I said in the other post, I'm not really keen on using something besides
reagent to render pages. Having two ways to render a page seems like misery
waiting to happen.
Also, having only the home page renderable doesn't give me the SEO benefits I
want. I need the detail pages to be
Awesome, thanks!
M
On Tuesday, April 21, 2015 at 4:17:30 PM UTC-7, Mike Thompson wrote:
On Wednesday, April 22, 2015 at 6:18:34 AM UTC+10, Matt Ho wrote:
First off, thanks for putting together such a wonderful framework in
reframe. We've been using it pretty extensively and loving
First off, thanks for putting together such a wonderful framework in reframe.
We've been using it pretty extensively and loving it. One question came up
recently though.
Subscribing to an event is straightforward enough, but how do I unsubscribe?
Specifically, when the component that's
Check out https://github.com/savaki/reagent-nodejs
It uses reagent with nodejs, but the technique should work on on as well
M
--
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
We ended up with a similar path with other folks that posted. We started with
Om, but found it brought with it a lot of incidental complexity. Switching to
Reagent has been very simple and we've been very happy with the transition.
For us, the code is understandable quickly, feels like less
I have a toy application written using reagent and cljs-ajax. The application
works with the hard coded state that I initialized with, but now I'm trying to
retrieve the state from the database on load.
Here's what the state looks like originally:
(def calendar-state (atom {:entries [
17 matches
Mail list logo
