floil's comments

And to connect it back to the original post: the moments that make me cringe the most in Grand Designs are the ones where the owner decides, as a cost-cutting measure, to manage the project themselves despite not having prior domain experience. Whereas the author of this article successfully engaged an expert early on, and saw it pay dividends, despite the up front cost.

> leafing through the book with gloves

Rare books are typically handled with bare hands rather than gloves. Gloves increase the risk of damage.

https://www.nytimes.com/2023/03/09/arts/rare-books-white-glo...

My interpretation: the paper describes a system that works for a starting concentration of 200 parts per billion, or higher. This is unrealistic because, in real world contamination scenario, you would expect to see a starting concentration of around 1 part per billion.

I've read the book twice, decades apart, and it gave me great joy each times in very different ways.

I can see how this text causes some to experience the opposite of joy.

Both experiences are valid. But like there's not some big conspiracy of people who claim to like this book or this writer as a facade. They say it's great because, for them, it's a wonderful and meaningful experience.

Chrome browser extensions aren't really compiled, though I suppose they can be obfuscated. If you install this extension you ought to be able to find it in your Chrome profile directory and look at the manifest and JS source.

(former longtime chrome engineer here)

Both the KitchenAid and the Hobart use a planetary action which is not the best for kneading bread. A better idea is to find a small spiral mixer where the bowl rotates and the mixer blade spins in place. I have a Haussler Alpha and it's great for tough doughs, and seems appropriately overbuilt.

Site Isolation launched in Chrome in 2018, but the work started in earnest in 2012 -- see the below check-in. The idea in Chrome dated to before the Chrome 1.0 launch; it was the subject of Charlie Reis's PhD dissertation and he interned on Chrome pre-public launch.

https://chromium.googlesource.com/chromium/src/+/c6f2e67ab40...

Site isolation proved to be the biggest refactor in Chrome's history, and was one of the motivating reasons for the webkit/blink fork. Making site isolation work touched a huge host of features, since handling iframes out of process has a way of making simple things incredibly complicated.

The example I always gave was: imagine how the "find text in page" browser feature would be implemented. With the entire document in-process, it was a simple for loop. With the document and its subframes sharded across multiple processes, it is now a distributed search problem that requires handling of out-of-order results and stitching them into a traversal order. What's more, to achieve Chrome's security goals, you want to avoid introducing functionality that would allow the [presumed-compromised] process of the outer document to query the contents of the inner document via the find in page feature. So you can't simply do this as a peer-to-peer query between the renderer processes; it needs to be coordinated by the main browser process.

Congrats to the Firefox team on this milestone.

It's not a whole new level. An aspect of Quadro differentiation has, since ages ago, been based on selectively disabling features that the consumer gpus silicon was capable of. It's the same strategy here.

This makes sense to Nvidia because it creates a segment differentiation and will allow them to charge more for the higher hash rate parts.

As someone who walked away from programming two years ago, reading this stirred something in my heart that I honestly haven't felt since quitting. I've been frankly surprised that I haven't had the desire to code in that time, but it turns out I am nostalgic about the times when coding was a fun process of self discovery.

This article gives me the inkling of a way back to get back to there. Thanks to whoever shared it.

Fairly certain this feature is more then ten years old.

Here you go: https://www.chromium.org/developers/design-documents

When I was a kid, my next door neighbor was an ultra-marathoner and the fittest person I'd ever met. He died suddenly one day of a heart attack while out on a run.

Read it as "both decelerate more slowly and rotate more slowly" and it's an accurate description of what happens when you sweep in front of a curling stone.

Can confirm. The whole group working on that effort has been laid off.

Fwiw: this has always been the case, since Chrome 1.0.

In chromium, the glyph attack defense works by normalizing to a "confusability skeleton" -- the ICU library actually does the normalization. Even within latin-1 this does some mangling: m gets normalized to rn, w to vv, etc. The query rewriting is a different problem, but it's possible it uses the confusables list as an input.

For myself, I switched everything over to Google WiFi's, precisely because they auto-update, and having worked previously on a security-focused team at Google, I trust them to have a competent security team and actually stay on top of the patches. I don't miss fussing with manually updating router firmware. Life is too short.

On the other hand, my Nest thermostats were bricked after a software update this week, so maybe today I'm starting to see a crack in my "auto update is best" dogma...

Did you read the article? She hasn't worked at Instagram since 2014.

Moreover, github.io is in the public suffix list, so it is effectively a TLD (foo.github.io is a different site from bar.github.io; they can't become same origin by means of document.domain).

The risk of eval() is giving control of the site data of foo.github.io to the author of a stackoverflow comment.

The warning is part of the fun, though.

Oh my.