Week in review
Despite my ranting and raving, it looks like the just4log guy is a glutton for punishment. He’s gone and released a new version. The killer feature now is the ability to add log statements to entry and exit points of every method. Needless to say you need to preprocess your class files through an ant task to gain this amazing functionality. I mean really, if you’re going to butcher bytecode for such nefarious purposes, you should at least try and be vaguely fashionable and use some AOP. The ‘hello world’ of almost every AOP system out there involves logging.
Jason also demonstrates once again his sledgehammer approach to life. Find a tool you like and harpoon every problem you come across with said tool. Ignore geometry of said problem’s pegs, and its relation to said tool’s shape and size. Take a deep breath Jason, I’m about to turn your brain inside out. I can use EJB’s, and I can also think that inheritance is a good thing. However, and here’s the truly zen aspect of it all, that does NOT imply that I use EJB’s with inheritance. Each has its place. You yourself just posted that remote, distributed, scalable architectures are not some kind of holy grail to be pursued at all costs. Most people I suspect rarely write anything more challenging than an intranet app with, if you’re really lucky, about 100 users. So for those kinds of projects, bragging that your app will scale to thousands of users is entertaining, but rather pointless as it’s a claim that’ll never be challenged by real life.
Finally, for those who didn’t ‘get’ it, I am in fact an op on #java, and I thoroughly recommend those of you who are prone to getting upset easily and crying every few minutes to stop in there, we’ll show you how to develop a thicker skin in no time. The rest of you can stop in too, since it’s a lot more fun than doing any real work.
July 28th, 2003 at 12:31 pm
Hmm… here we are again… you posting silly slams of me based on not much… My comment about EJBs and inheritance was a joke:
joke ( P ) Pronunciation Key (jk)
n.
1. Something said or done to evoke laughter or amusement, especially an amusing story with a punch line.
2. A mischievous trick; a prank.
3. An amusing or ludicrous incident or situation.
4. Informal.
1. Something not to be taken seriously; a triviality: The accident was no joke.
2. An object of amusement or laughter; a laughingstock: His loud tie was the joke of the office.
And my point about not needing remote objects was exactly that this connection of scalability requirements with distributed objects is a silly fallacy. BTW, I’m an architect for a large scale enterprise software product during the day, so, yes, I know the difference between an intranet app and something that needs to scale.
July 28th, 2003 at 1:51 pm
I hereby nominate fate for mixed metaphor of the week award. I don’t ever want to be harpooned by a sledgehammer.
July 28th, 2003 at 7:20 pm
LOL,
well, he IS the biggest village idiot of them all, so what do you expect? hehe…