HNHacker News
TopNewBestAskShowJobs

philipwalton

1,007 karma · joined March 23, 2012

submissionscomments
philipwalton··on The Google Analytics Setup I Use on Every Site I Build
analytics.js falls back to the older methods in unsupporting browsers.
philipwalton··on Houdini: Maybe the Most Exciting Development in CSS
No, that is an accurate impression. The ultimate goal of Houdini is to give developers the tools to innovate; unlike the current situation were all innovation happens at the spec level, and devs have to wait (often years) for browser adoption.
philipwalton··on Why I'm Excited About Native CSS Variables
> I guess that depends on how you define debate. I'm referring to that the proposal is made and some people show their distaste for part of what is proposed. Those that made the proposal respond. I see no resistance to the feature being introduced in that, just disagreement on a part of the proposal.

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.

philipwalton··on Why I'm Excited About Native CSS Variables
Polymer partially polyfills CSS Custom Properties: https://www.polymer-project.org/1.0/docs/devguide/styling.ht...

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?

philipwalton··on Why I'm Excited About Native CSS Variables
I don't see a lot of "debating" going on. If you want to point me to some constructive debates, that would be nice.
philipwalton··on Why I'm Excited About Native CSS Variables
Indeed! That's why I wrote the article :)
philipwalton··on Polyfills as a Service
No, the point of this tool is that some browsers require a polyfill, and some don't because the feature is natively supported. A transpiler like Babel cannot possibly determine that, so it has to be safe and include polyfills for all features used in the code it's transpiling, reglardless of whether or not the browser you're using already supports the feature.

A good example of this is Promises, which are supported in many modern browsers, but not all.

philipwalton··on Google: 90% of our engineers use the software you wrote (Homebrew), but...
The tweet starts out: "Google: 90% of our engineers...", which implies that this is information Google told him.
philipwalton··on Google: 90% of our engineers use the software you wrote (Homebrew), but...
My main complaint with the tweet is that it's almost certainly speculation.

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.

philipwalton··on Solved by Flexbox
When you use gutters sometimes the math doesn't work out quite right. http://codepen.io/anon/pen/xGEMYY
philipwalton··on Solved by Flexbox
Solved by Flexbox creator here. I wanted to add that if you're using flexbox today, you should also check out this other repo of mine:

https://github.com/philipwalton/flexbugs

A community-curated list of flexbox issues and cross-browser workarounds for them.

philipwalton··on Rent Control Creates Higher Rents in SF
The assumption is that without rent control, average prices would be lower. Therefore someone who couldn't afford to move previously now could.
philipwalton··on Ask HN: Front-end “design patterns”?
Honestly, at my previous company I worked as the sole front-end engineer on a team with mostly classically trained programmer types (all CS majors), and it started to become very obvious that the "traditional front-end best practices" for CSS weren't going to cut it for us.

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.

philipwalton··on Ask HN: Front-end “design patterns”?
This topic interests me as well, and I've written about many of these ideas in the past. They're not necessarily analogous to the GoF design patterns, but I think they're similar in spirit. I hope you find them helpful.

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...

philipwalton··on Flexbugs: a list of flexbox bugs and cross-browser solutions to them
Flexbugs creator here. For what it's worth, all of these bugs have been fixed in the tech preview of Internet Explorer 12. Also, my co-maintainer (Greg Whitworth) is a member of the IE team, and he's been as adamant as anyone that we educate people on the shortcomings of older IE versions, so we can all build better websites.

This isn't about assigning blame, it's about empowering developers to be able to use flexbox today.

philipwalton··on How to write better, more cross-browser flexbox code
I've also created a Github repository called Flexbugs: a community curated list of cross-browser flexbox issues and their known workarounds. https://github.com/philipwalton/flexbugs

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.

philipwalton··on Getting to work on diversity at Google
As a Google employee, the reasons I hear is that we'd like the diversity of our workforce to more accurately reflect the diversity of our users, so we can serve them better.
philipwalton··on Reference - HTML 5 Elements list
This is great. So is Josh Duck's period table of elements, which is mentioned in the footnotes:

http://joshduck.com/periodic-table.html

philipwalton··on Interviewing as a Front-End Engineer in San Francisco
Post author here. I agree 100% that HTML and CSS are not programming languages. However, any application that you build on the front-end is going to require your JavaScript code to interact with the HTML and CSS, so a solid understanding of how all the pieces fit together is crucial.

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.

philipwalton··on Interviewing as a Front-End Engineer in San Francisco
Yes, I provided a detailed resume as well as my Github account for all of these. The problem is it didn't seem like the individual interviewers had taken much time to actually look at what I'd done.

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.

philipwalton··on Interviewing as a Front-End Engineer in San Francisco
Related, I just found out that Darcy Clarke put this list together of good front-end interview questions. I would have included it in the article if I'd known about it ahead of time.

https://github.com/darcyclarke/Front-end-Developer-Interview...

philipwalton··on Interviewing as a Front-End Engineer in San Francisco
To be honest, I was actually having a good time. I'm one of the crazy people who likes interviewing. I think it's kind of thrilling.

Also, they flew me up there, so what was I gonna do?

philipwalton··on Interviewing as a Front-End Engineer in San Francisco
Maybe offline. I'm not interested in publicly calling out any companies. I mainly wanted to shed light on the process and my experience.

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.

philipwalton··on Show HN: Myth – CSS the way it was imagined
I agree 100% with Ian. I came here to say the exact thing, but he beat me to it.
philipwalton··on Font Awesome 4 released
In the what's new it says everything has been rewritten. Does this mean the icon vector files themselves or just the CSS?
philipwalton··on Solved By Flexbox – Cleaner, hack-free CSS
CSS Grid Layout is definitely not a dead end, it just didn't have enough support to showcase (yet).

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!

philipwalton··on Solved By Flexbox – Cleaner, hack-free CSS
You're quite welcome. It was a fun project to work on.
philipwalton··on Solved By Flexbox – Cleaner, hack-free CSS
Perhaps if you were my customer, but you're just consuming the free content I've spent a good deal of time putting together :)
philipwalton··on Solved By Flexbox – Cleaner, hack-free CSS
I disagree.

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 :)

philipwalton··on Solved By Flexbox – Cleaner, hack-free CSS
There's absolutely nothing wrong with `!important` if used correctly.

The problem is when people use `!important` because they don't understand CSS specificity.

← PreviousPage 2 of 4Next →