Re:The State of Go
by strken on Sunday February 05, 2017 @06:09PM
(#13575286)
I find Forth, Ruby, Elixir, various Lisps, etc. almost impossible to reason about because of this. Powerful metaprogramming tools can lead to really hard to understand and hard to refactor code.
[ Parent
| on HN ]
Re:The State of Go
by enraged_camel on Sunday February 05, 2017 @11:15PM
(#13576432)
>>Powerful metaprogramming tools can lead to really hard to understand and hard to refactor code.
They can, but that doesn't necessarily mean they do.
For example, the usage of Elixir macros, which are the primary metaprogramming tool in Elixir, is discouraged in the docs:
http://elixir-lang.org/getting-started/meta/macros.html#fore...
Re:The State of Go
by artursapek on Sunday February 05, 2017 @08:41PM
(#13575928)
Refactoring is the worst part, so bad that people just don't do it. This naturally leads to very convoluted code bases. Ugh. Never again.
And actually, this is another place Go shines. Refactoring Go code is easy because the compiler helps you along. There's even standard tooling that automates some of it. Amazing.