That "worst case scenario" (RCP85) was projecting a 5°C increase by 2100; the current trajectory still puts us at a 3.5°C increase by 2100, whoop-dee-doo. The "avoid climate change scenario" (< 1.5°C by 2100) is also rapidly becoming unattainable.
But in that case, you need to compare like-for-like with the situation where you need to insert all the prerequisite rows too. You can't just compare a delete cascade with a single insert where all the foreign keys are already satisfied.
The whole problem with the delete cascade is you can't tell how big it will be until you have entered the transaction to do it. An insert you either know or it will fail and you can retry.
That's true, but now you have moved the goalposts. The original claim upthread was "it takes just as much work to delete a row as it takes to insert a row", not "it's hard to predict the performance of a delete with cascade effects". And the obvious rebuttal to that is that it's equally hard to provide an upper bound for the runtime of a single insert: an application cannot control the other processes running on the database, some of which may delay, interfere with or even invalidate your query and you must account for that. A delete operation is just as much "it might fail and you can retry" as an insert, or the database you're working with isn't ACID-compliant.
> And the obvious rebuttal to that is that it's equally hard to provide an upper bound for the runtime of a single insert
This is precisely where you're going wrong. The insert is upper boundable in advance (you know the set of everything you might potentially have to insert), the delete isn't because you don't know what's in the db until you look.
I strongly recommend poking around with Foundation for this, because it becomes clear that this problem is the defining flaw with the way they tried to architect with layers, to the point they have a queuing system for processing large jobs of this type.
A concurrent DML happening then suddenly your MERGE INTO WHEN NOT MATCHED INSERT/INSERT INTO SELECT is way larger that you thought? I thought "some workloads can suddenly be way larger that I expected" was supposed to be a thing in all non-trivial DML.
For every cell mechanism that's being abused by cancer to fuel its growth, there are other cells in the body for which that mechanism is crucial for their correct functioning. Wholesale editing every cell in the body mostly guarantees that the patient does not die of cancer -- the cure will kill them before the disease does.
No, a mechanism that acts on every cell on the body doesn’t mean it changes every cell. The primary problem with gene replacement therapies is they cannot be effectively delivered to every cell. If we can find a way to deliver to every cell than just the ones with the right signature will get the changes.
The primary European failure here has been to allow the hollowing out of the EU tech space. There have been plenty of web tech players in the EU; the US policy over the last 30 years has been to absorb them into US companies or buy them off using US capital, and the EU strategy has been to very much encourage that.
But it is complete fantasy to use the current landscape as evidence of capability. It would be equally shortsighted to say "How would the US replace Chinese manufacturing? There simply are no equivalent supply chains in the US, regardless of pipe dreams that pedophile sycophants regularly conjure up. The US seems hellbent on becoming poor and economically irrelevant".
It never ceases to amaze me how people scramble to defend the EU's failed policies over the last three decades. The EU managed to regulate itself out of all relevant markets and it only has itself to blame.
The EU lost its manufacturing capacity to countries with cheaper labour, just like the US. The US has only succeeded in IT, everywhere else it struggles against Asia.
The ‘American dream’ attracted a lot of talent (look at how many tech leaders were immigrants), and once the network effects (both IT and social) kicked in it was hard to stop. This is a story that has unfolded many times throughout history. Talent moves to where talent is. And it will move if conditions change.
You’re missing their point, they’re not defending EU policy and in fact agree that current capability is poor. They’re saying that it can change and that the US is also self sabotaging in other ways.
> YouTube is an example of a site that Firefox has trouble handling
That's fully on Google. I use plenty of other streaming sites where Firefox handles full-screen video just fine. Coming from the web search company that penalizes the rest of the Internet for slow-loading pages, Youtube is basically an embarrassment and I'm convinced this is completely intentional.
It's gotten so bad that I don't even try to watch Youtube in-browser any more; when someone posts a link that I think might be worth the effort, it goes straight into youtube-dl and I'll watch it offline or not at all.
> Freedom of DNS choice has nothing to do with DoH
The attack vector that DoH offers is that data exfiltration companies will start shipping their own DNS resolver in javascript to work around DNS-based filtering. They can't do this with regular DNS because the network traffic can still be observed and blocked independently, but how will you block a browser from accessing specific https URLs without MITM'ing all traffic?
So yes, DoH does have something to do with DNS choice: it can completely subvert the OS-provided domain resolver service as well as the browser-configured one.
reply