> And then having a common app structure with thousands of other people that can provide help and insight. You don't think that there are thousands of people w

> And then having a common app structure with thousands of other people that can provide help and insight. You don't think that there are thousands of people who can provide help and insight into the standard Web & DOM API's? I mean, do you in all seriousness think that there are more people that can help you with React than it is that can help you with the Web & DOM API? Not to mention the standard browser libraries have decades worth of documentation and information about them, freely available. > * client side router * data transportation/cache layer * view layer * model layer * build pipeline Let's narrow that down a bit: client-side router - There's examples online of a router that's 20 lines[1] data transportation/cache layer - Umm, what? The browser already takes care of data transportation (also known as the HTTP protocol, WebSocket protocol or WebRTC - whichever floats your boat). Surprisingly, it also takes care of caching as well. view layer - if you absolutely need one, here[2] - 2KB and has everything you need. model layer - `class Model { ... }` and `let model = new Model('path/to/component')`. Simple as that. build pipeline - don't really need to "build" thanks to HTTP/2. Otherwise if you want to transpile anything you could always just setup a single-line `npm run build` script. > You people really are kidding yourselves. I feel bad for whoever is paying your salaries. Why can't you try to have a friendly discussion instead of attacking on a personal level as you've done countless times throughout the comments. Nobody's pointing a gun at you. [1] - http://joakim.beng.se/blog/posts/a-javascript-router-in-20-lines.html http://joakim.beng.se/blog/posts/a-javascript-router-in-20-l... [2] - https://github.com/pakastin/frzr https://github.com/pakastin/frzr