• 0 Posts
  • 56 Comments
Joined 11 months ago
cake
Cake day: August 8th, 2023

help-circle
  • You are aware that what Israel is doing in Gaza is comparable to the nazi treatment of e.g. the Warsaw ghettos… right?

    Take a step back, and look at the Israeli soldiers mocking Palestinian dead, mistreating the wounded and captured, and shooting at clearly unarmed civilians for fun. All this while they brag about it on video. Look at that and tell me that it doesn’t give you a sick feeling to your stomach of the type you haven’t had since you saw photos of concentration camps.

    There are dozens of children that have literally STARVED TO DEATH in Gaza because of Israel’s actions. They’re dying the same deaths that Jews were put through in concentration camps. Don’t you see the horrifying irony in this?

    Israel is at a point where humanitarian workers from recognised international organisations have been targeted and killed, and they brush it off as a “mistake”.

    I cannot think about anything in the past 70 years that compares to what Israel is doing, and I hope beyond hope that some force will smite their government and armed forces such that the slaughter will stop. Because it is a slaughter. It’s not a war when Israel is counting its dead on its fingers, while there are enough missing Palestinians in the rubble to fill a football stadium. It’s just Israel wilfully bombing, burning and slaughtering, with nobody stopping them.

    All this, and you have the fucking audacity to talk about antisemitism? Take a look at the world, and ask yourself how calling for an end to this can have anything to do with the religious beliefs of the perpetrators.




  • I am very fond of the idea of “stateless” code, which may seem strange coming from a person that likes OOP. When I say “stateless”, I am really referring to the fact that no class method should ever have any side-effect. Either it is an explicit set method, or it shouldn’t affect the output from other methods of the object. Objects should be used as convenient ways of storing/manipulating data in predictable/readable ways.

    I’ve seen way too much code where a class has methods which will only work"as expected" if certain other methods have been called first.


  • Sounds reasonable to me: With what I’ve written I don’t think I’ve ever been in a situation like the one you describe, with an algorithm split over several classes. I feel like a major point of OOP is that I can package the data and the methods that operate on it, in a single encapsulated package.

    Whenever I’ve written in C, I’ve just ended up passing a bunch of structs and function pointers around, basically ending up doing “C with classes” all over again…



  • This makes sense to me, thanks! I primarily use Python, C++ and some Fortran, so my typical programs / libraries aren’t really “pure” OOP in that sense.

    What I write is mostly various mathematical models, so as a rule of thumb, I’ll write a class to represent some model, which holds the model parameters and methods to operate on them. If I write generic functions (root solver, integration algorithm, etc.) those won’t be classes, because why would they be?

    It sounds to me like the issue here arises more from an “everything is a nail” type of problem than anything else.




  • I mean, in a perfect world, yes. The issue comes up when someone wears out or breaks the drill, and it needs to be replaced or repaired. Whoever spends time and resources ensuring that we have a drill needs to be compensated somehow, because that’s time they’re not spending on making sure they have food and shelter.

    Follow along that line of reasoning for a couple steps, and you end up with some kind of economic system, and likely some kind of enforcement system, so you’re suddenly back at an early stage proto-state/government.


  • You’ll survive for quite a while once you’re below 6000 m. In free fall that would take you around 90 s, assuming a fall from 11000 m, and that it takes 200 m (5 s) of fall to reach terminal velocity of 200 km/h.

    This is quite rough, but gives an appropriate order of magnitude. In those 90 s, you would be very likely to pass out and be guaranteed to get severe frost bite. We’re talking major amputations levels of frost bite, as you would be moving at 200 km/h, exposed, in temperatures in the -50 C to -10 C range. I’ve seen people get frost bites moving at 40 km/h in -15 C for a couple of minutes with just a sliver of skin exposed.

    So short answer: You might survive getting into the survivable range, but at the very least you will require intense and immediate medical attention upon landing. Seeing as there will be potentially a couple hundred people spread out over a large, possibly remote, area requiring this attention, it’s unlikely that many, if any, would survive the ordeal, even if most people survived the initial 5000 m of fall into the survivable altitude range.









  • I have to be honest: I dont see the problem of including the entire signature at the top of the doc, and the listing the params below. If I know the class/function, a quick look at the signature is often all I need, so I find it convenient that it’s at the top of the doc. If it’s a class/function I’m not familiar with, I just scroll to the bullet points.

    I agree on the bit about whitespace in signatures though. Luckily Python allows me to use as many lines as I want within a parentheses.