philipwalton

5 ms·

1.
by philipwalton 8y ago
I've updated the article to emphasize that this is indeed something we're experimenting with, and explain a bit more how built-in modules go through the standards process (in general and in Chrome).
2.
by philipwalton 8y ago
Article author here, I probably should have been clearer in the article. I was trying to strike a balance between: - presenting what I believe to be a compelling and exciting possible future for the web (especially considering it has a viab
3.
by philipwalton 8y ago
This is not different from existing web APIs, which are also not versioned.
4.
by philipwalton 8y ago
https://github.com/WICG/import-maps#scoping-examples
5.
by philipwalton 8y ago
There are links to all the standards work in the article. All of the APIs mentioned are going through the standards process.
6.
by philipwalton 8y ago
It's likely not "blocked" by analytics since pretty much all analytics libraries get loaded async. However, scripts loaded before the `load` event do delay the load event, and analytics script are typically loaded with the lo
7.
by philipwalton 8y ago
That 56K number isn't gzipped, gzipped it's only 18K (plus there's also some inline JS, some webpack boilerplate, and then analytics.js). The reason for its size is my site is my playground. It's where I get to experimen
8.
by philipwalton 8y ago
Right, when I said "what's taking so long to run?", in my mind I was thinking there'd be one obviously slow thing that I could just remove or refactor, but it turned out that it wasn't any one single slow function
9.
by philipwalton 8y ago
Article author here. Yep, not hiding that fact (I could have easily used a trace with minified code, but I didn't to point this out). Two things though: 1. I used to work on Google Analytics, and I've created a lot of open source
10.
by philipwalton 8y ago
Article author here. Most of the comments so far are talking about using lots of tabs, but what I think is actually the most interesting part (or parts) of the article hasn't been mentioned at all. As I was doing my research for the ar
11.
by philipwalton 8y ago
This isn't true. The proposal was discussed many times in the WebPerf working group and went through a TAG review before shipping. Microsoft made a public statement of support for the API, and Firefox engineers were actively involved i
12.
by philipwalton 9y ago
I didn't know about that. I'll look into it!
13.
by philipwalton 9y ago
You're right about it not working for webpack dev server, and I agree that it's unfortunate, but I think webpack will evolve to accommodate this. [EDIT: it looks like this is already supported, here's the documentation explai
14.
by philipwalton 9y ago
*she
15.
by philipwalton 10y ago
There is a way. Every autotrack plugin that sends hits has two configuration options that enable full customization over exactly what fields get sent with each hit. The options are `fieldsObj` and `hitFilter`: https://github.com&
16.
by philipwalton 10y ago
The library is designed to be loaded async, so it shouldn't affect load performance. And it uses new APIs (e.g. IntersectionObserver) and techniques like throttle/debounce for all of its event tracking, so it will likely have no n
17.
by philipwalton 10y ago
As dudus mentions: the GA article posted yesterday includes a recommendation to use this library. As for a comparison of it vs. the GTM setup used by thenextweb, I briefly explain my thoughts on GTM in another comment here: https:/&#x
18.
by philipwalton 10y ago
There are tons of things GTM can't do currently, unless you're willing to write custom code. And if you're writing custom code, I'd personally prefer that code to be in my app, under version control, and running through
19.
by philipwalton 10y ago
The maxScrollTracker documentation warns against using it with an infinite scroll type of page: https://github.com/googleanalytics/autotrack/blob/master/doc... As for under reporting of history state cha
20.
by philipwalton 10y ago
analytics.js falls back to the older methods in unsupporting browsers.
21.
Apple launches Safari Technology Preview, a new browser aimed at web developers(techcrunch.com)
2 points by philipwalton 10y ago|0 comments
22.
by philipwalton 10y ago
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 adopti
23.
by philipwalton 11y ago
> 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 b
24.
by philipwalton 11y ago
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, f
25.
by philipwalton 11y ago
I don't see a lot of "debating" going on. If you want to point me to some constructive debates, that would be nice.
26.
by philipwalton 11y ago
Indeed! That's why I wrote the article :)
27.
by philipwalton 11y ago
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 f
28.
How to Become a Great Front-End Engineer(philipwalton.com)
8 points by philipwalton 11y ago|0 comments
29.
by philipwalton 11y ago
The tweet starts out: "Google: 90% of our engineers...", which implies that this is information Google told him.
30.
by philipwalton 11y ago
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 may

More ›