A little over a year ago, I experimented with server-side React rendering in Go [1] via otto [2].
At least back then, otto wasn't fully ECMA5-compliant due to not supporting negative lookaheads in regular expressions; I had to open a PR on React [3] to remove one negative lookahead in the render path. I have no idea if otto can run the current version of React, and it's been so long since I've tried using otto with React that I won't be able to answer any questions about that setup. Hopefully this was still useful information. [1] https://github.com/mark-rushakoff/go-reactjs-benchmarks [2] https://github.com/robertkrimen/otto [3] https://github.com/facebook/react/pull/5614 On Monday, February 6, 2017 at 9:09:10 AM UTC-8, so.q...@gmail.com wrote: > > Correct me if I'm wrong, but in serving web apps and sites. > > Golang simply fills in the blanks for predefined templates. > > React appears to be a bit more complicated requiring the creation of > JavaScript/JSX classes representing the view. Having that rendered on the > server-side and the difference applied on the client. > > To combine the two, do I need to run Node.js on the server to process the > React/JSX classes before piping the results to Golang for responding to the > client? So Golang would be the conduit/middle-man filling in for Express > here. > > Does this even make sense? If I'm already running Node.js, does the use of > Golang feel superfluous? > > > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
