.. and the number of people that are used to procedural and don't grasp OO concepts in general, or those use to lack of standards and find Java restrictive because it imposes a certain framework, etc... Or we could generalise this with "the problem is definitely in the Java anguage, and not in the way we use it badly"....t0ne wrote:I think most of the problems with Java are the number of bloated over-engineered frameworks that sprung up everywhere and half the world believing they needed full on J2EE for everything.
"if the only tool you have is a hammer, then every problem begins to look like a nail" is an antipattern I quote regularly. Same as the number of people using Excel for everything because that's what they're most familiar with, bending a spreadsheet tool to perform functions required of databases, calendars, etc.Malf wrote:But of course my bosses are of the opinion that you can use the same old approach no matter the tool. I can hardly wait to start screwing in some nails...
I suppose the flipside is reinventing the wheel each time and completely ignoring code re-use. But right tool for the job, right time and a place, and everything.






