If you make changes to a large shared module, is it your responsibility to chase down each and every usage of it? For example if you are upgrading a dependency due to a somewhat breaking security issue such as Jackson 2.8->2.12
Seems like religiosity is a neurological need, but church is not. With organized religion decreasing in various countries, I wonder where people will get their outlets for social and metaphysical needs previously supplied by churches.
His point that conspiracy theories are acting as a substitute for religious community and purpose is interesting. I guess there are a number of different belief systems that can fill a void of purpose.
The charts are comparing “accelerated” performance versus what appears to be a cpu only baseline. It is not clear which M1 hardware beyond the CPU is used
Depends on the part of Amazon but it is pretty prevalent in Retail. The fact that it is both binary and self describing makes it pretty good for data at rest. You can still parse and understand that archival transaction data from 8 years ago.
The support for S-Expressions is both a blessing and a curse. The ability to write logic with native data structures in it is fundamentally interesting, but it leads to lots of reinvention of somewhat crappy Lisp implementations.
The tooling ecosystem has been slowly improving outside of JVM, particularly the latest JS implementation.
In a vacuum, the support for type annotations, timestamps, decimals and binary serialization make it superior to JSON for use cases where self describing data is appropriate.
Having a single wiki instance for your company is an awesome way to collect knowledge. You can write up operation run books, design documents, references all in an informal way.