3 ms·
I don't come from a frontend background, most of my experience is just cobbled together websites that use jQuery and maybe a spot of Angular. The myriad of JS
by djhworld 12y ago
I don't come from a frontend background, most of my experience is just cobbled together websites that use jQuery and maybe a spot of Angular.
The myriad of JS frameworks is bewildering to me sometimes.
- tracker1 12y agoAs someone who is trying to keep up with a lot of it, and using node/io.js on the server it's pretty cool and overwhelming at the same time. On the one hand, there is more choice than ever. On the other, there's almost two choices... and when you look one day, and get delayed/deferred for a few months, something you'd written off then deserves a second look. My leanings lately are towards React+Flux-like tools. Using the npm and browserify ecosystem. Which is far better than anything I've used in the past for building web applications.
- mattdeboard 12y agoI also consider myself a backend developer but have written a non-trivial amount of ReactJS code. It is really a pleasure to work with. I highly recommend next time you find yourself having to do something on the front end, use React.
- swah 12y agoAnother guy that enjoys both frontend and backend here. Something that's holding me back on ReactJS is that I'd like to render pages server side, and I don't want to use Node.js, but Go or Python instead.. and there aren't many folks doing this combo. (Maybe the best option is a "render server" in Node.js?)
- mattdeboard 12y agoYeah you would have to dispatch your server-side rendering out to a Node process which probably wouldn't be worth it.