ouch!, I have to agree that you misquoted Juan, he has always said he can’t embrace the Java OOP implementation

tamgo Says: When you sell solutions, it’s not relevant the language or technology you use. The important thing is that the users are happy, the application(s) hits the mark…

stop using that word dammit http://en.wikipedia.org/wiki/Solution

Now for the real topic, I have to say that after a certain number of languages you stop winning out of it, you should learn at least 2 languages for each paradigm (please note this is not paradigms x 2 languages)

On the other hand if you master say Java, this will help you a lot in other languages like C#, C++ and even C. SO it’s not a bad thing.

So I’m with you monk use the right tool for the right Job.

My point was about users being happy, and the consecuence of a bad implentation.

Napoleon and Hitler is another topic I don’t feel the need to discuss.

Are you really going to use mediocrity as a point of reference for making comparisons. If so, then there is no need to continue with this discussion. It will become a pointless, never ending, out of context mini flame war. Do you really want to do that?

It’s not about a job, it’s about making users happy (paraphrasing tamgo). Well there are a lot of people happy with Windows. so….

When you sell solutions, it’s not relevant the language or technology you use. The important thing is that the users are happy, the application(s) hits the mark, and does it without consuming too much resources. Of course, there are several exceptions to this, especially when money for licenses and company politics come into play. Another reason why I want to get out of the corporate life style.

Another thing, I am not the kind of guy that will migrate to the language that is currently fashionable, and neither are you. So I really don’t see how that last remark is even relevant in the discussion.

Last but not least. I know you are the man, never doubted it for one second :p.

Success is not the issue,–but ok let’s run with it for a moment–I do agree that you can be successful with only one language, that’s not worth arguing, but will you be sustainable over time?

To be quite clear I don’t have a problem embracing the OOP paradigm, I’ve used several OOP languages, some that are older than you :).

What I can’t do is translate my elegant solution to the Java language in a way that I feel, it’s good or efficient.

My point has always been, knowing one language is better than none, but don’t start bitching and moaning when you find that you can’t get a decent job because you only know x, and everyone is using y now. Also you always keep bringing up how I’m the second coming of Yoda (Sarcastic comment), but to be quite honest I know and I can handle most of the things that has been thrown at me, because I have taken the time to learn new paradigms, that force me to look at the problems from different points of view, so I’m sorry but I don’t buy into the one language is enough manure.
That’s my point.

Ummmm… no. Dumb and lazy idiots lead to crippled thinking. These same dumb and lazy idiots had a hard enough time learning one language that after they got it down, they don’t want to go out and learn another one. The “if it’s not broken, don’t fix it mentality” taken way out of context. This is common ground, not something that determines this demographic. Please don’t consider it so.

Even though you may be a good problem solver, if you cannot lay out your solution in a particular programming paradigm, then you are still in trouble. I have heard, directly from your mouth, that your main problem with Java is that you are still not capable of embracing the OOP paradigm. Simply because you have not dedicated time to it, you are more than capable of working with it, but that’s a discussion for another moment. This is a perfect example of a good problem solver (you, and you cannot say otherwise), not being able to use a paradigm to materialize a solution. I myself have a difficult time working in procedural weak type languages. This is not a result of my problem solving abilities, but of my procedural weak type language abilities.

Problem solving is one thing. And it is imperative from being a decent coding. Working in multiple languages/paradigms is another, and IT IS NOT IMPERATIVE in order to be successful.

As with any kind of industry which mixes creative thinking with logical thinking, you will need the perfect tools for the job. The more tools you have, the easier it will be to adapt to your needs.

The problem with doing this in a commercial setting is that companies have company-wide ’standard programming languages’, which limit your choice of tool, usually to just one. This makes sense from the business viewpoint as a mean of control and to ease up maintenance. This is a noble goal, but then some problem comes and that company-wide programming language will probably not be good enough for the problem at hand. Here is where the WTFs enter the equation.