3 ms·
Python != Crappy code. Lisp != good code. You can write crappy code in any language. My experience is that it is much less expensive to maintain Python in a
by doug_durham 3y ago
Python != Crappy code. Lisp != good code. You can write crappy code in any language. My experience is that it is much less expensive to maintain Python in a team environment in the long run. People aren't tempted to create their own personal "domain specific languages" in Python. Lisp kind of encourages that.
- munchler 3y agoI'm not saying Python is always crappy. It's just easier to create crappy code in Python, due to dynamic typing, rampant side effects, null values, OO madness, etc. If your team has the discipline not to do that, great.
- erik_seaberg 3y ago> dynamic typing, rampant side effects, null values I’m afraid these are also problems in Common Lisp.
- munchler 3y agoYeah, I’m not a Lisp fan myself. I was comparing Python to functional languages, like Haskell or F#.
- vindarel 3y agomuch, much, much less than Python. CL compilers (looking at SBCL) get you many type checks, at compile time, instantly (you compile the function at point), or you can send computation to compile time yourself, and the OO is different, etc.