My personal tale on this is that given that the brain contains chaotic circuits (i.e. circuits in which tiny perturbations lead to cascading effects), and these circuits are complex and sensitive enough, the brain may be inherently unpredictable due to quantum fluctuations causing non-negligible macroscopic effects.
I don’t know if the above is the case, but if there’s anything like free will out there, I’m inclined to believe that its origins lie in something like that.
I love pedantry <3 I got the “three medals per event” from some Wikipedia page, and I know they love pedantry over there as well, so maybe you should make a contribution?
In 2020 there were 448 events at the Olympics, let’s round up to 450. Each event gives 3 medals, for a total of 1350 medals. The Olympics are held every four years, so that 337.5 medals are awarded in an average year.
There are about 8.1 billion people in the world. On average, 0.000004 % of the worlds population receives an Olympic medal each year.
If this were a completely random yearly lottery, and you lived for 100 years, you would have about a 0.0004 % chance of winning an Olympic medal in your lifetime.
I would count myself lucky if I won that by the time I was 50.
I can’t post my memes on the much room bulletin board for everyone to see unless I print them :/
Very dense, yes, but stuff can be very dense and have low viscosity at the same time. Lava has a viscosity similar to peanut butter is what I’ve heard. You can push stuff down into it, it just requires some force to prevent the stuff from floating back to the top.
You could in principle walk on lava, either by moving quickly enough that you stay on top, or by protecting your legs enough that you could sink in maybe around knee deep where you would float.
Honest question: Are there no limits in the US to what you can legally name your child? Where I’m from a name can be rejected if it can “cause significant harm or inconvenience to the child”. This prevents idiots from naming their child “Traitor” or “Terrorist”.
Please tell me how, getting up at 5 (and going to bed at 21) is going to give me more time than getting up at 7-8 and going to bed at 23-00.
Also, I would like to know why “society” thinks you are “better” if you exercise at 6-7 before work, rather than 20-21 after work.
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…
I would argue that there are very definitely cases where operator overloading can make code more clear: Specifically when you are working with some custom data type for which different mathematical operations are well defined.
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.
Oh, thanks then! I’ve heard people shred on OOP regularly, saying that it’s full of foot-canons, and while I’ve never understood where they’re coming from, I definitely agree that there are tasks that are best solved with a functional approach.
Can someone please enlighten me on what makes inheritance, polymorphism, an operator overloading so bad? I use the all regularly, and have yet to experience the foot cannons I have heard so much about.
Did you read the text on that graphic?
… land conversion for grazing and feed …
I’m not talking about meat production in general (which I think should be minimised), I’m specifically talking about meat production from land that is not viable for other uses.
This was exactly my point: I’m legitimately interested in how that graphic looks if you consider meat produced on land that cannot be used for other types of agriculture, and which is local so that transportation is a negligible cost, and feed production is close to non-existent, because the livestock primarily lives off the land.
It seems like you’ve misunderstood what I’m trying to say. I’m saying that
A) There are legitimate reasons for a country to want to have some degree of self-sufficiency.
B) The environmental impact of producing meat is hugely different depending on how the livestock gets its food, and the environmental impact of transporting goods cannot be neglected.
C) There are countries with terrain suitable for livestock that cannot be used for farming.
Of course: Almost no countries are, or need to be, 100% self-sufficient, because we have trade, but there is a huge difference between 10% and 50% self-sufficiency. If we are to cut out meat entirely, many places would be incapable of maintaining any notable degree of self-sufficiency.
With you third paragraph, it seems like you actually agree with me. I don’t know how you got from me saying “there are legitimate reasons to produce meat”, to me saying this is a black and white issue. I’m explicitly trying to say that it’s not black and white, both because of self-sufficiency arguments, and because of the environmental cost of transportation. Thus, we need a nuanced approach. This means that we should minimise (or eliminate) the use of farmland for livestock production, without condemning livestock production as a whole, because there are legitimate reasons to have livestock, as argued above.
The basis of this thread was that livestock can be raised on land that is not viable for farming. Re-do the calculation when taking into account that the livestock wander freely ten months a year, and that feed is grown on land too harsh for all or most crops, and let me know how it turns out.
Take a look at a map of Norway. If you find a way of growing crops on rocks that are dozens of kilometres from the nearest road, and covered in snow 8/12 months a year, please let me know.
I’m not bringing up the state of access to agricultural land as some historical trivia. It’s just as true today as ever before.
The point is that plenty of countries/regions cannot be self-sufficient regarding food production without resorting to livestock. There are several reasons to be, at least in part, self-sufficient. From environmental considerations arising from the transport of food from other places, to food security in the case that conflict or crisis strikes the region supplying you with food, a region which you don’t control.
Stop acting like this is black and white, and that there’s absolutely no reason a country would want the capability of providing for its own people, as if that’s a thing of the past.
Which is why I said “in general, you’re right”. However, that doesn’t take away the fact that most livestock from some countries is primarily raised on land that can’t be farmed.
Speaking of supply chains: We could do the math on whether shipping a vegetable-based calorie from Brazil to Norway is more or less of an environmental burden than a meat-based calorie produced in Norway.
GET THE ROUNDIE!