(I still think it dropped a few words from what I would consider a literal translation? In particular I would translate the last clause more like "Let's *try* to practice "communicating" to someone *properly*". But either way, this was very helpful for getting me unstuck.)
It seems New Relic will soon stop using an unload event listener. This prevented pages to benefit from the ultra-fast back/forward cache.
They shipped an experimental setting last month: https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1222/
And they're about to make it the default: https://github.com/newrelic/newrelic-browser-agent/pull/401
Yeah for faster websites!
I've been trying to get Chrome release notes / articles / etc. to avoid this mistake, but it's an uphill battle. (Similarly for MDN.) The WebKit team shows us it can be done!!
This is some real Susan Calvin robot psychologist shit https://www.lesswrong.com/posts/aPeJE8bSo6rAFoLqg/solidgoldmagikarp-plus-prompt-generation
Here ... we ... go! https://google-research.github.io/seanet/musiclm/examples/
At one point in time Chromium tried to prevent busy loops inside unload / beforeunload by... overriding how the JavaScript Date object worked!? https://trac.webkit.org/changeset/48612/webkit
I’m going to tell you the story of the man who solved a crime.
Not, like, a cop who put together the clues and got his man, but a person who took a crime as old as civilization and fixed the problem where it got you in trouble.
The man: Artur Virgílio Alves Reis.
The place: 1920s Portugal.
The crime: Counterfeiting.
The problem he fixed: That the money is counterfeit.
(This is going to be a long 🧵 . Just trust me.)
If you’re annoyed by those floaty prompts on websites to sign into them with your Google Account, you can turn them off for your Google account! Link: https://myaccount.google.com/u/0/permissions
https://heistak.github.io/your-code-displays-japanese-wrong/for background on this problem. The supplement of which contains this fascinating info on "discretionary ligatures"...
As a maintainer of OpenSource libraries and packages, there is something that kept feeling off in the whole Software Supply Chain discourse. I think this comes down to something simple.
I am not a Supplier.
You can read more explanation there https://www.softwaremaxims.com/blog/not-a-supplier
Some fun reads on memory safety in C++: https://cor3ntin.github.io/posts/safety/ and https://danakj.github.io/2022/12/31/why-subspace.html. As someone without much expertise or experience, it's still quite interesting to see smart people at work on such a hard, practical problem.