3 ms·
What upsets me about go generate is that it is orthogonal to the language, yet it comes baked in. It unnecessarily increases the footprint of the language, whil
by zupa-hu 12y ago
What upsets me about go generate is that it is orthogonal to the language, yet it comes baked in. It unnecessarily increases the footprint of the language, while essentially killing any alternative approaches. Feature creep comes one feature at a time, I guess.
[ps. yet thank you big time for being able to program in golang]
- dsymonds 12y agoWhy does it upset you that it comes baked in? If you don't care for it, don't use it. It's for package authors, so you won't be exposed to it unless you want to.
- zupa-hu 12y agoThis is valid about any feature. It's like adding 10.000 pages to the docs and saying you don't need to read them unless you want to.
- zupa-hu 12y agoHm, I also see the benefits of having a suggested way of doing things, like gofmt. Maybe I'm wrong.
- Retra 12y agoI guess that'a a perfectly fine attitude assuming you never share any code with anyone.
- proveanegative 12y agoI think this is true about preprocessors in general. Couldn't you say that the C preprocessor is orthogonal to the actual C language?
- DAddYE 12y agoUnfortunately it is not a preprocessor, has nothing to do with that. Of course go comes with go/{ast,parser,scanner} which will facilitate that, but go generate is just not that.
- mseepgood 12y ago> What upsets me about go generate is that it is orthogonal to the language, yet it comes baked in. It's not part of the language, it's not in the spec, it's not part of the compiler.