slightlyoff

7 ms·

31.
by slightlyoff 4y ago
Original author of the post here. I'm also a Blink API OWNER, so can happily report that Container Queries have 3 LGTMs and will ship in Chromium browsers very shortly, likely 105 (shipping to Stable in September): https://c
32.
by slightlyoff 4y ago
Do you see them requiring only one browser engine on all of the Android devices they sell? No. The requirements of carriers are orthogonal to browser choice post-sale.
33.
The Performance Inequality Gap, 2021(infrequently.org)
5 points by slightlyoff 6y ago|3 comments
34.
by slightlyoff 6y ago
An update on devices, networks, browsers, and the new baseline scenario for web performance.
35.
by slightlyoff 7y ago
`.entries()` returns an iterator one can use directly in for-of loops: https://developer.mozilla.org/en-US/docs/Web/API/NodeList/en...
36.
by slightlyoff 8y ago
Hey, author of the patch here. The restrictions are wire size. `bootstrap.min.js` is ~10KiB on the wire, which means it comfortably fits (as do jQuery, most analytics packages, etc.). That said, the prototype does break a lot of the web
37.
by slightlyoff 8y ago
Hi, author of the NSM patch. Still very much under development, but most of the important considerations aren't technical, and making progress on a system like this is more about how to roll things out rather than implementation. It&#x
38.
by slightlyoff 8y ago
Author of the patch here. Note that the limits are wire size , not disk size. jQuery, post gzip, is closer to ~30KiB, meaning it fits nicely under the per-file restriction. The total JS limit per-interaction is 500KiB gzipped . Uncompress
39.
by slightlyoff 8y ago
The entire post is premised on frustration in my ability to share what I know in order to avoid punching down. That I can't share specifics is the whole reasonto try another tack. See also: https://wpostats.com
40.
by slightlyoff 8y ago
Author of the article here; you'd be truly shocked.
41.
by slightlyoff 8y ago
JavaScript can be evaluated top-level function by top-level function and file-by-file, modulo variable hoisting. You can create situations where everything is blocked, but that's not the norm.
42.
by slightlyoff 8y ago
WASM streaming compilation is possible today and runtimes are adding tiered compilers: https://v8project.blogspot.com/2018/08/liftoff.html Regardless, as long as you're network-bound in the critical-path, tha
43.
by slightlyoff 8y ago
Images aren't as expensive as critical-path code as we (the browser) parse and raster them off-thread. Outlined some of the costs here: https://infrequently.org/2017/10/can-you-afford-it-real-worl... Excited
44.
by slightlyoff 8y ago
The "hello world" demo app appears to require ~1.3MB of transfer, nearly all of it critical-path: https://blazor-demo.github.io/ This future isn't better.
45.
by slightlyoff 9y ago
Howdy; author of the article here. TTI would be pushed back regardless of where the script was included so long as it executed for more than 50ms (very likely). I used a trivial document that contains many pathologies I see in traces to i
46.
by slightlyoff 11y ago
The abuse considerations were what led us to implement the engagement check. An API for this would absolutely be spammy. If everyone is going to be calling it on every page-load, and if the browser is (predictably) not going to allow that t
47.
by slightlyoff 11y ago
Chrome for Android had the same buried "add to homescreen" thing for a long time: https://developer.chrome.com/multidevice/android/installtoho... Chrome for Windows has had "Create Application Short
48.
by slightlyoff 11y ago
Those features have all launched; see: http://blog.chromium.org/2015/03/chrome-42-beta-push-notific...
49.
by slightlyoff 13y ago
I realize that I'm an outlier but I support prefixing as a possible solution to this sort of thing; but that's even more out of favor with the CSS WG than what's being proposed (AFAICT). Looking forward to timely www-style fe
50.
by slightlyoff 13y ago
That's moving the goalposts. The full context of your statement was: > it'll be other vendors' pain as they have to reverse engineer Blink's implementation Which was the salient point I was replying to. Quoting out of
51.
by slightlyoff 13y ago
Meaningful progress is progress for the most people. To achieve that, it's often most effective to create coalitions to help you achieve that progress in areas you yourself cannot. This is where collaboration and standards come in. Wha
52.
by slightlyoff 13y ago
Hi Jacob, I sympathize with the hesitation that you must feel regarding a request to analyze a feature on a short timeframe, it is however the case that MSFT has in the recent past (Pointer Events, which are GREAT) used its prerogative to s
53.
by slightlyoff 13y ago
The details of both the semantics and syntax in question have been widely discussed and understood. It's pure hyperbole to appeal to "reverse engineer Blink's implementation" (which, as you might be aware, is Open Source
54.
by slightlyoff 13y ago
Progress delayed is progress denied. If you want a better web platform, that means wanting one that is different than the one we have today. It is also the case that standards committees are not outfitted with effective fitness functions (t
55.
by slightlyoff 13y ago
A previous solution based on explicit naming of "parts" of shadow DOMs was withdrawn several months ago. And update was given the the CSS WG last November that outlined the changes. FWIW, the "::part()" solution would ha
56.
by slightlyoff 13y ago
Just to be clear, Googlers (myself included) have been constantly participating in the standards process both pre-and-post fork. There's nothing "brand new day" here; conscientious standards engagement is just how we roll her
57.
by slightlyoff 13y ago
...and 10 = ( Luckily, those IE 9 users are less of an issue if IE 11 includes WebGL as they tend to be auto-upgraded. The IE 8 users are a harder case.
58.
by slightlyoff 13y ago
Chrome Frame won't be available for consumers to install any more. Chromium Embedded is a separate project and they can maintain whatever patches they need to make things fly, methinks.
59.
by slightlyoff 13y ago
This misunderstands what happens inside implementations. There ARE low-level bits "down there", but they aren't spec'd. That what the Navigation Controller is: a spec for the low-level bits. As a part of that process (an
60.
by slightlyoff 13y ago
Yeah, you are misinterpreting. See my other comment.

More ›