pkasting

7 ms·

1.
by pkasting 9d ago
The distribution opt-outs really bugged me at the time, and I went and talked to the marketing team. Surprisingly, users who got Chrome via one of those opt-out deals used it at rates/in ways statistically indistinguishable from "
2.
by pkasting 9d ago
Sure, it could easily take 1%. Going above 5%, OTOH, I would be shocked to ever see happen, for two reasons. 1) Mass-market adoption requires working well on an enormous long tail, which is difficult without a large team. 2) The primary dri
3.
by pkasting 26d ago
The common theme of this whole series of articles is basically "GCC extensions allow abominations".
4.
by pkasting 1mo ago
Ray Bradbury is the best horror writer to have worked in a sci-fi milieu. This story is one of only a couple sci-fi short stories to creep me out enough that I still remember them vividly decades later. (John Varley's "PRESS ENTER
5.
by pkasting 2mo ago
The closing problem is more fun. > A man is twice the age his wife was when he was the age she is now. When she reaches his present age, their combined years will be 100. Find the age of each. This seemed initially like something amenabl
6.
by pkasting 2mo ago
I was there 06-25, and this matches my recollection. Honestly, it's a very restrained document.
7.
by pkasting 3mo ago
The idea sounds good, even if Epic's recent track record of tools is not inspiring. But the commit messages etc. are very clearly products of vibe-coding. And version control is not the situation where "works 97% of the time"
8.
by pkasting 4mo ago
XHTML was never all the rage. Your premise is false. Hard errors up front are great when you control the full content pipeline. It's very rare that that's the case, and was rare even in 2004. As soon as including someone else&#x27
9.
by pkasting 4mo ago
On the contrary, image decoders all run complex processes that try and guess what to do in erroneous cases. I used to maintain Chrome's image decoders, and every single image format has "what the spec says" and then "wha
10.
by pkasting 5mo ago
(Tangent: What a pleasure to see your username again; will always think of your readability help fondly!)
11.
by pkasting 5mo ago
This list is missing my personal law, Kasting's Law: Asking "who wrote this stupid code?" will retroactively travel back in time and cause it to have been you.
12.
by pkasting 6mo ago
Crowing over omitting Arabic numerals in the name of avoiding any kind of cultural influence or bias seems silly when everything is still going to be expressed in decimal.
13.
by pkasting 8mo ago
C++ module implementation is a story with a lot of drama, if you ever want to read up on it. The short summary, though, is that no toolchain yet has a bulletproof implementation, though everybody at least has enough to let people kick the t
14.
by pkasting 8mo ago
Yeah, maintainers would certainly +1 a CL that added a note about the parts of //base to use instead. Trivial oversight.
15.
by pkasting 8mo ago
FWIW, I still think the Google Style Guide banning UDLs entirely is too harsh. I think they should be used sparingly, but there are cases where they make sense. In Chromium's UI code, we have a lot of APIs that deal with coordinates, w
16.
by pkasting 8mo ago
A cursory Chromium code search does not find anything outside third_party/ forcing either signed or unsigned char. I suspect if I dug into the archives, I'd find a discussion on cxx@ with some comments about how doing this would r
17.
by pkasting 8mo ago
Dunno! My last project there was to add support for one of the TI DSPs, but as I said, that's decades past now. Anyway, I think there are two takeaways: 1. There probably do exist non-8-bit-byte architectures targeted by compilers that
18.
by pkasting 8mo ago
Yes, reading the actual data would still be UB. Hopefully will be fixed in C++29: https://github.com/cplusplus/papers/issues/592
19.
by pkasting 8mo ago
At least in Chromium that wouldn't help us, because we disable strict aliasing (and have to, as there are at least a few core places where we violate it and porting to an alternative looks challenging; some of our core string-handling
20.
by pkasting 8mo ago
When I led C++ style/modernization for Chromium, I made this argument frequently: we should prefer the stdlib version of something unless we have reason not to, because incoming engineers will know it, you can find advice on the intern
21.
by pkasting 8mo ago
It's weird to me, as the former lead maintainer of this page for ten years or so, that this got submitted to both r/c++ and HN on the same day. Like... what's so exciting about it? Was there something on the page that caught
22.
by pkasting 8mo ago
The majority of things Chromium bans would still get banned in green-field use. Some notable exceptions: we'd have allowed std::shared_ptr<T> and <chrono>. We might also have allowed <thread> and friends.
23.
by pkasting 8mo ago
This bit us in Chromium. We at least discussed forcing the compiler to use unsigned char on all platforms; I don't recall if that actually happened.
24.
by pkasting 8mo ago
Green Hills Software's compiler supports more recent versions of C++ (it uses the EDG frontend) and targets some DSPs. Back when I worked in the embedded space, chips like ZSP were around that used 16-bit bytes. I am twenty years out o
25.
by pkasting 8mo ago
I don't think that's an accurate representation. There are a few features like that, but the majority of things banned in the Google style guide are banned for safety, clarity, or performance concerns. Usually in such cases Google
26.
by pkasting 8mo ago
Both parts of your sentence refer to the Google style guide. This doc isn't the Google style guide. It's the Chromium modern c++ features doc. We don't talk about exceptions or platform-specific stuff (save a note on [[no_uni
27.
by pkasting 8mo ago
We have base::Callback for when you'd reach for std::function, which provides superior safety.
28.
by pkasting 8mo ago
Sure; you can roll your own, or you can use one of the many other libraries that provide alternatives. There are obvious downsides to the former, and the latter is basically equivalent to using the Abseil ones in terms of practical tradeoff
29.
by pkasting 8mo ago
We have a linter that checks for most of them as a pre-upload hook.
30.
by pkasting 10mo ago
Ex-Google here; there are many people both current and past-Google that feel the same way as the composite coworker in the linked post. I haven't escaped this mindset myself. I'm convinced there are a small number of places where

More ›