3 ms·
The discussion is about Go-internal features, and whether or not dogfooding should be required. There's no contract being broken.
by ajross 7y ago
The discussion is about Go-internal features, and whether or not dogfooding should be required. There's no contract being broken.
- int_19h 7y agoThe whole point of OP is that many Go-internal features shouldn't be internal.
- ajross 7y agoAnd my whole response is that that notion of "shouldn't" reflects an aesthetic or moral argument and not a technical one. How Go is implemented says nothing about whether Go is a good language or not.
- Dylan16807 7y agoIf I understand you right, your entire argument depends on counting "Go exposes X internal feature" and "Go exposes something equivalent to X internal feature" as different things. Because demanding Go do either one is an engineering argument. But demanding the former over the latter is an 'aesthetic or moral' argument. Well, nobody else is making that distinction! They're only making the engineering argument! You're interpreting their words way too literally if you think they're making the aesthetic argument.