I agree with you that, in most cases, bringing a language into a project established in another language is a bad idea. I do not, however, think that makes every high-level language exactly the same. Furthermore, I do not think that makes the currently selected language *always* "The Right Tool For The Job." Sure, sometimes it is a much better decision to use the "wrong" tool for the job... but that doesn't magically make it a better tool.
I guess the main difference boils down to how we're interpreting "The Right Tool For The Job." You are taking the more pragmatic approach, which I think is the right thing to do most of the time. I still think there's value in paying attention to the more abstract component, though. And that's what I think this whole Right Tool business is talking about.
In any case, I think we've flogged this freshly dead horse long enough. I guess I'll agree to accept your wrongful interpretation of this too-often used term. :)
In reply to Re: Re: Re: Why the Right Tool for the Job is always ...
by revdiablo
in thread Why the Right Tool for the Job is always ...
by autarch
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |