|
|
|
|
|
|
by Dylan16807
186 days ago
|
|
|
> And I’ve already answered that question. You somewhat answered it in a way that doesn't really get to why they asked it (you can't make every decision based on "demonstrated impact"). But you did that in a different comment than the one I replied to. The one I replied to was just answering the wrong question entirely. Which is why I replied. > Rewriting from Go to another language wouldn’t solve the problem better. Because Go is an implementation choice, not a design choice. There’s nothing in Go that make Terraform better. It could be in C and a lot of people wouldn’t notice. I'm sorry, are you arguing that using feel to decide how to structure a piece of code is a "huge red flag", but the choice of entire programming language is unimportant? |
|
|
From my first reply, I've been arguing that using feels to decide things is very much dangerous. There are usually a less ambiguous way to frame the reasons behind a decision. Methodologies like the five why's can help.
And choosing a programming language is orthogonal to designing a solution to a problem. Everything get turned to opcodes and binary at some point.