If you show a skyscraper to an ant, should he abandon his queen because their little hill is too insignificant to matter? Or should he jump back in and build the best damn nest in the city? I just don't think relative scale is really important - even a galaxy-striding star-snacking titan would grapple with the same problem of meaning.
> Nihilists recognize that meaning is not inherent, but rather ascribed by the person experiencing the feeling.
That sounds reasonable, so here's an attempt at a synthesis. The universe is huge and mostly empty, but here we have a tiny patch full of life and self-ascribed meaning. Does the universe prefer life? The part that's alive certainly does! So don't let it fall to ashes just to appease the void. I think that's the best answer a mere mortal can give.
As a tiny representative of the universe, yes I do enjoy having feelings, hopes, and dreams. If nihilists find this to be meaningless, perhaps we simply disagree about which of us is the cancer.
Humans have feelings, hopes, and dreams. Humans are a subset of the universe. Therefore, the universe has feelings, hopes, and dreams.
Now that the universe has manifested we conscious agents of its matter, how dare we squander this gift? Just because it didn't come with an instruction manual? We will find our own purpose.
> The license must not discriminate against any person or group of persons.
> 6. No Discrimination Against Fields of Endeavor
> The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
> var myValue = DoSomethingAsync().ConfigureAwait(false).Result;
Came out a decade ago and we still don't know how to use it safely.
This example doesn't compile because there is no Result on ConfiguredTaskAwaitable. Regardless, ConfigureAwait(false) does absolutely nothing here because this Task is not being awaited.
If you're going to block this thread, you must push the work to another thread or it's going to deadlock when the implementation tries to resume a continuation (unless the implementation is 100% perfect and the SynchronizationContext smiles upon you).
var result = Task.Run(() => CalculateAsync()).GetAwaiter().GetResult();
- redundancy
- striping
- compression
- encryption
- mountpoints
- volumes
- quotas
- snapshots
- send/recv backups
- disk error detection (ECC protects memory only)
All built in with consistent well-documented tooling. No futzing around with lvm mdadm fsck luks fuse fstab etc.