3 ms·

>Saying 'a lot of younger programmers probably don't appreciate the best parts of haskell' is clear age-ism No it isn't. >I think it's annoying. Ok, but that

by copergi 13y ago

>Saying 'a lot of younger programmers probably don't appreciate the best parts of haskell' is clear age-ism No it isn't. >I think it's annoying. Ok, but that doesn't support the claim you made and I questioned.

ulisesrmzroche 13y ago
Are you for real? It's like deja-vu. I guess I should know better by now. There's probably some guy in a lisp thread who has been on my end of this argument for the last 20 years or so. http://en.wikipedia.org/wiki/Ageism#Ageist_prejudice http://en.wikipedia.org/wiki/Ageism#Ageist_prejudice
- copergi 13y ago
  I know what ageism is. You quoted something that is not an example of it. Given that this is entirely pointless, would you mind if we went back to the actual discussion?
  - ulisesrmzroche 13y ago
    The dude that said just said it was 'experience-ism', do I have to explain what nuance is? You've gotta help me out here, I can't do it all on my own. All you keep saying is 'no its not'. And then trying to move on as if that's the final word. Not interested in talking to you bro, we're not going to come to any kind of understanding.
jroesch 13y ago
As a 21 year old this is not ageism in the slightest, it is reality that as you see more and more problems the applicability of some solutions becomes more apparent. For example, when talking to seasoned engineers who have written a lot of concurrent code they immediately understand the value of purity, and immutable data because they have been burned by the problems that crop up when you try to write threaded programs using shared mutable memory. On the other hand if you take a 20 year old student still doing their undergraduate degree (like many of the people in the classes I TA), and try to explain the value of immutable data, many of them just don't get it. It has nothing to do with their intelligence or age, but the fact that they haven't written enough code to develop a sense of why such a thing would be useful. If you want example apps their are plenty littering the internet all covering the various web frameworks, for example here is one covering Happstack: http://happstack.com/docs/crashcourse/index.html http://happstack.com/docs/crashcourse/index.html

by copergi 13y ago

ulisesrmzroche 13y ago

Are you for real? It's like deja-vu. I guess I should know better by now. There's probably some guy in a lisp thread who has been on my end of this argument for the last 20 years or so. http://en.wikipedia.org/wiki/Ageism#Ageist_prejudice http://en.wikipedia.org/wiki/Ageism#Ageist_prejudice

copergi 13y ago
I know what ageism is. You quoted something that is not an example of it. Given that this is entirely pointless, would you mind if we went back to the actual discussion?
- ulisesrmzroche 13y ago
  The dude that said just said it was 'experience-ism', do I have to explain what nuance is? You've gotta help me out here, I can't do it all on my own. All you keep saying is 'no its not'. And then trying to move on as if that's the final word. Not interested in talking to you bro, we're not going to come to any kind of understanding.

jroesch 13y ago

As a 21 year old this is not ageism in the slightest, it is reality that as you see more and more problems the applicability of some solutions becomes more apparent. For example, when talking to seasoned engineers who have written a lot of concurrent code they immediately understand the value of purity, and immutable data because they have been burned by the problems that crop up when you try to write threaded programs using shared mutable memory. On the other hand if you take a 20 year old student still doing their undergraduate degree (like many of the people in the classes I TA), and try to explain the value of immutable data, many of them just don't get it. It has nothing to do with their intelligence or age, but the fact that they haven't written enough code to develop a sense of why such a thing would be useful. If you want example apps their are plenty littering the internet all covering the various web frameworks, for example here is one covering Happstack: http://happstack.com/docs/crashcourse/index.html http://happstack.com/docs/crashcourse/index.html