Both React and Angular are quite new to the scene and there doesn&#x27;t seem to be any sign of the industry settling on either (although the enterprise is currently betting on Angular). They are designed first and foremost to make the architecture of large sites&#x2F;apps manageable, particularly where JS is heavily used. React succeeds at this aim. Angular fails miserably and actually makes everything worse (which is probably why the enterprise chose to go with it).<p>Toolkits of the kind you&#x27;re looking for (ExtJS&#x2F;Dojo etc) just haven&#x27;t really taken off. ExtJS suffers from having an all or nothing approach to its usage, and last I checked its approach left much to be desired. Dojo is a bit more flexible in that sense but both libraries are big and complicated as they have to do a lot of work to achieve the behaviour they require of the browser.<p>Browsers simply aren&#x27;t designed (still!) to provide the grid-like layouts required by apps. It&#x27;s generally best to avoid the complexity required to do this unless you have no choice.<p>Flexbox promises to make grid layouts much easier. I have to admit, the last time I tried to work with it I found it quite difficult to get to work for me.<p>Web components promise to raise the number of available HTML elements by creating your own. The are indended to help you move from code like `$(&#x27;.datepicker&#x27;).datePicker()` to HTML like `&lt;datepicker &#x2F;&gt;`.<p>Fundamentally, there is not going to be a standard way of doing things on the web because there is no such thing as a standard website. When you visit a website today, you could be visiting an API, an RSS news feed, a database interface), a drawing package, a computer game, etc.<p>Such diversity of applications requires a diversity of tools and approaches, and that is what we are seeing a proliferation of today as we explore and discover the most successful ways of providing digital content.