Sometimes they do it in their own species, but much more commonly they do it across species. Eucalyptus will kill all but eucalyptus. Redwood trees will form networks and help each other; even an albino redwood tree (no chlorophyll https://education.nationalgeographic.org/resource/white-wond...) can survive.
A plant that killed all offshoots of itself would not survive. But plants much more often make perfect genetic copies than animals do, so the selfish gene can explain this behavior
Murder is a synonym for kill but you can differentiate between them to make a point that one particular instance of such a caused-death is worse. Is more reprehensible.
The semantics of the word are as fluid as the opinions of those who you are trying to explain the situation to, using such distinctions.
If you think the death was wrong, it is a murder. If you think the death was right, it was a murder, killing, assassination, or any such word. Language is obviously not as black and white as the example I gave, but the point stands.
I agree with your definition but think it’s too narrow, and thus missing the point of the original argument. I don’t agree with lo_zamoysk‘s original point. I think lions CAN murder. I think when they commit cannibalism it’s only when they murder other lions. All other deaths lions cause, lion or other animal, are killings (maybe murder maybe not). But when Lion A kills and eats Lion B, Lion A would have much preferred to get food another way. It’s a lot more likely Lion A is motivated by something other than hunger, like so many of Lion A’s - or even any Lion’s - kills are.
Motivations are required for murder. The word “murder” ascribes motivation to a killing.
Wow. I just read that whole wikipedia article and had a fantastic time. Thank you very much for sharing
But to comment on your point: species DO pay for it in the long term when members murder or teratorialism.
Lions are not cannibals. Some lions are cannibals. A successful group of lions cannibals existing (and what a brutal and awesome-in-the-biblical-sense story it is!) does not mean that it pays for the lion species as a whole to have groups of cannibals existing.
In fact, I could only see the “proliferation of groups like this committing atrocities” reach a tipping point for a species - not murdering when this murdering happens will make you cease to exist. So if the species doesn’t have a reason to reach the extreme where this NEVER happens, then it will quickly reach the point where this ALWAYS happens
If you could snap your fingers and have your type hints update to match your code, it wouldn’t get in the way of your work.
Hyperbolically: You have to be able to edit code at the speed of thought - whatever it takes - or else programming languages cease to be a more useful tool than just thinking.
If you type slower than you think, or can’t do the type-hint-based textual translation as quickly as you think, then… yeah - it’s not good for you.
The advice I’d wanna hear for myself is: just get better. But the advice I’d give to my coworkers is: have explicit domains where you’re able to do whatever is most efficient and effective, and then when you hand off data to the next subsystem - obey a contract. A schema. Be that type hints or a .proto file or a database schema or an API. Doesn’t matter.
> On the other hand, when speaking with anti-interrupt people, I often get so bored it's hard to pay attention
The post didn't ever explicitly say this, but part of the power of wait culture is that fact that it forces you to listen. Even when you think someone is wrong.
Of course, if what the other person is saying is not worth your time, then there's no reason to be a good listener.
As for an objective look at the mechanics of interrupt culture that you described, it works perfectly if everyone can agree on the relative importances. But if someone never lets you interrupt or ALWAYS interrupts, then... it just breaks down. It's almost like you're taking an economist's stance of "all humans are rational actors". If that's the case, then your arguments for interrupt culture are an nice proof detailing how - in any situation, the person that needs to talk more has the ability and permission to immediately gain the floor without listening to the other person waste time explaining an irrelevant detail or counterargument to a misunderstood point.
I like the way you're thinking, and I know that you would act in good faith under this system you see and have explained so well. Together, I would converse with you like that. And just hope that one of us doesn't get frustrated that the other person keeps interrupting with boring stuff.
Yeah if you're trying to fit the WHOLE web page into 14kb.
But you can get ALL the text there and have the images load in after. The first time I used a the static site generator Gatsby I was super weirded out by the blurry image that showed up upon first load of an Img. It will quickly resolve into a full quality image, ofc, but the point is a relevant metric is also time to first contentful paint.
Also the JS will load the rest of your pages while you're idling on the first page, so that's nice. It's not just good enough to have lazy-loading content, your strategy will have to change depending on how users use your site. Let's say 99% of people scroll to the right in a circular gallery of pictures. You should only really load pictures to the right.
Awesome app. Do you plan on using it for anything in particular? Or are you just creating it as a passion project. It's totally cool.
***
Learning about https://treenotation.org/ (linking this for other people, not for you, Breck :P), and I like what I see. My first impression was: "tree notation is like lisp, but with python indenting".
But then looking at it more and I see it's much more like YAML or CSV or whatever. But then I read:
> We no longer need to store our data in error prone CSV, XML, or JSON. Tree Notation gives us a simpler, more powerful encoding for data with lots of new advanced features
And I didn't understand! Tree notation seems equivalent to these. Like at a certain level, it's all just data. Now, the major benefit is that you're supposed to think differently about what you're doing when using tree notation. Would love to hear your opinion about this conjecture.
***
Not getting into the beautiful and amazing work that's been done WITH tree notation (yet), that's a whole other conversation!