5 ms·

http://www.electrode.io/index.html http://www.electrode.io/index.html > "Electrode is a platform for building universal React/Node.js applications with standar

http://www.electrode.io/index.html http://www.electrode.io/index.html > "Electrode is a platform for building universal React/Node.js applications with standardized structure, best practices, and modern technologies baked in. Electrode focuses on performance, component reusability, and simple deployment to multiple cloud providers—so you can focus on what makes your app unique." Sounds like the missing piece of the puzzle everyone's been waiting for?

groundhogday1 10y ago
Isn't this what Rails did/does?
- tracker1 10y ago
  Rails will load the above the fold content and render server-side, while allowing the rest to render client-side, do component level render caching on the server, and allow for client and server rendering with one codebase?
tracker1 10y ago
The complexity isn't likely completely free.. but could be incredibly useful for a lot of universal rendering scenarios... the above the fold content loading, and the component render caching server-side is particularly interesting. Now if Walmart.com just didn't look quite so hideous... but that's another issue... The tech stack for electrode is definitely interesting, and looking forward to playing around with it.
- alexgrigoryan 10y ago
  I hope you like it! I personally think that the above the fold content, server side caching, and redux-router-engine will make a positive impact on the server side rendering react community. We saw HUGE gains in performance using these. We are working on a blog post that goes through the performance numbers we saw on the live site. I also think Electrode Explorer will be popular for bigger companies that have many components. http://www.electrode.io/docs/electrode_explorer.html http://www.electrode.io/docs/electrode_explorer.html P.S. I'm from the Electrode team.
  - tracker1 10y ago
    Thanks for the reply, yeah, from what I've read and seen so far it definitely looks interesting... And seems to resolve a lot of the issues I had very early on with ismorphic^wuniversal rendering back when Yahoo's fluxible app had just come out. The render caching seems very cool as well, making up for the general double-render for fetching data triggered from the component. Right now at the day job I'm stuck in angular 1.x hell, though my contract is up in a couple weeks and looking for something in the React space again. Too much angular work in Phoenix to avoid completely though. Aside: wish I could get a hold of a hiring manager there if you have space for new people, have never even gotten a callback from walmart labs, and would love to work for your org.
    - alexgrigoryan 10y ago
      Your contact information is in your HN profile, I'll have our recruiters ping you with the opportunities we have available @WalmartLabs.
      - tracker1 10y ago
        Added more contact info, thanks... I'm @tracker1 on github and npm as well.

groundhogday1 10y ago

Isn't this what Rails did/does?

tracker1 10y ago
Rails will load the above the fold content and render server-side, while allowing the rest to render client-side, do component level render caching on the server, and allow for client and server rendering with one codebase?

tracker1 10y ago

The complexity isn't likely completely free.. but could be incredibly useful for a lot of universal rendering scenarios... the above the fold content loading, and the component render caching server-side is particularly interesting. Now if Walmart.com just didn't look quite so hideous... but that's another issue... The tech stack for electrode is definitely interesting, and looking forward to playing around with it.

alexgrigoryan 10y ago
I hope you like it! I personally think that the above the fold content, server side caching, and redux-router-engine will make a positive impact on the server side rendering react community. We saw HUGE gains in performance using these. We are working on a blog post that goes through the performance numbers we saw on the live site. I also think Electrode Explorer will be popular for bigger companies that have many components. http://www.electrode.io/docs/electrode_explorer.html http://www.electrode.io/docs/electrode_explorer.html P.S. I'm from the Electrode team.
- tracker1 10y ago
  Thanks for the reply, yeah, from what I've read and seen so far it definitely looks interesting... And seems to resolve a lot of the issues I had very early on with ismorphic^wuniversal rendering back when Yahoo's fluxible app had just come out. The render caching seems very cool as well, making up for the general double-render for fetching data triggered from the component. Right now at the day job I'm stuck in angular 1.x hell, though my contract is up in a couple weeks and looking for something in the React space again. Too much angular work in Phoenix to avoid completely though. Aside: wish I could get a hold of a hiring manager there if you have space for new people, have never even gotten a callback from walmart labs, and would love to work for your org.
  - alexgrigoryan 10y ago
    Your contact information is in your HN profile, I'll have our recruiters ping you with the opportunities we have available @WalmartLabs.
    - tracker1 10y ago
      Added more contact info, thanks... I'm @tracker1 on github and npm as well.