Engineer on @googlechrome. Involved in CSS and W3C standards. Previously @mozilla, @w3ctag. Mastodon: @dbaron@w3c.social

Rockville, Maryland, USA
Joined March 2008
Filter
Exclude
Time range
-
Near
Replying to @BenRossTransit
Quite possible if it's below freezing a few hundred feet up, I think.
Replying to @JakeAnbinder
Vandenberg Air Force Base? Coastal California temperate weather, maybe less earthquake risk than SF or LA, and the chance to build something dense?
3
Replying to @timdream
There might be less of a problem when the content people see is what they choose to see rather than what engagement-driven algorithms chose.
1
4
I find city budgets in the US hard to compare given the variation in what's included, and when many of the things sometimes included (e.g., hospitals (recall US medical billing), airports) have large budgets with relatively small subsidy/profit from/to the general budget.
1
It's nice to be ahead on rainfall for the year, for a change. (by enough to keep us ahead for a few weeks I think)
Preliminary station-based precipitation departure from normal in 2021. At the annual scale, a lot of highly impactful seasonal anomalies are muted. Still, an overall drier than normal year.
1
4
Anyway, don't forget to power-cycle your Boeing 787 at least every 248 days.
1
Er, except MDN says it's a value in milliseconds, accurate to around 5 microseconds, so that's the wrong threshold. Oops.
1
In other words, if you have a web page open for 285.42 years, you probably have bigger problems than your interval time precision becoming unable to represent odd numbers of microseconds since you loaded the page. Like maybe some important security updates.
1
2
Replying to @tabatkins
DOMHighResTimeStamp isn't used to hold clock time, though. It's for interval time. developer.mozilla.org/en-US/…
2
As another ex-Mozillian, I long ago learned to separate the Mozilla Foundation (which is clearly the part that did this) from the Mozilla Corporation (which makes Firefox, and where we both worked). Perhaps I shouldn't have been so accepting of that when I was there, though.
3
16
Are San Antonio and... Lubbock... close in Texas terms?
3
1
29
A reason to push non-TLS towards zero is that user agents (e.g., browsers) can't distinguish which sites need which combination of authentication, integrity, and confidentiality. Getting it to zero lets software make more meaningful promises to its users.
1
1
Yeah, the numbers on transparencyreport.google.co… (about halfway down the page) are pretty good. Reasonable people might disagree over whether that's good enough to count as "basically disappeared".
1
4
I did do the @_pernosco_ video, posted in this separate thread:
1/5 Last week I mentioned I'd also share a demo of @_pernosco_, which is a debugger whose interface is designed for record-and-replay debugging, although the debugging itself is less about replay than about moving between program states of interest.
5/5 A few more links: Pernosco: pernos.co/ The change I was debugging (which now contains the fix for the bug, but still isn't submitted): crrev.com/c/3307117
1
4/5 Another one of my favorite pieces of this video was entirely unintentional: I made a mistake and ended up in the wrong state. To fix this mistake, I just hit the browser's back button. Web technology (used well) really does have advantages.
1
1
3
3/5 The bulk of my rr demo video was really doing something that was a single logical operation: tracing backwards to find where a value comes from. One of my favorite parts of this pernosco video is near the opening, where I show that this becomes a few clicks in pernosco.
1
2
1
2/5 I recorded myself debugging (re-debugging, really) in pernosco. The bug turned out to be pretty simple; something that I perhaps should have figured out by looking at the code. However, I think it makes a reasonable demo of debugging in pernosco: drive.google.com/file/d/19TY…
1
2
2
1/5 Last week I mentioned I'd also share a demo of @_pernosco_, which is a debugger whose interface is designed for record-and-replay debugging, although the debugging itself is less about replay than about moving between program states of interest.
1/ Record-and-replay debugging has changed the way I work as a software engineer working on browser engines. I made a video showing how I used rr to debug one bug in Chromium. drive.google.com/file/d/15Ef… Some Chromium colleagues found this useful, so I'm sharing it here too.
1
3
1
12
Yeah, it helps that problem to talk about en.wikipedia.org/wiki/Qualit… or similar measures.
1