[peatfreak]

The article has the following near the end:

"To see more real-world examples of makefiles, see my [World Atlas](https://github.com/mbostock/world-atlas) and [U.S. Atlas](https://github.com/topojson/us-atlas) projects, which contain makefiles for generating TopoJSON from Natural Earth, the National Atlas, the Census Bureau, and other sources."

I checked those repositories because the descriptions of the makefiles sound interesting, but I couldn't find the makefiles. Am I looking wrong?

[Mister_Snuggles]

It looks like the author gave up on using Make with this commit: https://github.com/topojson/world-atlas/commit/8f92f6eb692d1...

[throwaquestion5]

More like they moved from the need of using Make to create the topoJSON to use prebuild ones with Node.

In the package.json of that commit:

> - "description": "Roll your own TopoJSON from Natural Earth.",

> + "description": "Pre-built TopoJSON from Natural Earth.",

[peatfreak]

It kind of makes the whole article irrelevant. Like a house of cards that is build on a foundation of Make, but when you get to the bottom there are no actual Makefiles there.

[throwaquestion5]

It just means when the article was published, the need was real and make was useful. Context matters.

Based on that commit they don't need to download the data to generate the .json file, so they don't, Make became irrelevant. If anything this shows that a tool can be really useful but you don't need to marry it. Don't use if you don't have to.

[peatfreak]

The whole point of the article is to discuss Make.

[johannes1234321]

Which isn't invalidated by a project having no need for it anymore.

[peatfreak]

This makes no sense!