3 ms·
I gave up on perl when I saw the following code: $x = $src[$src]; I was confused as hell until I realized that arrays and scalars had different namespaces. T
by steven2012 12y ago
I gave up on perl when I saw the following code:
$x = $src[$src];
I was confused as hell until I realized that arrays and scalars had different namespaces. That, along with the fact that "or" and || had different precedences were what ended Perl for me. I'm not saying that wonderful code can't be written by Perl, it just wasn't the right language for me in that I hate memorizing one-off rules, which Perl seemed to have plenty of, instead of a language that was more internally consistent.
- oneeyedpigeon 12y agoIIRC, 'or' and || have different precedences in other languages, too - PHP, for example.
- mst 12y agoIf you only want a single namespace for everything, I recommend sticking to only scheme (note: I really love scheme for that property, I'm not being sarcastic). Once you learn -enough- perl, there's a sort of overall consistency that's actually really nice, but there's a gap ... simple perl is very simple, but mid-level perl is generally a mess until you get to the expert level, and then its awesome again. There's probably an analogy to text editors here.
- anko 12y agoI couldn't agree more, and that's why I hate perl. That gap in the middle makes it really hard to hire perl developers unless they are experts. It's hard to find experts because they think perl code is a mess before they get there. It's probably the main failing of perl.