Kuwait was “saved” by the US. The Iraq invasion was approved by the GCC, partly as payback for Kuwait, and anyways Iraq is not part of the GCC. The Qatar blockade was self-inflicted (and extremely stupid).
9,721 karma · joined July 2, 2011
All views are my own, etc.
* Homepage: https://assil.me
* Github: https://github.com/aksiksi
* Twitter: https://twitter.com/aksiksi
[ my public key: https://keybase.io/aksiksi; my proof: https://keybase.io/aksiksi/sigs/PhsFUqf4TTQdHrQvnrRhLU4bgilyPjSZjo5DQFHM9QU ]
Kuwait was “saved” by the US. The Iraq invasion was approved by the GCC, partly as payback for Kuwait, and anyways Iraq is not part of the GCC. The Qatar blockade was self-inflicted (and extremely stupid).
This is a battle of economies and regional influence.
A NixOS config is a bit different because it’s lower level and is configuring the OS through a first-party interface. It is more like extending the distro itself as opposed to configuring an existing distro after the fact.
The other big difference is that it is purely declarative vs. a simulation of a declarative config a la Ansible and other tools. Again, because the distro is config aware at all levels, starting from early boot.
The last difference is atomicity. You can (in theory) rely on an all or nothing config switch as well as the ability to rollback at any time (even at boot).
On top of all this are the niceties enabled by Nix and nixpkgs. Shared binary caches, run a config on a VM, bake a live ISO or cloud VM image from a config (Packer style), the NixOS test framework, etc.
I run both right now, but I am in the process of just running NixOS on everything.
NixOS really is that good, particularly for homelabs. The module system and ability to share them across machines is really a superpower. You end up having a base config that all machines extend essentially. Same idea applies to users and groups.
One of the other big benefits, particularly for homelabs, is that your config is effectively self-documenting. Every quirk you discover is persisted in a source controlled file. Upgrades are self-documenting too: upstream module maintainers are pretty good about guiding you towards the new way to do things via option and module deprecation.
So we are going to ignore the JCPOA? Also, the rumor is that there is another player in the region who has undeclared nuclear weapons and refuses IAEA inspections. Should we bomb them next?
And that deployed ship will do nothing. The only way forward is a negotiated agreement.
Uh if you say so. Can you point me to the rule stating that I need to keep engaging in a discussion I am not interested in having?
Second, I don't have much else to say to you if you actually think that assassinating a head of state in the middle of active negotiations is anything but vile & uncivilized behavior unbecoming of a "civilized" superpower.
Ultimately, this is going to be a major strategic loss for the US and Israel. They have achieved none of the goals stated at the outset of this "operation", outside of perhaps diminishing the Iranian missile manufacturing capabilities & stockpile.
And Iran has been respecting that principle for decades. So why exactly did the US and Israel (and GCC countries) think that the status quo would remain even if they keep antagonizing Iran? Imagine getting bombed during negotiations - not once, but twice in a single year! Their sovereignty was being disrespected, so now they're understandably establishing a new status quo.
And btw, if Iran and Oman cooperate, there is no threat to "freedom of navigation" under international law.
In a nutshell: play stupid games, win stupid prizes.
2. Blatantly kidnapping and assassinating heads of state is the culmination of US foreign policy and not an anomaly. The machine is working as designed.
The only foreign policy blunders I would attribute to Trump are the completely unnecessary spats with Canada and Denmark/the EU, although neither blunder seems to have made a dent in the ass kissing.
Or are we not allowed to compare these things because of who the perpetrators are?
And, in the case of colonial crimes, don’t tell me to “let bygones be bygones” until apologies have been made and reparations disbursed.
In the meantime, the West is complicit and can instead direct their holier than thou attitude and patronizing lectures inwards.
Why? Given the nature of how NixOS works (config-driven), the maintainers have plausible deniability: if push comes to shove, they can shift the burden to users and have them enable the age verification service as part of their NixOS config.
I run Proxmox at home, but now that I have been drinking the NixOS koolaid over the past 2 years, all of my homelab problems suddenly look like Nix-shaped nails.
But the only real world impact is that the device that was used to stream that 4K content gets blacklisted at the hardware level.
To workaround this, piracy groups try to batch 4K rips because they know that the device will be burned soon after they upload the content. They then acquire another device, and the game of whack-a-mole continues.
There are some interesting discussions in this HN thread: https://news.ycombinator.com/item?id=46803451
Personally, I don’t see the need for this with NixOS. Setting aside the fact that Omarchy is way too opinionated (Basecamp installed by default?), NixOS is already quite composable, so you can easily build a well-formed experience out of isolated NixOS modules.
Btw, I say this as a huge fan and heavy user of both Nix and NixOS.
Especially given:
(1) The (relatively) fragmented reality of Linux distros and desktop managers. I am sure that such a migration could have been executed faster had the Linux desktop world been more centralized like Windows or macOS.
(2) The age and maturity of X11