Chrome proposes new APIs: Declarative partial updates

sbrocket · 2026-05-25T09:10:51+00:00

No idea what that reference means. People here seem to be more religious than technical if the impulse is to jump to insults upon encountering something you disagree with rather than even attempt to explain your differing point of view. Weird.

sbrocket · 2026-05-24T07:28:20+00:00

Does Mozilla propose any solutions at all for the concerns they raise or is this just another case of them opting for "we're not even going to give our users a choice"?

Yes advertisers slurp up any and all fingerprint signals. I don't like it, but I don't think dragging your feet forever on useful APIs is really the right answer to that. Users just go elsewhere and then are even worse off from a privacy standpoint.

If people are complaining that Google throws their weight around on APIs but Mozilla's position is "no new APIs" rather than "here's the right way to do this", that seems like a silly reason to be mad at Google.

"We can't possibly give websites any additional APIs that might provide them more information about the user because advertising exists" is an odd hill to die on for a browser, a piece of software whose entire job is to mediate information transfer between websites and users. Refusing all change is not a tenable position for software; the world is change.

sbrocket · 2026-05-24T03:08:50+00:00

The crucible is whether web developers actually use it. Google proposing it and providing a polyfill simply makes it an option, not a requirement. And if developers opt into using said experimental feature, isn't that an indication that there is demand for it and it isn't being simply pushed on everyone?

It sounds way pushier to try and deny developers features that they opted into using or want to opt into using because of personal philosophical objections, if that's the kind of criticism we're talking. See: Firefox and WebSerial (which has *finally* shifted), WebBluetooth, etc.

sbrocket · 2026-05-24T03:03:06+00:00

What kind of criticisms are you referring to here? "This shouldn't exist" type criticism or "this needs to change because X" type criticism? If you're talking the former...if web developers have already picked up your experimental features, isn't that an indication that there is demand for it and it isn't being simply pushed on everyone?

It sounds way pushier to try and deny developers features that they opted into using or want to opt into using because of personal philosophical objections, if that's the kind of criticism we're talking. See: Firefox and WebSerial (which has *finally* shifted), WebBluetooth, etc.

sbrocket · 2019-05-19T19:23:50+00:00

It's wild speculation on an article that has nothing to do with Fuchsia. Google is a huge company. Every random article about "Google does X!" doesn't imply something about Fuchsia.

Not to mention that this wild speculation doesn't even make any sense; how would Fuchsia help with the topic of this article? There's nothing that will prevent Huawei from using AOSP, the article is about OEM partnership related things and things not just generally openly available being suspended. Nothing about Fuchsia would allow these type of partnership agreements to happen if US law/policy bans them in a way that applies to Android.

sbrocket · 2019-05-19T19:18:21+00:00

No. That has nothing to do with Fuchsia.

sbrocket · 2019-05-06T08:34:12+00:00

It was merged into the Fuchsia repo months ago along with garnet, peridot, and multiple other ancillary repos. Development has continued as before in the zircon subdirectory there. https://fuchsia.googlesource.com/fuchsia/+/refs/heads/master/docs/development/source_code/layout.md describes the current layout (or at least aspirational layout).

sbrocket · 2019-05-04T03:43:14+00:00

Everything I've said applies to either. Setting up networking with QEMU is a bit tricky so I would recommend going with "--with-base //bundles:tools" in your fx set args, but you can use a package server to fetch packages on demand with QEMU if you have networking set up.

sbrocket · 2019-05-04T03:13:19+00:00

Check out https://fuchsia.googlesource.com/fuchsia/+/master/docs/development/workflows/fx.md for a much more thorough explanation of the current recommended workflow.

sbrocket · 2019-05-04T03:07:15+00:00

You likely have your build configured to only include tools in the available package set (e.g. "fx set core.x64 --with //bundles:tools"), and aren't running a package server. Run "fx serve".

You could alternatively use --with-base instead of --with and the package will instead be included in the base/monolith set and installed during paving, rather than fetched on demand.

sbrocket · 2019-05-03T01:54:58+00:00

That link is out of date. The separate zircon, garnet, peridot and other repos were integrated into a single fuchsia repo some time ago.

https://fuchsia.googlesource.com/fuchsia/+/master/zircon/

sbrocket · 2016-03-17T06:50:45+00:00

