The Java Drivel
"... and for this I will use a factory generator factory which gives me references to a repository manager."
I gave the Java engineer a blank stare.
He leaned back in his chair and crossed his hands behind his head apparently relaxing.
"That's the way to do it in Java."
I already could see another 200 MB main memory going down the drain and into the bowel of some Java application. And the start-up time would reach lunch-break dimensions.
My whole IT life was passing before my inner eye. I remembered the Z80 with the whopping 1MHz clock rate and the turbo fast Turbo Pascal which I used to write interrupt handlers. I remembered the VAX cluster in 1986 where we ran huge scientific apps. They would fly.
Now, many many Moore cycles later the quad core machine with the 4GB would crawl under the load of one single, bloody Java app server.
"And as long as every application is implementing the FactoryGeneratorInstancePropertyManagerRepositoryInterface everything should work."
What should I think of a language which needs so many patterns? Maybe that something is seriously wrong with the object model? I closed my eyes, dreaming of a better world.
"It is really easy."
he tried to push his point.
In vain, because I definitely knew that in Perl I would just write this single line tie-ing a hash to a YAML file.
But then I realized something: The corporate world had pushed this language to make itself independent from the programmers. To make them exchangeable, outsourceable.
And as punishment they got ridiculously complex, ill-adjusted technology, long development cycles and the whole rat-tail of additional tool-chains.
I wicked smile crept onto my face:
- "Sounds great. Let's do it that way."
I just kept a Java developer busy for a year.