| Please note a lot of our focus on performance is around server side rendering (universal js/ isomorphic js). I'm trying to write a blog post around our performance improvements on a per module basis (it takes time to get good data and writing good content is hard :D). You can use these specific SSR performance enhancing modules without the rest of Electrode: http://www.electrode.io/docs/above_fold_rendering.html http://www.electrode.io/docs/server_side_render_cache.html http://www.electrode.io/docs/redux_router_engine.html I agree, there are tons of platforms and when your starting out fresh, it's difficult to grasp the millions of ways to do things. We tried to focus heavily on documentation and building an application together for the folks that are new to the ecosystem. If you look at our docs, we try to build an application with you and we break it down from basics (get app running and deploy), to more intermediate (make plug ins, add routes, we will add material UI docs), to more advanced (lets do SSR rendering, above the fold rendering only, etc). For small apps, we try to have a more barebones app using `yo electrode` instead of the boilerplate (which has everything), and get you deployed to Heroku or Google Cloud quickly (our docs break down how to do it, step by step). The big thing we are missing for folks that are new to the ecosystem is what's inside our archetype and what goes inside a production app (the webpack configs, linting, css modules, and so much more). We are working on this part. The benefit of WalmartLabs backing this project and actually using it internally to power walmart.com (and samsclub.com + grocery.walmart.com next year) - we are extremely sensitive to breaking changes. If we release a breaking change, we hear lots of groans around our desk and a line of folks expressing themselves :). |