React is one of many client side (browser) JavaScript frameworks for building user interfaces.
JSX is not required when using React, but is recommended as it gives you the full power of JavaScript to describe your rendered HTML. Node is not required. If you're using Go, use it to build a server-side JSON API and, optionally, act as your web server. Our last project was a Go based API service with the HTML/JS/CCS served-up by Caddy (a web server written in Go). On the client side we used VueJS, one of the bazillion alternatives to React. It's all works quite well, and I would recommend a similar approach for those looking to use a Go based solution. i.e. Go JSON API services with your web server and JS framework of choice. -- Kevin Powick On Monday, 6 February 2017 12:09:10 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.
