News for hackers. Stuff that matters.
Re:Code boilerplate: Is it always bad? by banku_brougham on Saturday June 10, 2017 @06:47AM (#14526891)
Your comments clearly ring true, for the example code snippets shown. But i think you have missed the point of the article, which is the benefit of the Go version when iteratively changing the structure.

The author could have brought the examples forward, instead of just providing links to urllib3 and the Set type.

Re:Code boilerplate: Is it always bad? by coldtea on Saturday June 10, 2017 @11:37AM (#14527712)
>Your comments clearly ring true, for the example code snippets shown. But i think you have missed the point of the article, which is the benefit of the Go version when iteratively changing the structure.

You can iteratively change a smaller, terser code, must faster. There's a reason prototypes are often written in languages like Python.