floil
Joined 12 years ago
Karma
175
Submissions
47
Member since
Mar 28
Recent submissions
Comment · 1 month ago
Comment · 2 months ago
I'm unfamiliar with claudish and the example helped show the problem. But! There was something uncomfortably familiar in the Claudish example -- this is the way human programmers write when they're deep in the weedy details, and writing the changelist description afterwards as if coming up for air. Overuse of parentheses in nested lists especially, as if the English text needs to bend to the strict needs of a C++ parser.
The rewrite did seem to lose the important fact about the ensure- pattern being idempotent.
Comment · 3 months ago
This is correct (I worked on chrome in 2008) it's important to remember that chrome's renderer was webkit, an existing c++ stack.
Chrome's stability innovation was to run different tabs in different processes, and the security innovation was then to sandbox those processes.
Rust would have been super nice but it wasn't an option then, and of course let's remember that Rust was developed by Mozilla specifically with the goal of making safer browsers.
Comment · 3 years ago
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.
Comment · 3 years ago
> 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...
Comment · 3 years ago
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.
Comment · 3 years ago
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.
Comment · 4 years ago
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)
Comment · 5 years ago
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.
Comment · 5 years ago
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.
Comment · 5 years ago
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.
Comment · 6 years ago
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.
Comment · 6 years ago
Fairly certain this feature is more then ten years old.
Comment · 6 years ago
Here you go: https://www.chromium.org/developers/design-documents
Comment · 7 years ago
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.
It's been this way for 25 years and I don't see it changing.