AQXt

> especially since the images are stylized / colored anyway

The thing that I don't like about the new images is the abuse of star flare effect. The colors are okay, but the flares... that's simply too much.

That's an interesting way to illustrate the myth of meritocracy: random luck is enough to create a society of rich and poor.

Amazing! I'll try it with my kids. :)

Suggestion: create an app so we can see the results immediately.

So, you are re-implementing Altavista, Lycos and other old search engines.

They used the naive approach: you searched for "steak", and they would bring the pages which included the word "steak".

The problem is that people could fool these engines by adding a long sequence like "steak, steak, steak, steak, steak, steak" to their site -- to pretend that they were the most authoritative page about steaks.

Google's big innovation was to count the referrers -- how many pages used the word "steak" to link to that particular page.

The rest is history.

I searched for "giraffe evolution" (without quotes) and received the following links on the first page:

- Evolutionist scientists say the theory is unscientific and worthless

- Seven Mysteries of Evolution

- OTHER EVIDENCE AGAINST EVOLUTION

- Evolution Falsified

Not a single result about the evolution of giraffes...

> I can understand where the author is coming from, but this is the cruel reality of the world.

This article was written in 2015, when this kind of dilemma (who would you save) was purely theoretical.

Fast-forward to 2020/2021, and it became real: we had to decide how to allocate scarce, life-saving resources -- COVID-19 vaccines -- and we decided to distribute them to the elder and most vulnerable first.

I hope this decision -- replicated in most countries around the world -- will put an end to this attempt to calculate the value of human lives.

That's one of the coolest programming demos I've ever seen!

Suggestion: make the completed rows fade asynchronously.

Before Present? (Just guessing)

The first part of the article can be summarized as:

1. Initiate as few attacks as possible

2. Let your enemies break up each other’s continents;

3. Take only one country per turn

The problem is that it doesn't explain which country to take, and how to attack without being attacked -- which is what makes the game difficult.

But, then, the article suggests something new (at least for me):

1. Find a way to grow in strength by taking lots of countries (but not taking a whole continent)

2. Make sure you get lots of cards for bonus armies

If this is a good strategy, I have always played it wrong -- because I've always tried to take whole continents.

Your conjecture may only hold for tiny (< 500 lines of code) problems.

But when you deal with big problems -- millions of lines of code, written by hundreds of developers over a period of years -- you'll definitely see the benefit of OO.

Of course, most projects are somewhere in the middle; but you shouldn't dismiss OO just because you can't see the benefit in tiny projects.

How about `npm`, `pip`, `cpan`?...

We have seen bad updates breaking the entire Javascript ecosystem, but they were not intentional.

All it takes to inject a bad dependency is a burned out developer willing to delegate his free project to someone else...