More toolsets seems like the wrong way to me. The reason is that browsers barely even keep up with the current ones or even old ones. Also browsers work becaus

More toolsets seems like the wrong way to me. The reason is that browsers barely even keep up with the current ones or even old ones. Also browsers work because of standards. It's not about the "best", but about agreeing. Recently I see many people trying to make one suboptimal thing by starting from scratch, removing all standards compatibility, throwing away all the knowledge that went in to a thing to make this one single thing work better, resulting only in incompatibilities, non-standards-conformance and making everything else than that one thing harder or even impossible. You can see this with web frameworks, with system tools, etc. Usually this stems from people knowing how to use stuff, but not understanding concepts or why things are the way they are. This is actually also true for CSS. CSS was meant to support all kinds of output devices, regardless of being graphical or not, support screens in all sizes and nowadays people use it to only really support a low number of "pixelperfect" screen sizes with default settings. Everything else is completely broken. Nobody even bothers to look at new CSS3 features, new HTML 5 elements (unless it is for SEO), etc. In the end nobody is interested in implementing it correctly which usually results in standards to only slowly advance and having individual vendors only implementing their favorites or even their proposals and experiments, rendering the standard itself unusable, because of it being implemented by one single vendor. In the end we live in a world where the only thing that's really common inside the infrastructure are hacks to work around those problems. Most developers hoped this would change after Firefox ate a big part of IEs market share, but currently it seems to be repeating. Btw. I am not excluding myself from these things. I don't actively work into other directions and basically do the same things. Before you disagree: If you have something about CSS in your resume. Did you ever even completely read through CSS standards?