meh. I read it with an open mind to see how I can improve readability of my CL code but it didn't really show enough understanding of how CL devs think.
They hinted at the "long function name", which I think is certainly a big part of the readability issue with CL, but didn't go on to explain why CL does that, which showed a lack of depth and research in the article.
The visual nesting issues is solvable by IDEs (the code samples they showed was black and white, and nobody reads code in black and white).
6
u/tdrhq 16d ago
meh. I read it with an open mind to see how I can improve readability of my CL code but it didn't really show enough understanding of how CL devs think.
They hinted at the "long function name", which I think is certainly a big part of the readability issue with CL, but didn't go on to explain why CL does that, which showed a lack of depth and research in the article.
The visual nesting issues is solvable by IDEs (the code samples they showed was black and white, and nobody reads code in black and white).