3 ms·
> What's so confusing from this post, is the complete lack of motivations for why anyone would want this over a shell script at the root of their project. I'm
by olalonde 12y ago
> What's so confusing from this post, is the complete lack of motivations for why anyone would want this over a shell script at the root of their project.
I'm not very familiar with go but I think the motivation might be inspired by Python's "one way to do it" maxim. https://wiki.python.org/moin/TOOWTDI https://wiki.python.org/moin/TOOWTDI
This seems to be the philosophy adopted by Go as well (e.g. the gofmt tool, the integrated build system, only one loop construct, slices, etc.).
Personally, I think this philosophy is extremely beneficial in making code more readable and I would say this feature is consistent with it.
- zak_mc_kracken 12y ago> I'm not very familiar with go but I think the motivation The motivation is pretty transparent: since the Go team is categorically refusing to implement generics, they are trying to find workarounds to avoid having developers copy/paste code to simulate genericity. Their solution is to have a tool generate that code instead of developers doing the copy/paste.
- mahmoudimus 12y agoThat was my initial impressions as well. Seems like a convoluted way to get around Generics. Very interesting stance from the Go team.