I never said, "purely functional" only that the language is functional friendly, which Python very objectively is not (absence of anonymous functions being the first indicator).
So what do you call closures, lambdas, a builtin map function, list comprehensions, callables, higher order functions and lazy evaluation if not functional constructs?
I'm sure you will reply saying "hey, you can't write multi line anonymous functions so everything else you just said it's moot" :-)
(And yes that is an opinion, which is shared by Stanford and Carnegie Mellon.)
Please, link me something where they say that OOP is bad for your brain (and no, not something where someone says FP might be a better intro to programming). Words have meaning. You know you can do OOP in C right? So C is bad for your brain because it supports OOP?
Defaulting to for loops, for example, instead of thinking of how such interaction would happen concurrently through, say, a map/reduce/filter approach is definitely going to cause you to write non-concurrent code
Not all code has to be concurrent. Not all programs are massively parallel. I'm sure there's no point in me telling you that you can do parallel, map reduce in Python also. I have had a feeling since your first post that you decided that you're right despite any argument that might chip at the argument :-)
I read your post by the way and I agree with part of it and disagree with other parts but after your very elegant closing up here I don't think I have the will to keep on arguing.
Let's agree to disagree and call it a day.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
So what do you call closures, lambdas, a builtin map function, list comprehensions, callables, higher order functions and lazy evaluation if not functional constructs?
I'm sure you will reply saying "hey, you can't write multi line anonymous functions so everything else you just said it's moot" :-)
Please, link me something where they say that OOP is bad for your brain (and no, not something where someone says FP might be a better intro to programming). Words have meaning. You know you can do OOP in C right? So C is bad for your brain because it supports OOP?
Not all code has to be concurrent. Not all programs are massively parallel. I'm sure there's no point in me telling you that you can do parallel, map reduce in Python also. I have had a feeling since your first post that you decided that you're right despite any argument that might chip at the argument :-)
I read your post by the way and I agree with part of it and disagree with other parts but after your very elegant closing up here I don't think I have the will to keep on arguing.
Let's agree to disagree and call it a day.