You can’t 10x the number of lawsuits, as the courts are already at capacity. If frivolous lawsuits become common they’ll just change the laws to require a greater damages for it to be heard.
Lawsuits are just one type of legal services. There will also be more contract reviews, more cease-and-desist letters, more patent applications, more regulatory comments, more license applications, etc. Although I do expect legislatures will eventually budget for expanding civil court systems in response to lobbying from business groups to speed up trials.
And remember how Iran slaughtered tens of thousands of its own citizens a few weeks prior. And the continual killing of Iranian citizens having differing political options of the regime.
War is never pretty or perfect. Winning a war comes with great cost
Killing civilians and destroying infrastructure in the name of saving oppressed people; it's quite impressive such low-effort imperialist propaganda still works after Iraq, Afghanistan, Syria, Libya.
> And remember how Iran slaughtered tens of thousands of its own citizens a few weeks prior. And the continual killing of Iranian citizens having differing political options of the regime
So, that's over, then? We changed the regime and now things are better?
The purpose of starting a war is to extract concessions from the other side that you were unable to get through diplomacy, not to kill a lot of people because you think they deserve it. So far Iran has not been willing to make any concessions that it wasn't willing to make before the start of the war, and has shown that it can disrupt Gulf oil exports, which it didn't do prior to the US starting the war. Nothing has been achieved besides pointless bloodshed.
You talk about it as if America cared one bit about those citizens. This war just made the regime stronger.
If America succeeded, it would change the head, steal oil and keep the regime there to keep control on locals. Like in Venezuela. Maybe committing few atrocities on top of it.
But also of course, it would then invade Cuba and Greenland and god knows who.
Eh, as much as I might dislike the government of my country, I think I believe I would hate a lot more the country that decided it was a good idea to blow schoolgirls from my country into minced meat.
Invading a country and wanting to steal their resources at any cost, a cost as large as needed, is a crime against humanity.
The USA is not defending itself, it is just trying to control Irans oil to increase the power of American economic elites. Billionaires want more power, children, women and men die indiscriminately because of that.
And, you are totally right. Billionaires does not care that winning a war comes with great cost, because the cost is for USA service men and for all Iranians.
Most startups can just scale your traditional separation of compute & storage here though. You’d be shocked how well duckdb against s3 scales for 99.9% of use cases
It's one thing to be able to scale database compute/storage; it's another thing to be able to partition it. It's extremely common for bad queries/access patterns to cause noisy-neighbor effects on other simultaneous accesses to the database, to the extreme of knocking the whole database over with timeouts/OOMs/etc.
Scaling out DB compute can only help with that to a (expensive) point; eventually, you end up wanting to either prevent the bad queries from being added to the system (DBA culture) or ensure that the bad query runs on database infrastructure that doesn't affect other queries. That's why partitioning DB compute (and storage: noisy-neighbor effects from a bad query at the storage layer don't require storage to be running e.g. a BookKeeper or whatever on a server; they can manifest as hot S3 keys or cloud object/block store rate limiting) is a necessary capability if your plan for dealing with a culture of "anyone can add any access pattern they want" is to scale the DB.
Iceberg & Delta Lake do partition the data. You can add as many DuckDB servers processing them as you want, each app can have as many as you need. You pay Amazon for all the I/O and let them worry about it scaling it.
I'm not saying there is no point of contention - depending upon your write patterns you have practical limits, but for reading data that is already stored you pretty much just pay more to do more and the rate of that cost is close to linear.
I'm sure there is a scale at which that pattern breaks, and I'm sure 99.9% of people reading this will never operate a system at that scale.
Iceberg addresses the hot s3 key prefixes. It places entropy in the prefix path per object so reads/writes are randomized over the bucket key prefix space.
It’s much less of an issue. Also, 99%+ of Aws customers likely don’t have enough QPS to hit the per prefix limits anyway
Most software developers now are absolutely ignorant of performance concerns. Just throw more compute at it until it works, and someone else will pay the AWS bill.
I have AI confirm the logic works as expected, but review for system design.
Often in both web/backend I’ve found AI to produce overly duplicative code, or have aspects that could be hard to maintain. Generally less due to the AI, and more because of the prompt itself.
That and even if you’re going to AI slop it up, I’d still demand it be broken up into 1-2k LOC chunks or per meaningful “thing”. This also lets us gradually ramp the change to confirm it actually works earlier on
And that is exactly why AI marketing touts ability to replace programmers, when in reality it is much better suited to replace middle management between client and programmers...
It’s faster than trino and spark for 99% of your use cases. Only once the datasets reach the 100GiB to TiB range is trino/spark faster. Compute is scaling vertically faster than Data Eng/Analytics dataset growth, over time DuckDB will be the better choice.
reply