However, Angular was designed from the beginning to support Web Components. They even ship their own Shadow DOM emulation. In other words, when Web Components are ready, only Angular is specifically designed to use them. This is another reason that we are building many of our own components on Angular’s infrastructure, so that when Web Components are ready, our own leap won’t be nearly as far.
I’ve been creating sites since before CSS was in existence, so I’ve seen a lot of new trends, frameworks and the like come and go in that time. Not all of them have been bad, but a lot of them, mainly frameworks, have only made HTML or CSS even more complicated.
Let me tell you a secret: CSS is NOT a programming language. The beauty of CSS is that it’s so easy for almost any to pick up quickly and read (though it’s very difficult to actually use it properly for the big stuff). Adding a preprocessor on top just needlessly complicates and adds yet another piece of bloat to an already over bloated workflow.
Famo.us is similar to Twitter Bootstrap, but instead of being a framework for building websites, it’s a framework for building apps in 2D (like normal apps) or 3D. The big thing famo.us solves is PERFORMANCE for web app development.
Currently, the most popular library for working with SVG is Raphaël. One of the primary reasons Raphaël became the de facto standard is that it supports browsers all the way back to IE 6. However, supporting so many browsers means only being able to implement a common subset of SVG features. Snap was written entirely from scratch by the author of Raphaël (Dmitry Baranovskiy), and is designed specifically for modern browsers (IE9 and up, Safari, Chrome, Firefox, and Opera). Targeting more modern browsers means that Snap can support features like masking, clipping, patterns, full gradients, groups, and more.