News for hackers. Stuff that matters.

A comment on Dueling Rhetoric of Clojure and Haskell. Parent comment

Re:Dueling Rhetoric of Clojure and Haskell by Xephyrous on Wednesday November 01, 2017 @04:52PM (#15605373)
Classes definitely give you a lot of rope to hang yourself with (metaclasses, inheritance, MULTIPLE inheritance), but they have their place. I'll usually start with a function, but when it gets too big, you need to split it up. Sometimes helper functions is enough, but sometimes you have a lot of state that you need to keep track of. If the options are passing around a kwargs dictionary, and storing all that state on the class, I know which I'd pick.

You can memoize methods to the instance to get lazy evaluation, properties can be explicitly defined up-front, and the fact that everything is namespaced is nice. You can also make judicious use of @staticmethod to write functional code whenever possible.

[ Parent | on HN ]
Re:Dueling Rhetoric of Clojure and Haskell by jstimpfle on Wednesday November 01, 2017 @05:01PM (#15605437)
You can always opt for explicit dict passing. You are right that it's more typing work (and one can get it wrong...), but the resulting complexity is constant in the sense that it is obvious upfront, never growing, not dependent on other factors like number of dependencies etc.

When opting for explicit, complexity is not hidden and functions are not needlessly coupled to actual data. Personally I'm much more productive this way. Also because it makes me think through properly so I usually end up not needing a dict at all.

Regarding namespacing, python modules act as namespaces already. Also manual namespacing (namespacename+underscore) is not that bad, and technically avoids an indirection. I'm really a C programmer, and there I have to prefix manually and that's not a problem.

[ Parent | on HN ]
Re:Dueling Rhetoric of Clojure and Haskell by kreetx on Wednesday November 01, 2017 @05:22PM (#15605596)
Yup, this open field to do whatever with meta classes, inheritance, properties, etc. was what hanged my interest. Since all this "multiple meta monkey patching" was possible, there was no way of telling (for me) what's a good way to implement something in an elegant way. Simple was not good enough, but complex had no rules.
[ Parent | on HN ]