> EE to debug react state management ... easily pick up most of it after a week long crash course while training a performance engineer ... would take months
Isn't that mostly because as you go up the abstraction layer, tools and docs to teach yourself the tricks of trade fast are in abundance (let alone a popular layer like React)? Which inturn is likely a function of incentives and opportunities.
It's because the higher up the stack you go, tools become more declarative and literate. Calling sort is far easier than understanding the algorithm for example.
Unironically, wet / dry cycles isn't good news for California either.
Research published in the aftermath of the fire examines how this extremely wet to extremely dry weather sequence is especially dangerous for wildfires in Southern California because heavy rainfall leads to high growth of grass and brush, which then becomes abundant fuel during periods of extreme dryness.
I wonder how much of an effect human activity has on these cycles. Obviously, there are cycles within nature that don't include human activity but is this particular "equilibrium" (if we could call it that) the result of human settlements and all that entails or have they always happened this way but without a huge chunk of the population being in the midst of these modulations to witness it and be affected by it.
Huge amount, but maybe not in the way you intended.
Many of California's ecosystems have evolved to expect fires. Humans can't stand fires and aggressively put them out. So fuel that would be regularly burned off in mild wildfires instead builds up into megafires that exceed the limits of what the ecosystem can handle (a lot of California trees are fire-tolerant, but there's a point where the flames get too high and too intense).
So yeah, the human activity that affects these cycles is caused by our cognitive dissonance and fear to phrases like "mild wildfire".
This might be a good time to recommend you all read the first 5 pages of East of Eden by George Steinbeck. It’s about how the Salinas valley goes through flood and draught cycles, and how every time they’re in one cycle they forget the other one ever happened
Depends on how you quantify human impact. Lodgepole Pine (for example) is fire adapted. That's not something that evolved overnight. So it's safe to say that broad swaths of California have been experiencing a feast-famine cycle since before humanity developed agriculture.
Most of the actual wild fires just get put out. The big ones are happening because the build up is too big since all the smaller ones have been put out. It's all in service of the forestry industry.
> Can't tell if it's an OS level safeguard or an app-level one.
App version rollbacks are not allowed on Android. Even if it were, apps will have had to implement support for rollbacks (think database schema changes that must be undone etc).
> CF could have kept coasting on what Astro was building, but instead they are paying for it. But in return they get a lot of control.
Supabase pioneered the modern implementation of this model. Probably, RedHat before it? Google also tend to "acquihire" maintainers of popular FOSS projects, like Ben Goodger (Firefox), Scott Remnant (Upstart), Junio Hamano (Git), Guido von Rossum (Python).
TFA is missing a host of many a popular isolation techniques like Isolates, Code Interp / Binary Translators [0], Enclaves, Exclaves, Domains/Worlds, (RISC V) SEEs, TEEs, SEs, HSMs, pKVMs ...
> as the CLOUD Act "gives the US government authority to obtain digital data
AWS maintains a similar stance, too [0]?
The CLOUD Act clarified that if a service provider is compelled to produce data under one of the limited exceptions, such as a search warrant for content data, the data to be produced can include data stored in the U.S. or outside the U.S.
> Microsoft admitted that it 'cannot guarantee' data sovereignty
Hm. As for AWS, they say that if the customer sets up proper security boundaries [0], they'll ensure will keep their end of the bargain [2][3]:
As part of the technical design, access to the AWS European Sovereign Cloud physical infrastructure and logical system is managed by Qualified AWS European Sovereign Cloud Staff and can only be granted to Qualified AWS European Sovereign Cloud Staff located in the EU. AWS European Sovereign Cloud-restricted data will not be accessible, including to AWS employees, from outside the EU.
All computing on Amazon Elastic Compute Cloud (Amazon EC2) in the AWS European Sovereign Cloud will run on the Nitro System, which eliminates any mechanisms for AWS employees to access customer data on EC2. An independent third party (the UK-based NCC Group) completed a design review confirming the security controls of the Nitro System (“As a matter of design, NCC Group found no gaps in the Nitro System that would compromise these security claims”), and AWS updated its service terms to assure customers “there are no technical means or APIs available to AWS personnel to read, copy, extract, modify, or otherwise access” customer content on the EC2 Nitro System.
Customers also have additional mechanisms to prevent access to their data using cryptography. AWS provides advanced encryption, key management services, and hardware security modules that customers can use to protect their content further. Customers have a range of options to encrypt data in transit and at rest, including options to bring their own keys and use external key stores. Encrypted content is rendered useless without the applicable decryption keys.
The AWS European Sovereign Cloud will also benefit from AWS transparency protections over data movement. We commit in the AWS Service Terms that access to the EC2 Nitro System APIs is "always logged, and always requires authentication and authorization." The AWS European Sovereign Cloud also offers immutable, validated logs that make it impossible to modify, delete, or forge AWS CloudTrail log files without detection.
Isn't that mostly because as you go up the abstraction layer, tools and docs to teach yourself the tricks of trade fast are in abundance (let alone a popular layer like React)? Which inturn is likely a function of incentives and opportunities.
reply