2 ms·
I sort of agree. I had a project in which I wanted to use Go, but I ended up writing Emacs macros to repeat boiler plate code. That wasn't pleasant, and to me i
by tgv 7y ago
I sort of agree. I had a project in which I wanted to use Go, but I ended up writing Emacs macros to repeat boiler plate code. That wasn't pleasant, and to me it meant that Go wasn't the most suitable language for that problem.
That applies here too: if you find yourself writing too much boilerplate code in favor of an abstraction, try another language. If you want/have to continue in Go, look for another solution.
- erik_seaberg 7y agoGo demands a ton of boilerplate but writing it all by hand isn't a good use of time. Lots of people are working on //go:generate tools, much as cfront used to emit awful C boilerplate we would ignore while writing C++.