http.ListenAndServe is implemented under the hood with a new goroutine per incoming connection. You don't have to explicitly use goroutines here, it's the default behaviour.
Will be an underlying safety issue in some system library, but they have only seen "in the wild" exploits targeting Intel. "Defence in depth" - better to push the bugfix to all than to scrutinize ARM security features to understand if an exploit is possible there as well.
Thing is nearly all cooling. And look at the diameter on the water cooling pipes. Airflow guides on the fans are solid steel. Apparently the chip itself measures 21.5cm^2. Insane.
It's not just that there are few signals to prevent the wrong person being put in charge, but this kind of government bureaucratic actively selects for the wrong person. These kinds of government IT projects are often soul sucking to work on, and so they attract a specific kind of applicant.
The port on the bottom is really the least offensive element of the design. I know people find it fun to clown on, but if any of them had ever used one for 5 minutes they would realize it's a terrible mouse for a bunch of other more important reasons (weight, feet quality, tracking accuracy, polling rate etc.).
Court isn't the place for scientific inquiry into these issues. It's just not setup for it. French courts have also found in favor of "electrosensitivity" issues.
Sounds like a really interesting problem space. I'm curious if you have any comments about how you approached dealing with inconsistencies between information sources? System A says X, system B says Y. I suppose best approach is again just to bail out to manual resolution?
One example is that instead of adding support for edge case mutations/changes late in a process, it's sometimes better to force those records to be thrown away and reset with a new record from the start of the process. You avoid chasing down flow on effects of late unexpected changes in different parts of the application.
To give a contrived/trivial example, imagine a TLS handshake. Rather than building support to allow hosts to retry with a different cert, it's better to fail the connection and let the client start from scratch. Same principle can be applied to more complex process automation tasks in business. Imagine a leave tracking system. It might be better to not support changing dates of an existing leave application, and instead supporting cancel & re-apply. Best part is that the user facing part of both versions can be exactly the same.
It's not "until sales shows up", it's until regulators start causing problems for Cloudflare because you are using Cloudflare infra to host a grey market online gambling website.
Even grosser is that they explicitly limited the iOS version of Google Photos to refuse to work with scoped access. So on iOS the app will refuse to work without being granted whole library access, a permission that Google no longer allows to any third party photo app on Android. Blatantly anticompetitive.
I'm also completely sick of fielding API migration emails from Google on mobile Android/Firebase. Feel like I get some "action required" every couple of weeks. This stuff saps our resources, both to fix it, and to diagnose if the issue even applies to us in the first place. If you are lucky Google includes details of the app using the API, but often this part is even left out.
This is a rod Samsung has made for their own back though. Fewer SKU's, and more shared parts between models would be better for consumers and for the planet.
