You don't have to use server-side rendering. You can have the React client make ajax requests to your Go backend.
On Monday, February 6, 2017 at 12:09:10 PM UTC-5, 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.
