News for hackers. Stuff that matters.
Re:Duktape: an embeddable JavaScript engine by swah on Thursday December 04, 2014 @03:44PM (#8701508)
IMO the killer app today is compiling React server-side, and fast! I'd use that in Go...
Re:Duktape: an embeddable JavaScript engine by grosskur on Thursday December 04, 2014 @04:49PM (#8701886)
There's also otto, a JavaScript interpreter written in Go:

https://github.com/robertkrimen/otto

Here's an example Go app using otto for React server-side rendering:

https://github.com/101loops/go-reactjs

Re:Duktape: an embeddable JavaScript engine by swah on Thursday December 04, 2014 @07:56PM (#8702585)
Its great but still too slow for that.
Re:Duktape: an embeddable JavaScript engine by xanderjanz on Thursday December 04, 2014 @04:05PM (#8701629)
Sounds like you're looking for Rendr.
Re:Duktape: an embeddable JavaScript engine by reverius42 on Thursday December 04, 2014 @06:30PM (#8702352)
No need for Rendr if you're using React -- React is easy to server-side render on its own (assuming you're already using node on the server).
Re:Duktape: an embeddable JavaScript engine by swah on Thursday December 04, 2014 @04:10PM (#8701650)
Not everyone wants to use Node...
Re:Duktape: an embeddable JavaScript engine by xanderjanz on Thursday December 04, 2014 @04:35PM (#8701795)
Why not use a node script for this one part? Seems to me pretty wise to use a javascript runtime when evaluating javascript. You can still use Go or whatever else for all your other tasks.
Re:Duktape: an embeddable JavaScript engine by swah on Thursday December 04, 2014 @07:56PM (#8702587)
Just simplicity of the deployment. Now I think the right solution is an RPC to a NodeJS server, like you said.