styles

They do cycle their styles, so you might want to stock up if you see something you like.

With the style.css fully cached, I'm getting ~15ms faster on the sideband approach than with inline styles.

Any front-end developer will understand how to extract the styles to a style-sheet.

Was the style you used one of the styles on the American MTV?

One problem with this is that it enforces certain styles upon the programmer.

Semantics in class-names, the choice of inline styles vs style sheet etc.

It just means we have different parenting styles.

There are many styles of dresses with multiple levels of formality.

You will participate in code reviews, help develop our best practices and coding styles, and ultimately have a big impact as our company is starting out.

It's trivial to pull the styles out of that markup.

I think that there's a place for both of these styles in the world.

I agree that there is a place for both styles in the world.

I read the title too quickly as "Microsoft's Aesthetics Armageddon" and was disappointed that the article was not about inconsistent icon styles.

I love specifically that in any silly bikeshed-painting argument about code styles, the answer will be "gofmt is definitive, and this conversation is over".

This means that `<div class="the-actual-element">` goes away, and we are left with a tag name that actually tells you what kind of content there is inside, class names that specify "mixins" to load in styles or event bindings for multiple elements, and the content of the element can be styled in any way.

About violating "some earlier architectural plan" in the case of libraries: Being able to do this allows CL programmers to freely mix libraries with different "architectural plans" without resorting to some half-baked fusion architecture that has to account for the different styles used by the libraries.