WW1 happened due to the crazy web of treaties between nations. It's not unlike nuclear holocaust and MAD doctrine. There could have been other triggers for WW1, but that's not really a guarantee.
That is to say, definitely possible and maybe even likely but not inevitable.
There's an argument to be made that WWI started because Wilhelm II was an incompetent statesman who disassembled his country's relationship with friendly states, and turned them into enemies.
Several leaders were itching for war, to build empires. Emprice building was normal to them as was going to war to achieve it. They opinions we hold today on war (largely from reflecting on the world wars) are not the opinions they had about war.
They gave commands to prepare for war and just needed the excuse to say go. I think the not-war outcome was very unlikely.
Which leaders? I don't believe any of the players thought they would gain empire in Europe. Everyone was trying to be defensive, combined with slow communication and poor politics. Now that historians have access to much of the internal documentation it doesn't seem like an inevitable war. If only the Habsburgs had been more decisive, or Wilhelm more politically astute, instead of making grand gestures then going on a boating holiday with his British naval mates.
It's not that they needed an excuse to say no, it's that they each thought backing down would be worse. And tbh I don't think any the current leaders are better. Nicholas II "I will not become responsible for a monstrous slaughter" vs Putin's war of choice.
He asked for his country to go to war more than two dozen times leading up to the outbreak. Ferdinand was the main opposition to his desires
The first episodes to the YT channel go into many of the details. I really like that group, they make week-by-week war documentaries with many mini-series on special topics. Top notch content and production quality.
The issue, as I understand it, is that someone with standing to sue over the 4th amendment would be prosecuted under a FISA court. Those cases due to how the court was created and structured, do not end up in front of the supreme court.
It's one of those weird things in the US constitution which allow for congress to create new federal courts which don't ultimately fall under the jurisdiction of the regular federal courts.
The FISA court only handles warrants, not prosecutions. Generally the only parties involved in a warrant request to a court (FISA or any other), are the judge and the government representative(s) seeking the warrant, though the court can pull in third-parties if it wants, e.g. for advice on legal questions.
A secret criminal prosecution trial would be unconstitutional under the Sixth Amendment ("In all criminal prosecutions, the accused shall enjoy the right to a speedy and public trial"). Though SCOTUS has unfortunately allowed for some classified material to be kept secret, sometimes (IIRC) even from the defendant and the jury, though usually this is ancillary stuff, not the direct evidence that would secure a conviction.
Warrants are what's at issue when the 4th amendment is in play. The thing you can't do when FISA issues a warrant is get the details about that warrant, who issued it, why it was issued. You can't even know that a FISA warrant was deployed against yourself.
Yeah, I really think we are on the cusp on the difference between SOTA and cheap models is small enough that paying 10x or 100x the cost makes no sense.
It also helps that a lot of effort has already been spent figuring out how to do more with weaker models because SOTA 1 year ago was behind what the cheap models do today.
1 year from now, unless the SOTA companies come up with something truly revolutionary they will be in a lot of trouble.
> and this famously failed, along with every attempt to fix it.
What was the cause of failure? I see that it is now deprecated which surprises me. It was my understanding that large portions of this were taken from the Java memory model and in the JVM, it seems to have been pretty successful.
Is it because the compilers themselves refused to respect it?
The C/C++ memory model starts with Java's data-race free memory model, but makes data races fully UB. Atomics are introduced into C/C++ that allows fine-grained definition of synchronization, with four different models of atomics: sequentially-consistent (equivalent to Java's volatile), release-acquire, release-consume, and relaxed (which are not synchronizing and are therefore closer to a defined data race than proper atomics). The Java 5 memory model doesn't have the concept of atomics, except that volatile variables act like C/C++ sequentially-consistent atomics.
Relaxed atomics took a couple of tries to specify, and still have a known out-of-thin-air hole that people are still struggling to solve. But the problem with relaxed atomics is that the practical operational semantics are pretty clear, but the formal model is quite tricky for various reasons.
Sequentially-consistent matches the model that most people naively think is going on in hardware (execute a single instruction at a time from a random thread). Release-acquire is a slight relaxation of that model that works well most of the time; the main difference between sequentially-consistent and release-acquire is that release-acquire requires you to specifically release and acquire on the same memory location to get the synchronization, whereas sequentially-consistent synchronizes across different memory locations. Since most multithreaded code tends to have a concept of something like a lock or mutex that is guarding access to a particular region of memory, release-acquire is usually sufficient.
Release-consume is supposed to be release-acquire, but only for data-dependent loads of the consume. This is the only part of the memory model that has really failed, and that's because compilers cannot really guarantee preservation of data dependence in the optimizer. (This also comes up with pointer provenance, FWIW).
As my sibling comment from jcranmer points out, it was only `memory_order_consume` that failed outright. The other aspects of the C++ memory model mostly worked out, at least after revision.
I believe the last attempt to come up with a comprehensive new proposal was P0190 (https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p01...), which reduced the ordering-imposing dependencies in the model to essentially just be pointer dependencies (which does eliminate some legitimately useful cases, e.g. stealing bits from pointers). The paper mentions the unresolved problem of control dependencies from compiler knowledge of pointer equality, which is intertwined with the pointer provenance discussions from around the same time.
I would like to see the basic concept realized in another language some day.
There was no reason to strike Iran in the first place. The absurd claim that "they were about to get nukes in 3 days!" is something that Israel has been claiming for 20 years. Our own intelligence agencies have said that they were not developing nukes.
If this was a military command center, this would still be a war crime. The US was not at war with Iran before it attacked them.
This was a stupid war to get into and it’s been prosecuted embarrassingly poorly, but Iran has been sponsoring terrorist groups all over the world for decades. They’re not some innocent country going about their business who was suddenly attacked unprovoked.
> but Iran has been sponsoring terrorist groups all over the world for decades.
Let's say I grant this. The problem you run into is these terrorist groups have not attacked the US. The last time Iran did anything aggressive towards the US was in the 1980s.
In fact, Iran has aided the US in going after common enemies like ISIS/ISIL and Al-Qaeda.
The terrorist groups supported by Iran have primarily been groups fighting Israel, not the US. That's what makes it particularly unprovoked.
In fact, the US has a stronger argument to attack Saudi Arabia than it does Iran because they actually have funded terrorists that directly attacked the US. Heck, you could argue that the US is justified in directly attacking Russia with this sort of argument.
Last time wasn't 1980s. 2024 was the Iran-Israel war, but US was involved too. Iranian proxies attacked US troops then. Iran itself attacked US forces in 2020 after the US killed general Soleimani, after years of Iran's proxies attacking US troops in Iraq etc. It goes back and forth, and I'm sure the bottom of it was the US being involved in the Mid East for no good reason (the reason was Israel/AIPAC), but this didn't start in 2026.
Even the Russian invasion of Ukraine wasn't unprovoked. Yeah Ukraine didn't attack Russia, but they did try to join NATO, then after Germany blocked that, the US was getting involved there in more covert ways. Ukraine overturned pro-Russia Yanukovych's presidential election in '04 which saw meddling from both Russia and US, then he reran and won in '10, then Ukrainian protestors forcibly removed him in '14.
I think the least provoked thing was the Iraq War, cause Bush blamed Saddam Hussein for 9/11 and fake WMDs. He was a legit problem ever since invading Iran and Kuwait, but that wasn't the reason for the war.
It actually hasn't "gone back and forth". That's the issue. What you have is 2 good examples of Iran being attacked, unprovoked, and then responding to the attack and STILL after those attacks trying to establish peace negotiations.
For the 2024 conflict I see no indicator that US troops were involved, other than providing defensive support for Israel. Iran didn't target the US even as it was shooting down their missiles and drones.
Nope. It was a proxy of Hezbollah who Hamas, Iran, and Hezbollah all condemned. And after the US attacked Iran in retaliation, they again de-escalated.
> Houthis also attacked US ships if you count that.
This is probably the best example of the point you are making. It was because of Israel's actions in Gaza, but yes, this is a case of an Iranian proxy attacking US ships.
Look, I'm not saying Iran is great or their government good. But I am saying they have been pretty level headed towards the US for quite some time. The main reason the US comes into any sort of conflict with them is Israel and Israeli aggression in the region.
For better or worse, Israel is our ally, and countries go to war on behalf of their allies being attacked.
And yes, the US has a valid argument for attacking Saudi Arabia for funding terrorists that have attacked the US. That they have not does not in any way bolster your argument.
Sorry, there’s just no rational argument for the idea that the US attacking Iran was an unprovoked war of aggression and thus a war crime.
At least originally, servo was just an experimental browser with the intention to carve up useful parts and send them back into Firefox. I believe firefox's current css parser came from servo.
Their origins are in C++, which is what SerenityOS has used. They've never done zig. They explored using Swift as a C++ successor language for the project[1], but seeing the platform support out of Apple was lacking, they gave up and made the bet on Rust[2].
The motivation to use a memory safe language as the alpha approaches sounds more of a longer term bet [3].
They did start with C++. They experimented with Swift, then experimented with Rust, ultimately choosing Rust. I don't see how experimenting with things makes anything "not serious". If you don't question your primitives and just accept them "because that's how it has always been", you're not a very good engineer in my book. In any case, the tech stack is not in constant flux as you claim, it's still C++, with more and more parts moving / being started in Rust, with the eventual probability of Rust replacing C++ organically, I suppose. Seems like pretty sound strategy to me to slowly, but surely, adopt a memory-safe language.
> This idea that the state has a monopoly on getting money from doing a thing that you are saying is bad doesn't make sense.
It makes a lot of sense. Here in Idaho, hard alcohol can only be sold in state run liquor stores. The stores aren't advertised and the staff is all well trained. People that want booze can still get it, but at the same time it's not being ran like a business (It still turns a profit). That is to say, there's no advertising or marketing for it.
> If it is bad and yet the government is allowed to use it to make money then is the government evil?
People are going to gamble if they want to. Making it illegal just pushes them to underground gambling. Making it state ran allows the state to better control the gambling, including doing things like having the ability to provide recovery options and interventions.
> Why does the government get to do it if we can't?
The government isn't motivated by (just) money. They don't have to advertise for gambling and they don't have shareholders to make happy. They could even operate the gambling at a loss if they wanted to.
> It just makes the whole thing seem ridiculous and makes underground betting seem like I guess it isn't really that bad since the government is allowed to do it.
Completely the opposite. The government doing it happens to stop underground gambling from happening. You can sue the government and expect them to treat you fairly. Underground gambling, on the other hand, has no reason or motivation to treat it's participants fairly.
It's not unusual for us to end up with bad query plans because the shape of our data can vary pretty greatly. In many cases, a Foo has 1 Bar. But in some cases, a Foo has a million Bars. That can cause the query optimizer to treat lookups on the bar table as if there are few elements there (causing a scan instead of a seek).
For the general case, the optimizer gets it right. However, the fringe case is one that causes the entire system to crash. It's a bit akin to how an insertion sort can be faster than quick sort when n is small. The optimizer might make a bad assumption about the size of n which makes it pick an expensive n lookup when log(n) is available (but slower for small n).
I mean, probably not technically due to some EULA you were forced to sign which says the hardware is actually Google/samsung/etc and not yours. Giving them the right to brick your phone the moment you step out of the bounds they define.
We really need some sort of open firmware legislation that mandates manufacturers of computer components need to opensource their drivers and firmware. There's no "special sauce" in that software that warrants a company being able to keep it secret. It's literally just so they can force you to purchase new devices when they get bored of supporting their old devices.
Agree, what I'm saying is "it is mine and we should treat it as mine, same as my laptop/desktop." We both agree the current status quo is not that, I'm saying what it should be.
WW1 happened due to the crazy web of treaties between nations. It's not unlike nuclear holocaust and MAD doctrine. There could have been other triggers for WW1, but that's not really a guarantee.
That is to say, definitely possible and maybe even likely but not inevitable.
reply