<p>I currently have a Go server that sits in front of a Node.js server whose sole purpose is to render React Components to strings, which it sends back to Go to template and serve. </p>
<p>Being a fan of "less moving parts" I was wondering if there was a way to have the Go server do the server-side rendering of the JavaScript instead of needing Node.js in the background?</p>
<hr/>**评论：**<br/><br/>shazow: <pre><p>I haven't done it myself, but take a look at this project: <a href="https://github.com/olebedev/go-starter-kit" rel="nofollow">https://github.com/olebedev/go-starter-kit</a></p></pre>ryokuichigara: <pre><p>Yeah, I looked at this and apparently duktape is a bit behind in terms of performance. While I don't need a 1:1, it's apparently a 1:5 on a good day :<</p></pre>mmmmmmmmmmz: <pre><p>For Node.js-like performance rendering React.js templates, I highly recommend using this Go V8 binding: <a href="https://github.com/ry/v8worker" rel="nofollow">https://github.com/ry/v8worker</a></p>
<p>The engine used in that starter kit (duktape) is great for getting started quickly because it's embedded, but performance-wise V8 seems to blow everything else out of the water.</p></pre>ryokuichigara: <pre><p>I actually fan across this as well; I'll definitely look into it. Thanks for the validation!</p></pre>xyproto: <pre><p>Could Algernon be what you are looking for? It can render JSX to JS and is easy to get started with.</p>
<p><a href="https://github.com/xyproto/algernon" rel="nofollow">https://github.com/xyproto/algernon</a></p></pre>ryokuichigara: <pre><p>I'll definitely look into this, thanks!</p></pre>Fwippy: <pre><p>There's also <a href="https://github.com/robertkrimen/otto" rel="nofollow">otto</a> for a native Go solution, which might simplify your deployment. It might not be as well optimized as some of the more battle-tested javascript implementations (V8), but it's probably worth a look.</p></pre>ryokuichigara: <pre><p>Mmkay, I'll give it a peek, thanks!</p></pre>
