はてなブックマーク

Warning: experimental stuff ahead. Make sure you know more about running Rails in production than I do before you take this & run with it. Source on GitHub Here's my favourite slide from Pete Hunt's JSConf EU talk on React (which you should totally watch). If you render a React component with the same data, it will always return the same result. It makes absolutely no difference whether you do tha

TL;DR multiple classes is ok, but restrict yourself to a single modifier class and a single state class or state data attribute per element:

Originally posted as “Goodbye Compass”, but that made it sound like I was glad to be rid of it. Compass is an amazing framework with a lot of thought behind it that made my life easier for years; the emergence of other tools certainly doesn’t change of that! Around this time last year I threw together Style, a starting point for scalable, maintainable CSS architecture based on work I was doing in

After doing things like this for a while, I've found that it doesn't make long-term maintenance easier and actually slows down development. It depends what you mean by "semantic".For a variable name to be semantic, it must convey useful meaning. For me as a developer, this is anything but semantic: