What? Settlers are totally tolerated and supported by the state. Look at Ariel, it is a fully established town settled almost 50 years ago with a university that operates in every practical way as part of Israel. If you think the government doesn't support them, what would support look like?
> From where I sit nobody is questioning that the Israelis are supposed to be the good guys in this story.
That's a baffling claim.
Israelis emphatically not being "the good guys in this story" is a very mainstream (though not necessarily majority) view in every country in the world, possibly with the exception of Israel itself.
Gaza has been under a near-total naval blockade since 2007 (which is an act of war BTW). Any meaningful "reduction of tensions" would have included lifting that.
What he’s saying is that you need to vote with a consistent message. Voting for Bush, then voting for Obama, then voting for Trump is unlikely to make any lasting change
That’s the separation of powers at work, which is desirable. Congress has to (and can) do it. Obama, unlike Trump, would sometimes back down when he met the edges of executive authority. That’s how it should be.
I wanted Gitmo closed, but I don’t want it closed in a way that further expands the executive branch by once again nibbling at the edges of another branch’s authority.
Plenty of countries that are well-run democracies don’t have separation of powers between the legislature and the executive — the UK is one of many examples.
Separation between the executive and the judiciary is important, but separation from the legislature doesn’t really seem to be.
Even among countries that do have such a separation, the US is unique in making it so difficult for the legislature to pass anything, which IMO is the most serious flaw in its system. The permanent deadlock is what creates such a temptation for the executive to circumvent the rule of law and try to seize power wherever it can.
At ~all times for a long period of time during Gitmos operation, there was at least one (revolving) prisoner that no nation on earth would take. I think that was the biggest challenge for someone who actually wanted to close gitmo, to close it. Not clear where you would put them that wouldn't be yet another prison.
I guess now that the US has normalized relations with the Taliban, maybe they'll end up sending them to them, not sure who else will take the last ones.
They should stand trial in a US court, and if they’re acquitted, they should be set free, like anyone else. That’s a pretty fundamental principle of the rule of law.
If they’re indeed innocent and can’t be deported because nobody will take them, then they have to be allowed to stay in the US. That’s unfortunate but not really their fault given that the US brought them into its jurisdiction against their will in the first place.
It seems transparently unfair to capture someone and then keep them forever because nobody else wants them.
A lot of them were captured for things like simply having an F91W watch and also being proximal or familial to a terrorist. They were initially wanted but then once 'cleared' the problem became once accused as a terrorist no country on earth wanted to take them even if they were cleared as likely innocent.
Obviously it was also politically infeasible to admit them into the general US.
FWIW, the GP comment's claim that you're lucky if you can compile 2-year-old code is exaggerated, but so is yours. Rust does not offer "strong stability guarantees". Adding a new method to a standard type or trait can break method inference, and the Rust standard library does that all the time.
In C or C++, this isn't supposed to happen: a conformant implementation claiming to support e.g. C++17 would use ifdefs to gate off new C++20 library functions when compiling in C++17 mode.
> and the Rust standard library does that all the time.
I don't doubt this is true, but do you have an example? I think I haven't run into a build breaking like this in std in like maybe seven/eight years. In my experience breaking changes/experimental apis are typically ensconced in features or gated by editions.
Granted, it'd be nice to be able to enforce abi stability at the crate level, but managing that is its own can of worms.
I did find that the breakage rfc allows for breaking inference, which tbh seems quite reasonable... inference is opt-in.
Almost every major release of rust stabilizes new library methods. For example, the latest major release (1.93) stabilized Vec::into_raw_parts. This isn’t gated by an edition. So if you had a trait with a method “into_raw_parts” which you had defined on Vec, after updating to 1.93 or later your code will either fail to compile, or start running different code when that method is called.
Sorry, I meant to write “method resolution”, not inference. This isn’t the same issue as type inference (though indeed, stdlib changes can break that too)
will only terminate if pasted into a REPL, not if invoked from a file.
This is because every top-level form in the REPL has an implicit continuation "return to the REPL and read more input".
So after "continuation called" is printed, we go back to the prompt and await more input.
However, if this code is saved in a file and you run it (e.g. "guile my-script.scm") then the continuation of the top-level `displayln` call is the top-level `begin` form, and we enter an infinite loop.
Curious why you responded to this comment in particular when 90%+ of the comments express roughly the same sentiment.
A world in which people are entertaining their kids with AI-generated slop seems self-evidently horrific and it’s normal for people to want to push back on that.
I guess because (1) It was the top comment at the time, (2) there were a lot fewer comments at that moment; (3) it was more personally critical than the others (though again, I'm sure that was unintentional).
reply