pkasting

9 ms·

61.
by pkasting 3y ago
Hmm. Over in the browser space, I'd say Google's shown significant, long-term investment in Chrome/Blink, especially compared to Apple's relative disinterest in putting significant engineering resources on WebKit. Perhap
62.
by pkasting 3y ago
Ah, angry Internet people. I have my own collection of responses, from someone who argued that my choice of a default value for a setting was tantamount to forcing someone to have an abortion against their will, to the time when restricting
63.
by pkasting 4y ago
Indeed. Here's the bug where we fixed it: https://bugs.chromium.org/p/chromium/issues/detail?id=109098...
64.
by pkasting 4y ago
It's surprisingly hard to detect these sorts of cases reliably; we have a request out to the clang-tidy folks to add some improved detection of use-after-move there.
65.
by pkasting 4y ago
Took a couple of months actually, but it's mostly complete now and we're starting to throw the switches.
66.
by pkasting 4y ago
Well, Chrome has many, many hundreds of developers who have worked for many years on the codebase. If we froze the world and turned the whole team over to writing Rust, and we assumed people were perfectly productive in Rust from day one,
67.
by pkasting 4y ago
Not publicly, unfortunately. This talk was given internally a couple of times.
68.
by pkasting 4y ago
This is from Chromium's perspective, yes, but Chromium complies with the Google style guide. I disagree with your characterization that "a very restrictive subset of features" are allowed, though. What's banned is rela
69.
by pkasting 4y ago
Chromium compiles with -Werror, so deprecation warnings must be fixed before we can upgrade.
70.
by pkasting 4y ago
You cannot refactor C++ to Rust at the individual function level without good Rust<->C++ interop. The Carbon docs go into this at a sufficient level of detail; TLDR, interop paths exist but are insufficient and are actively being res
71.
by pkasting 4y ago
I work on the Chrome team. Safety is not the only goal for the codebase. There's also things like readability, maintainability, performance, and correctness. Finally, there's the need to chart a course towards how you get there
72.
by pkasting 5y ago
You're very welcome!
73.
Chromium C++ 201: Four-part tutorial video series(youtube.com)
9 points by pkasting 5y ago|3 comments
74.
by pkasting 5y ago
I'm a developer on the Google Chrome team and recently released a four-part series of talks I did on "Chromium C++ 201", a look at topics like copying and moving, lambdas, constexpr, RAII, Unicode strings and more, through th
75.
by pkasting 8y ago
Your visited URLs are in general only sent to Google if you have opted into sync and have "History" as an enabled datatype.
76.
by pkasting 8y ago
In the sense you seem to be asking, no; see https://news.ycombinator.com/item?id=19381175 and https://news.ycombinator.com/item?id=19393019 .
77.
by pkasting 8y ago
This isn't sourced from any Chrome-collected data. See https://news.ycombinator.com/item?id=19393019 .
78.
by pkasting 8y ago
Usage data helps us make UI changes. For example, if not a ton of people are using some functionality, we might prioritize modifying or removing it. When we make a change, seeing how it affected usage is an important part of verifying we
79.
by pkasting 8y ago
Regarding "data they're collecting": The list here is based on popularity of search engines in different locales, determined using publicly available data.
80.
by pkasting 8y ago
False dichotomy. You provide all browsers with data by using them; the question is what they do with that data. Chrome is not materially different than other browsers in the level of control you're able to have over what gets sent el
81.
by pkasting 8y ago
I've worked on Chrome since the beginning (I'm a founding team member) and I designed and built the omnibox and wrote most of this code. I'm confident we haven't ever done what you're describing. We haven't al
82.
by pkasting 8y ago
Sync is opt-in.
83.
by pkasting 8y ago
You're correct that manual configuration of the suggest_url is unavailable ( http://crbug.com/8395 ), but incorrect that the prediction service sends data to Google in the case where that's not configured. In tha
84.
by pkasting 8y ago
This relies on several things: * Enabling Chrome Sync, which is opt-in * Syncing history, which is on by default if you enable sync * Not using a custom passphrase for sync data (not using one is the default) * Having "My Activity&quot
85.
by pkasting 8y ago
The full details are in https://www.google.com/chrome/privacy/whitepaper.html#malwar... , but the short summary is: A hash prefix list gets downloaded locally; Chrome checks locally against the prefix list. If a
86.
by pkasting 8y ago
No; see https://news.ycombinator.com/item?id=19381175 .
87.
by pkasting 8y ago
Correct; if you are using DDG as your default search engine, and you enable "use a prediction service", suggest queries are sent to the "suggest_url" configured for that engine. For DDG, that URL is here: https:/&
88.
by pkasting 8y ago
Eh? "Use a prediction service" is about whether you send data as you type _to your default search engine_, not to Google. If you change to DuckDuckGo as your default search engine, toggling "use a prediction service" o
89.
by pkasting 8y ago
That's not what I meant by raising this incident. The top-level reply spoke about marketing something as better than a competitor, then switching to that competitor, and the cognitive dissonance involved. The PowerPC to Intel switch
90.
by pkasting 8y ago
Rust as a language was significantly less mature a few years ago; I think that's the bigger factor here. It certainly doesn't hurt to do compelling things in Rust in a browser engine, but doing compelling things in Rust in some ot

More ›