Usually in the morning. The more I am throughout the day, the more tired I am, and the quality of my code resembles this.

If I develop, let's say, an S3 based piece of code, I should of course have to reweite it one I decide to move away thar feature dlfrom S3 and use another service from another vendor, that will have a different API. You could see my question as: is there a real risk to move away my application from AWS? Am I risking too much by leveraging AWS services that much?

Trying to force usage of a language/framework to fit it in every situation, instead of understanding that often one kind of job has its preferred tool.

Subversion (SVN) and CVS are both VCS (Version Control System, as @sandeep says) or SCM (Source Code Management) systems. Other SCMs are Perforce, Mercurial, Git, Microsoft SourceSafe, Microsoft Visual Studio Team System... and probably others I forget :)

Uhm, probably my idea won't work now that I think about this. I forgot about the Shadow DOM that would prevent the class to be applied. I'm sorry!

Why don't you dinamically apply a class element (e.g. style-0, style-1, etc.) on the body and then work on CSS inheritance rules?

Yes, it's huge. But it's so because it's a framework who goes to cover a lot of aspects of implementing a modern SPA. In React, how many modules you do have to bring in and make them coexist in order to achieve the same functionalities? Beware, I'm not saying that the Angular's approach it's better that React's. In fact, as everything in life, there's no universal "best way", it all depends what you need to achieve. I'm sorry if you got offended about the fanboyism stuff, but believe me, you really sounded like one, just trashing a framework with a 5 lines answer and a link. I'm no Angular fanboy either (even if I worked and I am still working with Angular 1 as of now, and only have a theoretical overview of React), and if you read carefully my previous comment you can easily understand that I didn't even mention Angular, so how can I be defending it? ;) In the end, I absolutely agree on point 5. That's why I see no sense in defending or attacking one particular technology, and again, I'm not defending or trashing anything here. And, of course, I'm sorry if I misunderstood your answer.

If you "don't know what", how can you even elaborate an educated answer? Please bring your deductions and proof to the table, or just keep your React fanboyism out of here.

For sure it's complicated, but this in my opinion is because Web Development has become the "lingua franca" of software development; the fact that, thanks to responsive design, one could develop the same (or a big part anyway) software for both mobile and desktops is a huge plus, and this helped this paradigm to spread anywhere, increasing use cases and peculiar scenarios. However, I honestly don't agree with the "over": it depends on what you need to achieve, and what your constraints are. As everything in life, the secret is to find the perfect equilibrium.