←back to thread

Tilt: dev environment as code

(github.com)
136 points saikatsg | 5 comments | 26 Apr 25 19:14 UTC | HN request time: 0.47s | source
1. francescobianco ◴[26 Apr 25 23:18 UTC] No.43808137[source]▶
Why do not use well organized Makefile instead of invent new junk. Is it a product placement?
replies(3): >>43808158 #>>43808419 #>>43810408 #
2. haolez ◴[26 Apr 25 23:21 UTC] No.43808158[source]▶
Makefiles are bad with state that is not represented as files, right? I remember that I had to create "stamp" files with hashes and things like that to overcome this limitation.

There is also .PHONY, but that would make the rule to always be triggered. Maybe I'm misremembering, it's been a long time :)

3. xyzzy_plugh ◴[27 Apr 25 00:26 UTC] No.43808419[source]▶
Makefiles are for building artifacts. They are wholly inadequate at orchestrating environments and task pipelines.

Can you do it? Sure, but somewhere someone is going to be suffering.

4. DonHopkins ◴[27 Apr 25 08:40 UTC] No.43810408[source]▶
Better yet, use a well organized "rm -rf" command!
replies(1): >>43810981 #
5. DonHopkins ◴[27 Apr 25 10:56 UTC] No.43810981[source]▶
Refactoring advice: "The cheapest, fastest, and most reliable components are those that aren't there." — Gordon Bell