Ivan’s Childhood; although all of Tarkovsky’s oeuvre is worth it.
Ivan’s Childhood; although all of Tarkovsky’s oeuvre is worth it.
That’s Alan Turing the traitor as played by Sherlock Holmes?
It is a film with a great list of cheap tropes to avoid.
I’m a mathematician too. They’re probably speaking from an intuitive grasp of utility.
The Tarot of the Bohemians.
I think it’s fairly parochial, and sounds quite infantile to me. Growing up (uk) we just used clockwise to tighten.
“I love life on Earth… but I love capitalism more.”
That was my, admittedly bitter, point, yes. You do have to wonder what the hell weretcollectively playing at.
We live in a world of plenty where we still produce enough food that nobody need go hungry.
It does make me wonder about quantum suicide.
The Sixth Sense.
The beeb. Interviewees were both pro-Israeli and representatives of different Palastinian groups; what could not be distinguished between them was the playground line of blaming the other for their own behaviour.
In the days following the October attacks, the media was filled with spokespeople repeatedly delivering the line, “look what they made us do”.
It comes to the same conclusion regarding the illegality of the weapons, even if it’s pretty lenient in its interpretation of how thousands of devices can be “reasonably expected” to all end up in the hands of combatants.
You’ve linked into it, but I was just going to point at the Git book: https://git-scm.com/book/en/v2
It’s an afternoon’s reading; it does an excellent job of giving you the right mental model - and a crib aheet of commands to navigate it.
I have observed people taking Rust seriously. You need to reexamine your assumptions.
We have an evolved capability to short-circuit decisions with a rapid emotional evaluation. It means as a species we didn’t die out early [“that’s a lion; I’m a oerson; lions eat people ergo… Agh!” is not a sustainable strategy] - what’s amazing is that we can also apply it to elarned abstract things like an aestetic sense about programming languages. Such instincts aren’t always perfect, but they’re still worth paying attention to. I don’t see a reason not to express that in a blog post, but you can replace it with “this is unergonomic and in some cases imprecise” if you prefer.
That seems like quite a lot of booms.
That seems like a non sequiteur. Did you watch the video? Did you hear what the presenter was asking for? Technical feedback on the API semantics they were describing. A heads-up if breaking changes to those APIs were about to land, so they can update bindings. They were bending over backwards to be accommodating. None of this is the entitled behaviour you describe.
It’s what C is for, too.
The point is that there may be cases already where the type system that rust provides its guarantees off the back of is insufficiently expressive. (I say “may be” because there are ingenious qays to use what it does provide, although nonobvious and not necessarily without cost.) If you’re using unsafe
then it’s just an uglier C. I don’t think anyone considers the current state of Rust’s type system to be the be-all and end-all of expressivity.
That’s an interesting notion (although it underestimates the effort, I think). Honestly, having machinery to write down contract semantics in a fashion amenable to automated proofs (meaning, does it type-check?) is massively promising; and I’m a dyed-in-the-wool C hacker. I would hope that the public exposure of this bad behaviour causes a few moments of self-reflection.
I suspect that attempting to chase a moving target of describing C apis with rust is just an avenue for burnout, unless there really is a mechanism for getting fixes back in the other direction, and professional respect flowing in both directions. That would be a massive shame, and an incredible missed opportunity.
Antibiotic-resistant communicable diseases don’t respect political borders.