mathias

5 ms·

1.
by mathias 4y ago
Did you know that “old” Chrome Headless (2017–2023) was a separate, alternate browser implementation that just happened to be shipped as part of the same Chrome binary? It doesn’t share any of the Chrome browser code in //chrome.
2.
Chrome’s Headless mode gets an upgrade: introducing –headless=new(developer.chrome.com)
5 points by mathias 4y ago|2 comments
3.
by mathias 6y ago
https://github.com/puppeteer/recorder
4.
Faster Apps with JSON.parse (Chrome Dev Summit 2019)(youtube.com)
1 points by mathias 7y ago|0 comments
5.
by mathias 7y ago
The article includes a working polyfill that includes old IE support.
6.
by mathias 7y ago
Author of the referenced article here. The article includes a working polyfill that includes old IE support, so I’m not sure what you’re complaining about. Also, saying “jsvu is the justification for the polyfill” doesn’t make much sense. j
7.
What’s new in JavaScript (Google I/O ’19)(youtube.com)
8 points by mathias 7y ago|0 comments
8.
by mathias 7y ago
Thanks :) Glad to see people appreciate simplicity (and the performance that comes with it).
9.
by mathias 8y ago
We do indeed measure improvements against more than one website. We wouldn’t want to improve website X while regressing the rest of the internet. See https://v8.dev/blog/real-world-performance (from 2016): > We now
10.
by mathias 8y ago
The article links to the explanation by the proposal champions: https://github.com/tc39/proposal-class-fields/blob/master/PR...
11.
by mathias 8y ago
I mean, they have been solved. With the exception of String#matchAll (which is currently a Stage 3 proposal), all these features are part of ES2018 and shipping in Chrome. Other browsers implement some of them already and are working on s
12.
by mathias 8y ago
I make sure to keep the article up-to-date. It correctly states the status for each of the features. They’re all part of ES2018 with the exception of String#matchAll which is currently at Stage 3.
13.
by mathias 8y ago
Hey, I’m the author of the article. Despite its age, it’s still accurate and up-to-date. > these features aren't entirely new Depends on what you mean by that. These features are still not universally supported by all modern browser
14.
by mathias 8y ago
That’s not very JavaScript-y. Where else in ECMAScript are constants used like this?
15.
by mathias 8y ago
That would be a Chromium feature. V8 only implements ECMAScript and WebAssembly.
16.
JavaScript engine fundamentals: optimizing prototypes(mathiasbynens.be)
2 points by mathias 8y ago|0 comments
17.
What’s new in modern JavaScript and V8? (Google I/O ’18)(youtube.com)
2 points by mathias 8y ago|0 comments
18.
by mathias 9y ago
The article is two years old but still up-to-date. The links to the relevant browser bugs are in the document, and the Edge bug is still unresolved. https://wpdev.uservoice.com/forums/257854-microsoft-edge-dev...
19.
by mathias 9y ago
> In older browsers, useCapture is NOT an optional parameter Which browsers are those?
20.
by mathias 9y ago
> Which means you can’t practically use the new form without feature detection. That does not follow. `{ capture: true }` works in both, since it’s an object, and thus truthy. There’s no need for feature detection in the case you describ
21.
by mathias 9y ago
That’s not equivalent though — in the article’s example, imagine `element` is `undefined`, for example. `then()` wouldn’t be called in that case.
22.
by mathias 9y ago
Correct. By Stage 3, the proposal is supposed to be stable enough to start shipping it in stable browsers.
23.
Asynchronous stack traces: why await beats .then()(mathiasbynens.be)
2 points by mathias 9y ago|0 comments
24.
by mathias 9y ago
Wondering what a given legacy HTML color value (as seen in `bgcolor`, `text`, `link`, `vlink`, and `alink` attribute values) looks like? This tool (which I made for a presentation years ago) shows you: https://mothereff.in/b
25.
Browser-based timing attacks: demos(labs.tom.vg)
9 points by mathias 10y ago|1 comments
26.
Unicode property escapes `\p{…}` and `\P{…}` in JavaScript regular expressions(mathiasbynens.be)
1 points by mathias 10y ago|0 comments
27.
by mathias 10y ago
Present tense: https://domenic.github.io/streams-demo/
28.
by mathias 10y ago
Replace `test` with `example.com` et voila.
29.
by mathias 10y ago
+1. Still, code screenshots in Notepad?!
30.
by mathias 10y ago
Nowhere in the blog post does Wright say “this is the proof I’m Satoshi”. The entire write-up reads like he’s just giving an example. Why does everyone think it’s some kind of proof?

More ›