1,007 karma · joined March 23, 2012
Just to be clear, neither I nor Addy Osmani proposed CSS Custom Properties. We're just excited about the feature and sharing it with others. So when people respond negatively to us, it doesn't feel like debating.
The time for debating was when it was being discussed in the working group; before it was implemented in three different browsers.
Also, for what it's worth, not all new JavaScript features are polyfill-able. Proxies, for example, are impossible to polyfill, should they not have been added? WeakMaps are also only partially polyfill-able, are they overdesigned too?
A good example of this is Promises, which are supported in many modern browsers, but not all.
1) Most companies (for legal reasons) don't tell candidates why they weren't offered a job. Maybe it was because of the binary tree question, but maybe it was for some other reason.
2) Homebrew is a Mac-only product, so the likelihood that 90% of Googlers use homebrew is very low. Moreover, Google does not track the software its employees download onto their laptops, so there's no way they would even know the percentage.
https://github.com/philipwalton/flexbugs
A community-curated list of flexbox issues and cross-browser workarounds for them.
Most of the recommendations I make came from learning things the hard way.
As a concrete example, early in my time at this job I needed to make a small CSS change in some template. I made the change, checked it in, and then like 50 tests started failing. I found it absolutely crazy that my changing such a trivial, visual thing would break so many functional tests, so I started suggesting that we not use the same classes for styling as we did for local hooks. I didn't know the word for it at the time, but there was clear coupling between our style and functional classes.
Anyway, it was little things like that, over time, that helped be develop much of my philosophy on this stuff.
CSS Architecture http://philipwalton.com/articles/css-architecture/
Side Effects in CSS http://philipwalton.com/articles/side-effects-in-css/
Decoupling Your HTML, CSS, and JavaScript http://philipwalton.com/articles/decoupling-html-css-and-jav...
This isn't about assigning blame, it's about empowering developers to be able to use flexbox today.
The goals is if you’re building a website using flexbox, and something isn’t working as you’d expect, you can find the solution there.
I can't tell you how many times I've seen back-end engineers hack together a 100+ line JavaScript solution to a problem when one line of CSS would have fixed it.
If you don't know CSS, HTML and DOM very well, then you're probably going to be over-engineering your front-end apps.
If they had, then maybe I'd agree with you, but it seemed like many of them were just going through the motions. It seemed like they interview people all the time.
https://github.com/darcyclarke/Front-end-Developer-Interview...
Also, they flew me up there, so what was I gonna do?
I will say that when interviewing for previous jobs in the past (at smaller companies), I got asked a lot more front-end questions. Maybe it's just a big company problem.
As for the difference, Flexbox is for one-dimensional layout and Grids are for two-dimensional layout.
Grids will eventually be able to do what you now need a flexbox within a flexbox to do, and much more. They'll be especially helpful for layouts that need to be dramatically different across media breakpoints.
Hope that helps!
In classes that are supposed to be global helpers/modifiers, it makes absolute sense to use `!important`. For example, if I have the utility class `.u-hidden`, that selector has very low specificity. But if want to be damn sure that anything I put that class on gets hidden. There's no way to use specificity in this case because it's generalized for use on any website.
This is a common pattern seen in most well architected CSS libraries today.
BTW, I am the they you were referring to :)
The problem is when people use `!important` because they don't understand CSS specificity.