3 ms·
I mean was there anything wrong about the makefile? Did your product need reproducible builds? This is becoming more and more of a pet peeve of mine, about to
by Cthulhu_ 4y ago
I mean was there anything wrong about the makefile? Did your product need reproducible builds?
This is becoming more and more of a pet peeve of mine, about to become an outright annoyance; the adding or changing of tools without things actually improving, or the purported improvement not actually being relevant or even close to the most important thing that time should be spent on.
https://mcfunley.com/choose-boring-technology https://mcfunley.com/choose-boring-technology is a good starting point for moving away from this mindset.
I had a Go project up until earlier this year, I could set it up myself. I picked makefiles to build it (not bazel, that would be overkill; not mage, that would mean more coding), and it worked just fine. I never had a compelling reason to move away from it.
Actually it was more than fine, it was a relief; my previous experience with tools like that had been Maven (where everything is XML and you need a plugin to do basic things like move or remove a file) and the Javascript ecosystem, from before everything was merged into package.json / nodejs-style. Dependency management too.
- ParetoOptimal 4y agoI typically want reproducible builds to never ever have to deal with build issues and to be able to free up that space to think. Boring technologies are easier for people better and making due with what they have and accepting sometimes very large limitations. ADHD makes boring tasks harder for instance, and boring technologies give you no escape from the tedium. With a little fancier technology though, you at least have hope ;)