It's more complicated than that. The US government is currently at war with Iran, alongside UAE and the Saudis as allies. Meta is a US company.
I'd say the US government is more important to Meta than either the UAE or Saudi government. What do you think US government people are saying to Meta about this?
They did say who was blocked, they list 2 NGOs and 2 individuals by name, while also saying "100 others" in the second paragraph. They link to Meta's transparency report for the "100 others".
Those countries are all very different with very different interests in their respective regions. China doesn't care about Ukraine, Russia doesn't care about Taiwan, and both were very muted in their reaction to the attacks on Iran.
The major thing they have in common is not respecting American trade embargoes against themselves, which, of course they don't.
Yeah, and "don't launch wars of aggression or bomb girls' schools on a whim" has been a principle for about the same amount of time.
Iran has been pretty clear that they'll open the strait if the USA lifts the blockade. How can we complain about fair passage while maintaining a blockade ourselves?
The best way to thread the needle I can see was that maintaining highly enriched uranium was a deterrance/bargaining strategy. Doesn't break the fatwa but sends a message. Obviously it wasn't successful, they should have either built a bomb or not bothered, in hindsight.
> Obviously it wasn't successful, they should have either built a bomb or not bothered, in hindsight.
The JCPOA obviated the need for a nuke. It was a reasonable assumption that the US would honor its side of the agreement under the doctrine of continuity. Even in hindsight, you cannot have productive diplomacy without good faith
Iran really had no need for a nuke in the first place if they weren't constantly provoking the entire region, unless that need is destroying Israel.
> Even in hindsight, you cannot have productive diplomacy without good faith
Iran never really negotiates in good faith either, the JCPOA didn't really do anything at all to restrict their ballistic missile program and terrorist proxies.
Why not have a bunch of SRAM and various operations like "Q4 matmul" in silicon? Model weights and even architectures could still evolve on a platform like that.
Doesnt "a bunch of SRAM" top out at maybe a few gigs per chip (with zero area used for logic)? You'd need an order of magnitude more to fit even a fairly weak general purpose LLM model.
Even then, Musk didn't cut fat and then produce multiple revolutionary products. He tanked Twitter's ad revenue and wound up with a much smaller business that had to get bailed out by SpaceX, otherwise it doesn't pay for the acquisition costs.
If you don't ever have a massive PR from a dynamite session, then you cannot ever be better than "average and plodding". So the question is, what's the context of the massive PR and how should it be handled?
* Mature product making money, intermediate engineer just refactored everything so it's "better"? Shut the fuck up, kindly please, you will have to demonstrate that you understand why things are this way and why it's better before we even have this conversation.
* Greenfield dev, trusted engineer getting from 0 -> 1 on something big? Maybe it shouldn't be held up in committee for 2 weeks. Maybe most objections will be superficial stylistic concerns.
Obviously there are many other contexts and these are 2 extremes in a multi-dimensional space. But if the process is "we litigate every line", then that's just not an innovative place to be. Yes, most PRs should be small, targeted, easy to review and tied to a ticket but if you're innovating? By definition it's a little different.
In retort, that's just doubling down that everything should always be average and plodding.
I'm not saying one shouldn't learn how to stage large changes into a mature codebase. Sometimes the overhead is very worth it, maybe most times if you're close to the profit center of a faang. But one should understand multiple ways of working, for different situations.
If you can't be arsed to prepare your code for review because it's such a buzzkill to your velocity, why are you even reviewing then? Just push to main.
I'm not being snarky. I put different review standards in place for different repos on my team. Sometimes the standard is no standard. Push to main. Figure it out later.
> you will have to demonstrate that you understand why things are this way and why it's better before we even have this conversation
I can fling that back to you: very often the team hates the conclusion I arrive at, which is "It worked during your initial crunch and then everyone is just afraid to change it, which means your test coverage is far from good -- why is it not enriched?"
I am not trying to be an arse on purpose but the inertia and cargo-culting and tribe-defending practices I've seen during my contracting years (10-11) made me almost physically sick. Programmers are a fiercely territorial bunch and it's often to the detriment of the organization.
Of course the reverse cases exist: where the domain is difficult and ugly hacks had to be done so the project works and makes money. Absolutely. I love receiving this knowledge and integrating it; makes for interesting engineering discussions.
> Greenfield dev, trusted engineer getting from 0 -> 1 on something big? Maybe it shouldn't be held up in committee for 2 weeks. Maybe most objections will be superficial stylistic concerns.
Yep, full agree. And often times these stylistic concerns are not even that; they are often "I suffered here at the beginning, this green-horn should suffer as well!" which is honestly pathetic and it also happens quite a lot.
reply