News for hackers. Stuff that matters.
Re:React v0.11 by arianvanp on Thursday July 17, 2014 @05:19PM (#8050242)
Great stuff. I really love React. Especially stuff like server-side prerendering of the DOM is extremely cool.
Re:React v0.11 by swah on Thursday July 17, 2014 @05:23PM (#8050262)
But that assumes a world where everyone uses Node :)
Re:React v0.11 by swannodette on Thursday July 17, 2014 @05:28PM (#8050276)
React server side rendering doesn't require Node. Works just fine with Java 8's Nashorn too.
Re:React v0.11 by fiatjaf on Thursday July 17, 2014 @10:40PM (#8051409)
Re:React v0.11 by Touche on Thursday July 17, 2014 @07:16PM (#8050788)
Awesome news. Not enough resources on Nashorn out there.
Re:React v0.11 by fidlefodl on Thursday July 17, 2014 @06:11PM (#8050530)
Fwiw, i use serverside React rendering with a Golang API server. My JS code has an interface layer which interfaces to browser/node, and on first load a balancer throws the request to Node, which makes local API calls to the api server, and renders it all in node.

Technically i use Node, but only to implement a small interface layer for things like http requests. So i don't really consider it a Node app. The real code is all React and Golang.

Re:React v0.11 by juliennakache on Thursday July 17, 2014 @11:46PM (#8051568)
Awesome stack. It's exactly what I've started working on lately. I have 2 questions for you :) 1. What router do you use for react as it's necessary if you want multiple entry points into your app ? Rrouter seems promising. 2. How do you elegantly proxy client cookies from your node app to your api ? (both way: read and writes) Thx!
Re:React v0.11 by compedit on Friday July 18, 2014 @03:27AM (#8052044)
If you've ever used Ember's router and liked it, I'd suggest the react-nested-router[0]. So easy to use

[0] - https://github.com/rpflorence/react-nested-router

Re:React v0.11 by jjsz on Wednesday July 23, 2014 @09:39PM (#8077848)
Do you happen to have a boilerplate of your stack on github?
Re:React v0.11 by baddox on Thursday July 17, 2014 @10:30PM (#8051377)
It only assumes a world where everyone uses JavaScript. And in this context, "everyone" is web developers, so it's a fair assumption.
Re:React v0.11 by poseid on Thursday July 17, 2014 @05:36PM (#8050331)
maybe not yet, but I just wrote a blog post why in the future here: http://radar.oreilly.com/2014/07/next-generation-web-apps-wi...
Re:React v0.11 by Dewie on Thursday July 17, 2014 @07:04PM (#8050750)
100% javascript, that would be living the dream......
Re:React v0.11 by andybak on Thursday July 17, 2014 @07:13PM (#8050781)
Is my sarcasm meter on the blink again?
Re:React v0.11 by notduncansmith on Thursday July 17, 2014 @07:22PM (#8050810)
I don't know, but this subthread is off the charts on the Poe scale.
Re:React v0.11 by Dewie on Thursday July 17, 2014 @07:40PM (#8050878)
violent beeping
[deleted]
Re:React v0.11 by Dewie on Friday July 18, 2014 @05:16AM (#8052239)
Woah, where did Haskell come from all of a sudden?
Re:React v0.11 by ebiester on Thursday July 17, 2014 @06:22PM (#8050582)
The JSX translation shouldn't be too hard to write a binding. I know that it happened with mustache. Now, it would mean keeping it in sync, but it might not be a bad idea for people outside node and the JVM.
Re:React v0.11 by fiatjaf on Thursday July 17, 2014 @10:58PM (#8051460)
What should we do with all the Javascript code between the brackets?
Re:React v0.11 by polskibus on Friday July 18, 2014 @02:43AM (#8051958)
There's a ASP.NET MVC plugin for server-side rendering of React http://reactjs.net/