> We live in a world where for every language there are build tools that know far, far more about the needs of that language environment than make, and thus are

> We live in a world where for every language there are build tools that know far, far more about the needs of that language environment than make, and thus are far better suited. Languages don't exist in a vacuum. A big reason for the resurgence of make by developers is every language/environment comes with something new that tries to recreate make. They all have issues and limitations where make ends up being a better tool. Also, when you need to deal with multiple languages in a project, these tools tend not to be that helpful. As a web developer, there's been so many attempts to make tools like gulp [1], grunt [2], npm scripts [3], web pack [4], etc. and a dozen more, to do a part of what make has been doing for decades. And literally every 6–12 months, there's a new, hot tool that everyone gets excited about. It's just reinventing the wheel over and over. Now that I've settled on make for web projects, it's no longer a concern. I much rather describe my dependencies using make than JavaScript (ugh), which many of these tools use. Some tools fall out of favor; developers stop creating plugins or whatever for them. As a user of the tool, you can find yourself shit out of luck for your particular project or use case. The beauty of make is it can handle the tasks of building a web site or web app using modern tools that didn't exist when it was created. As someone mentioned further up, make is eternal; it's not going anywhere. [1]: https://gulpjs.com https://gulpjs.com [2]: https://gruntjs.com/ https://gruntjs.com/ [3]: https://docs.npmjs.com/cli/v9/using-npm/scripts https://docs.npmjs.com/cli/v9/using-npm/scripts [4]: https://webpack.js.org https://webpack.js.org