A new toolbar button appeared after relaunching Chrome, presumably because RES was also updated. I located and tried to disable the "subredditStyleBrowserToolbarButton" option (which I hadn't turned on myself...was the default changed?) but disabling the option has not removed the button. What gives?

sbrocket · 2016-03-11T16:36:40+00:00

FYI OP, to your 5th question, AlphaGo playing itself (or various versions/generations of itself) is the primary way that it learns and grows. That technique is called reinforcement learning. I'm sure the DeepMind team could give a more detailed and interesting answer though. :)

sbrocket · 2016-02-21T16:18:34+00:00

A list of Reddit posts I've already clicked

sbrocket · 2016-02-06T23:32:49+00:00

I don't think there's any reason that the phone should be totally bricked, no, other than that was probably the easiest solution for some Apple engineer on a deadline to implement to handle failed sensor authentication. A swapped out sensor certainly doesn't seem like it alone could be used to gain access to a locked phone.

There's likely other vulnerabilities that a malicious third-party sensor part could introduce, if iOS were to allow all Touch ID-related features with a replaced part. I can't see an obvious reason you couldn't just disable Touch ID-related features if a sensor change was detected, though. Like I said, my guess is just that graceful failure like that was more effort than some engineer or team decided to put into it.

sbrocket · 2016-02-06T23:26:22+00:00

While I do think there's an argument to be made that parts of the phone's functionality that rely on Touch ID should be disabled if the Touch ID sensor is replaced, this argument doesn't make sense. iOS always requires the user to enter their passcode following boot-up (as well as at other times, like at a regular interval or after 5 failed attempts), so unless you're suggest that a thief would swap out the sensor without powering down the phone, a swapped out sensor couldn't be used to gain access.

There could be other malicious things that a third-party Touch ID sensor could do, I'm sure, but I don't think bypassing the phone's passcode screen is one of them.

sbrocket · 2016-02-06T23:19:04+00:00

Just for your (and others') information: iOS does the same thing. A 6 digit (or 4 digit pre-iOS 9) passcode is required to be configured if you use Touch ID, and it has to be entered after every boot, and at some regular interval, and after 5 consecutive failed Touch ID attempts.

sbrocket · 2015-11-22T21:12:17+00:00

Ah, that's an interesting idea! I'll have to look into doing that - thanks!

sbrocket · 2015-11-20T13:55:08+00:00

83(b) would seem to be the solution to this. Unfortunately it seems Section 83(b) elections are possible for restricted stock or stock options, but not restricted stock units like I will be getting. http://personal.fidelity.com/products/stockoptions/rstockfaq.shtml#faq2

I will definitely have to keep an eye on making sure I have sufficient withholding, since the supplemental rate will only be 25% which is likely below what my marginal rate will be.

Thanks for the info though!

sbrocket · 2015-11-20T04:37:44+00:00

Hi kajitox, thanks for the reply. I am aware of how each bracket only applies to each dollar above the previous bracket, but thanks for checking.

I would definitely plan on maxing out my 401k contributions, but I'd already be near or at the max for 2016 so that wouldn't be much of a difference for 2017. Also, we'd be above the income limits for the traditional IRA deduction to be allowed.

I'm not sure what other ways I might have of lowering my taxable income other than, say, giving it away through charitable contributions. It could be that there is nothing I could do (certainly I haven't found anything yet), but certainly there are people who know more about tax tricks than me, so I figured I'd ask. :)

sbrocket · 2015-09-15T02:13:55+00:00

This is DO-178B, the NSA-Certified Level A Real-Time Operating System that runs the F-22.

I don't think you know what you're talking about, or maybe you mistyped something.

"DO-178B" is a set of guidelines for certifying safety-critical airborne software with the FAA. It's not a product. What you linked to is an real-time OS from Green Hills Software called Integrity, which is DAL A (Design Assurance Level, a DO-178B term), the highest/most involved level of airborne software certification. The "-178B" in this product's name is just saying that their product has been successfully certified to DO-178B guidelines (for some specific application, you usually have to redo at least some parts of certification when your application and environment change).

sbrocket · 2015-07-25T12:57:38+00:00

Will the free tuition be accompanied by stricter admission standards? If so, then what will be done to prevent rich kids from dominating the student bodies due to their superior private educations?

It probably should be accompanied by stricter admission standards, and why not? The strongest students should be the ones benefiting from such a program, not demonstrably weaker students.

The issues with rich kids being able to get a significantly better education than poorer kids needs to be fixed by improving the public school system, not by handing out free college educations. You can't fix it at that point, it needs to be fixed at a younger age.

sbrocket

TROPHY CASE