Technical jobs yes. Infantry still requires a lot of physical strength. I'd welcome anyone who has that strength to be in the infantry, but anyone who can't, male or female, should not be in the infantry, or any job that might require dragging heavy people or heavy equipment.
Can someone explain to me how the Selective Service is constitutional? I know Congress "shall have Power To... provide for calling forth the Militia to execute the Laws of the Union", but that's only a call, not a legal requirement for anyone to answer the call. The argument seems untenable to me. Not to mention that it's a gross violation of individual freedom, and that if you can't get people to fight for their country then maybe there's something wrong with the country.
It’s the same reason there is a different legal system in the military than for everyone else.
Sometimes, you need to round up all the men and start killing folks - or everyone else dies. Such is life. Making it easy to find them is a basic operational best practice.
> Countries and most borders are just an abstraction.
Not true. Patriotism is very real. It's an affection for a group of people and for the ideals of those people. To some lesser extent it's also love for the geography of your land. But patriotism is rarer in the west than it once was. Also, if a country's territory is invaded by an enemy, at least some of its people will go to fight to protect their families from the oncoming enemies.
I'm probably going to get flagged for this, but here goes anyway.
Russia absolutely has reason to not want Ukraine to join NATO. I'm not condoning the invasion, but I say it absolutely makes sense for Russia to carry it out. Not a reason to commit war crimes, or to cause any more suffering than necessary, but from a national security perspective it makes sense to want to disrupt the process of Ukraine joining NATO.
Only if you accept the hidden assumption that Russia is an antagonist toward the rest of Europe. Otherwise the common "national security" justifications make no sense, because Russia benefits immensely from other NATO members investing resources into the development of institutions in newer member states.
A former Russian foreign minister has labeled NATO "free-of-charge security" for Russia, because NATO membership requirements turn a country into a stable and predictable place. The best neighbors Russia has are in NATO, and much of that stability is directly attributable to their membership.
Would they do that for an international departure? They know where you’re flying, and I’d think they’d just tell you to stop being an idiot and show them the passport you obviously must have. But policies can be weird, so maybe not.
Yes, that's what I said above. The US government doesn't give a toss, but the airline has to fly you back if you're refused entry at your destination, so they will do their best to ensure you have the documents you need.
I'd just like to interject for a moment. What you're referring to as Linux is in fact not the origin of the "everything is a file". More properly, "everything is a file" is a Unix concept and Unix's creators deserve credit for the idea. Though Plan9 carries it out much better: Unix networking isn't file-based, Plan9's is.
> I'd just like to interject for a moment. What you're referring to as Windows, is in fact, NT/SlopPilot+Windows, or as I've recently taken to calling it, Copilot plus Copilot plus Copilot.
Plan 9 implements some sort of "everything has a directory entry" concept. Sockets are files already in Unix. "Everything is a file" in Unix means they have a uniform treatment as file descriptors. Its perfection is probably in Capsicum where when you create a new process, you get a process file descriptor referring to it instead of a PID.
As much as I like bsd I think the socket interface is their biggest failure, don't get me wrong, the socket interface is not bad, it is an amazing accomplishment that most of the internet is based on. The reason I regard it as a failure is because it is so close but not quite touching. A core unix idea is to have a single namespace registry and a simple universal api(open, seek, read, write, close) to access resources on this registry. and you can tell the bsd socket team was trying(like I said it's close) but they failed to close the loop and shipped an api that did not match the core unix api.
And for free, a rant, I think this is why Microsoft's registry is so bad. On paper it sounds great "a single place to put all your config" I could totally sell it. But in practice it is miserable to use. When proposed nobody said "we already have a hierarchical namespace where all our config can go and it already has pretty great tooling, lets just make it better" so they invented a custom one that required custom special access patterns and custom special tooling and custom special api's, and... it sort of sucks to use. I guess in their defense they were not fully onboard the idea that you could have one tree(they liked their many trees A: B: C:)
You do read sockets with read/write, that's the point of saying 'everything is a file'. You can basically can do read/write/close on things that are a socket.
reply