|
The "maybe" defense?
|
Posted: Jan 3, 2007 10:12 AM
|
|
> Really? I don't know what to tell you. Look up the > definition of 'maybe'?
Be honest, James. If somebody had made the same statements as you but used "java" in place of "C++", you'd be on it like white on rice and you wouldn't let them weasel out of it by invoking the "maybe" defense.
> And you overreacting over this makes me suspect you are > trying to get in some digs at me. Why do you care? Are > you married to C++? Did you have some hand in the > creation of C++? This is like getting angry at me for > thinking a santoku is better than a chef's knife for > chopping celery. I'm not really sure how this kind of > emotional attachment to a language helps anyone.
I hardly know where to begin. Why do you consider "calling" you on your unsubstantiated statements overreacting? I don' have any emotional attachment to C++, I'm not even using it (by choice) on my current project.
You > haven't actually explained why threading in C++ is just as > easy as it is in Java. I'm completely open to that being > the case.
This is a common ploy, but I'm I'm wise to it. I have no hypothesis to prove, I'm just challenging yours.
> > Look, instead of saying 'threading is easy and if you > think it is hard, you are incompetent' I thought I'd try > to be diplomatic and leave the door open for some other > factor that might explain why this is perceived as being > difficult. C++ was named because it's popular and > supports threading but not at a language level. I can't > name another language where threading is commonly used and > not part of the language.
The fact that you were even thinking that only an incompetent would consider threading difficult speaks volumes about your way of thinking. To paraphrase Shakespeare "There are more things in the world of programming, James, than are dreamt of in your philosophy."
We all have experience only in a small subset of the programming world. Don't make too many assumptions about those parts you know nothing about.
|
|