597 karma · joined July 6, 2016
I'm really tired of the idea that a hero has to be a perfect saint by modern, vogue definitions. We have a news media that is so rabidly searching for reasons to destroy people, that Musk headbutting a car in frustration is somehow news. So what? Who hasn't banged their head in frustration? Then we have more serious cases, like attacks on Gandhi, where compromising situations with 18-19 year olds (which I'm not defending) get transmuted into accusations of pedophilia.
Can we just stop!? Let good actions be remembered, and let truely bad ones be punished in a timely fashion. By speaking ill of the dead, we rob ourselves of heroes and examples that are genuinely worth following, just because the whole person isn't who we want to be.
Edit: transmitted -> transmuted
Which is a perfectly rational thing to do, if the risk is close enough to 1. Even in actual housing, they preemptively condemn and evacuate buildings that have become too unsafe to trust, before a disaster occurrs.
That doesn't look to be the case. While the "net native" generation is more likely to turn to digital content than other media, studies show that computer literacy, in the sense of understanding the basic workings of a computer, is on the decline.
The problem here is simply dilution. Every niche social site that grows large will eventually face the Eternal September, when the userbase grows too large for moderation, and the content drifts dramatically. At that point you simply have to move on and find somewhere that still has a focus on the topic you originally were looking for.
I would much rather have a short list of simple, powerful functions, that operate over sequences. Array Oriented, if you will, or perhaps even Map Oriented. If you need to construct a full name from an object, whether it's a user or a client, or a character, or a cat or whatever, that can be passed quickly over my lists to return the relevant strings.
This function-and-array style of programming forces you to standardize your data formats and types across your program, and is easily tested. While the OO approach allows you to indulge a thousand different quirks of naming and style and logic, that will take far longer to test, and will likely still have quirks and inconsistencies.
Oh, please no. I've had to play fixer to too many codebases that used interesting tricks to implicitly import code, without pointing to a source. Trying to suss out the origin of a specific function named 'get' in a 100k line application, in a file that invokes, but never declares it, is an exercise in frustration. Less context, please, more explicitness.
Unsurprisingly, legal documents have a reputation for being at least as difficult to read as some code.
Natural language, designed for human communication, is, by its nature, unsuitable for precise definition, and a precise language is also unsuitable for human communication.
It really makes sense once you realize how much conversation and prose depend on puns, allegory, allusion, symbols, context, emotion, and so on. All of which are hostile to stating a thing as exactly as possible.
I can't really empathize with someone who sees no value in suffering. Suffering is not the ultimate evil, and pleasure is not the ultimate good. Go read some Cicero. He tears Epicurus a new one in much better language than I can muster.