The Golden Record acts as a good thought exercise about how we'd go about communicating with an alien species. It's also a good public outreach and educational tool. It inspires awe and encourages taking time to reflect on what we are most proud of as a species.
I think you mean to say that you couldn't afford to devote the time to making a map that Microsoft did. Generally, in C++ we get to use data structures that have had far more attention to every detail than we could apply personally because they are used by many more than just us. Microsoft's gets used by everybody who uses their compiler, and so commands attention. It probably deserves more than Microsoft actually spends, but that is a management problem.
So definitely don't use it if you care about performance? (You can't write it, but anywhere you'd use it you can probably beat it). But we're getting into discussion of sensible benchmarking of actual deployable applications so let's leave that for another time.
Or just make PHEVs. Cars that have small batteries, that are big enough to do 95% of your driving on electricity. That still let you jump in and go somewhere without hoping that there is a place to charge up. And even when running the ICE engine, you're getting fuel economy much higher than a regular ICE car.
I think that if everybody could reduce their ICE usage by 90%, and only use 1/4 of the batteries, that is a win-win for everybody. People driving around in 200-350 mile EVs, that only drive less than a 1/4 of that on a regular basis are just wasting batteries that could have gone into other cars and saved them on the cost of their current car.
Like seriously, how often do you drive more than 100 miles? Once a week, once a month? We all know the stats for people's commutes are far shorter. Most people don't need long range EVs except for once in a while. That's what pro-EV people have been saying for years.
Even a Jeep Wrangler 4xe that only has like 10 miles of range... if your commute is 20 miles round trip, that's still half the gas usage. That guy probably wasn't going to buy an EV anyways. PHEVs are also a way to get skeptics to reduce reliance on gas.
I believe ludjer is referring to S3 Storage Inventory. This is a daily, or weekly, file produced containing metadata on every file within a S3 Bucket. It does not use the synchronous List APIs.
> You can use Amazon S3 Inventory to help manage your storage. For example, you can use it to audit and report on the replication and encryption status of your objects for business, compliance, and regulatory needs. You can also simplify and speed up business workflows and big data jobs by using Amazon S3 Inventory, which provides a scheduled alternative to the Amazon S3 synchronous List API operations. Amazon S3 Inventory does not use the List API operations to audit your objects and does not affect the request rate of your bucket.
>
> Amazon S3 Inventory provides comma-separated values (CSV), Apache optimized row columnar (ORC) or Apache Parquet output files that list your objects and their corresponding metadata on a daily or weekly basis for an S3 bucket or objects with a shared prefix (that is, objects that have names that begin with a common string). If you set up a weekly inventory, a report is generated every Sunday (UTC time zone) after the initial report. For information about Amazon S3 Inventory pricing, see Amazon S3 pricing.
Configuring emacs isn't a test of intelligence, it's a test of investment. I wish the mindset that conflates intelligence and investment would go away.
Software is going to continue to play a bigger influence on everyones life. The majority of this software is going to be written by engineers of average intelligence. Having tools that are easier for everyone to use will make your life better down the line too.
Think databases which run across many different machines.
Distributed databases are often conceptually modeled as a state machine. Writes are then mutations on the state machine.
With a starting state (empty database), if everyone agrees that on a fixed list of mutations which are executed in a rigidity defined ordering, you will get the same final state.
Which makes sense, right? If you run the following commands on an empty database, you would expect the same final state:
1. CREATE TABLE FOO (Columns = A, B)
1. INSERT INTO FOO (1, 2)
1. INSERT INTO FOO (3, 4)
Which would be:
```
FOO:
|A|B|
|-|-|
|1|2|
|3|4|
```
So where does "consensus" come into play? Consensus is needed to determine `mutation 4`. If the user can send a request to HOST 1 saying 'Mutation 4. should be `INSERT INTO FOO (5, 6)`' then HOST 1 will need to coordinate together with all of the other hosts and hopefully all of the hosts can agree that this is the 4th mutation and then enact that change on their local replica.
This ordering of mutations is called the transaction log.
So, why is this such a hard problem? Most of the reasons are in [Fallacies of distributed computing](https://en.wikipedia.org/wiki/Fallacies_of_distributed_compu...) but the tl;dr is that everything in distributed computing is hard because hardware is unreliable and anything that can go wrong will go wrong. Also, because multiple things can be happening at the same time in multiple places so it's hard to figure out who came first, etc.
RAFT is such an algorithm to let all of these hosts coordinate together in a fault tolerant way to figure out the 4th mutation.
Disclaimer: The above is just one use of RAFT. Another way RAFT is used in distributed databases is as a mechanism for the hosts to coordinate a hierarchy of communicate among themselves and when a host in the hierarchy is having problems RAFT can be used again to figure out another hierarchy. (Think consensus is reached on leader election to improve throughput)
