Try reading documentations to see how the 70k+ vocabulary helped the writer and reader.
Sigils like $ and # are even worse. I had to maintain an old perl codebase once (# @_ holds all arguments passed)
Try reading documentations to see how the 70k+ vocabulary helped the writer and reader.
Sigils like $ and # are even worse. I had to maintain an old perl codebase once (# @_ holds all arguments passed)
https://github.com/mojolicious/mojo/blob/master/lib/Mojo/Dat...
I just find it impossible to glance over it and understand whats happening even though I know what is supposed to be happening there.
Something similar in golang
https://github.com/araddon/dateparse/blob/master/parseany.go
Beside that, the extra clarity in Go is from using a static language. Also, Perl is inexcusable for having no readable function signatures, that's really a no-go for a modern language :|
But for me at least, when I see that wall of boilerplatish Go code, my mind instantly ADHDs away, while those dense squiggles of Perl make me WANT to spend time and focus and solve the puzzle of what they do, I have 10x more chances of paying attention to the Perl code while reading it and maybe even spotting a bug in it :P ...