Actually, I like encapsulating global state in a structured and documented construct. But I guess I could see Java developers going overboard with abstraction in an imperative language.
I've recently come to appreciate the "refactor the code while you write it" and "keep possible future changes in mind" ideas more and more. I think it really increases the probability that the system can live on instead of becoming obsolete.
Actually one of the few languages you can learn in its completeness in less than a day, so I wouldn't really say it's "hard to understand". More like hard to read and understands programs written in it.
Sure, it's advantageous in the short-term. I think this is where we misunderstand each other. What I'm trying to say is that under normal circumstances, individuals aren't maximizing their output. They are just living as part of the community, following the unwritten rules and benefiting from that. (In the prisoner's dilemma, this would be choice A).
If this is how everyone would act in their daily life, you would see crime, theft and abuse on an unimaginable level. No, people don't always do what benefits them "at every individual point". We are social creatures, acting as a community where the individuals benefit from working together. Although this has been successfully undermined by capitalism and other hierarchies.
This whole concept is also called, the Prisoner's Dilemma, one of my favorite thought experiments because it shows how being rational can result in everyone being worse off.
Without any limits, individual cattle owners have an incentive to overgraze the land, destroying its value to everybody.
This is factually false, because the land will be destroyed and individuals don't benefit, not even in the short term. Commons work great (see open source software), but capitalism and power structures abuse and destroy them for short-term profit.
Interesting viewpoint, but I think the applications aren't at fault: The operating system should ensure that the user has control of the computer at all times. I think you need to do three things to achieve that:
Limit process RAM usage, so the system never has to swap
Limit process CPU usage, so the system never stalls
When drivers / the operating itself crash, revert into a usable state (this one is probably the most complex one)
What do you think the authors of the video don't understand? You must have some insights if you say you understand AI better then everyone criticizing it.
I'm bored (but not in a bad way). I wish I could hang out with people, but I have nobody around right now. I feel happier than ever, just can't share it with anyone. I guess I'm just going to call someone and satisfy this extroverted phase that way.
Even if these are an alternate evolution path I think it's pretty exciting. The results presented by the teams investigating this sound pretty convincing, so I don't think it's just "misidentified human children".
A little bit of Go when I'm not too frustrated from loosing the last game (don't know why this happens only with Go, but I can't help it) and Netrunner.
Interesting, that definitely makes sense!