3 ms·
This is the first time I've seen anyone complain about positional arguments. While I can see the point of such a complaint (and its arguably even worse in Hask
by maxander 11y ago
This is the first time I've seen anyone complain about positional arguments. While I can see the point of such a complaint (and its arguably even worse in Haskell, where there's application-order confusion at the same time), my impression is that the larger body of programmers are still miffed whenever they have to explicitly name a type- explicitly handing every argument of every function to a specific named field sounds deeply onerous by comparison!
I suspect the next Holy Wars in programmer practice will revolve around "how much can we get away with not writing out?"
- protomyth 11y agoI've made that complaint quite a lot and heard it quite a lot. I hung out with a lot of Smalltalkers and I have programmed Objective-C since NeXTSTEP 3.3. I like selector syntax and find it a pain in the butt when I'm in Perl or C looking for the order of arguments. I guess its all in who you associated with early. That's probably why I don't like Swift (which does it clunky) as much as Objective-C.
- icebraining 11y agoIt's not either/or - you can make it optional, like in Python.