Our friends at Google are at it again with a "super cool" mapping application that blows everyone else away. Not sure how this app works yet...and probably haven't just searched the net enough to find out how.
But it's damn cool!
Tuesday, February 08, 2005
Howard Lewis Ship - Brilliant, Self Promoting Jackass, or Both?
Check out Howard's latest missive on The Server Side.
I'm not sure what to think of this guy. Every time he lays out a well thought out post, that everyone can learn from, helping to make their own mind about stuff....he ends up ruining it.
He outlines a fine commentary on why people get confused over IoC and/or DI:
But, just in case he is...Howard, take a clue, and just put it in your sig. At least then you wouldn't be tooting your own horn so much trying to make people think you're so freaking cool. How Tapestry/HiveMind does things is not part of the subject. Maybe you should blog about it and have people click over to your site to learn about it.
Perhaps "take it to email" needs to be updated to "take it to your blog". That's why I'm posting this here and not on that thread! It's not relevant to the thread whatsoever.
I'm not sure what to think of this guy. Every time he lays out a well thought out post, that everyone can learn from, helping to make their own mind about stuff....he ends up ruining it.
He outlines a fine commentary on why people get confused over IoC and/or DI:
I have seen a common thread among people who "don't get IOC" that they confuse an object constructor with the construction of a service.And then proceeds to screw it all up with the following self-promoting lump of crap:
The object is not the service (it's a key part of the service, but not the service itself). The object's constructor is not the services constructor.
Adding more code never makes things simpler! This kind of heavy weight approach just shifts the design towards more heavyweight, monolithic services. I prefer the opposite ... small, easily testable services with minimal dependencies.
In Tapestry 3.1 (which is built on the HiveMind microkernel), most of my services inject fewer than three collaborators, often just one or two. So, even though there are dozens of individual services, testing is under control because no single service is that complicated. I know the system works because I do very complete unit testing, plus a good amount of automated integration testing.What the hell is that? Why does this guy repeatedly ruin any good commentary he has by being so brazen to self promote his next consulting gig? It's highly obvious it's what he's doing, despite any claims otherwise. I can't believe he'd be that naive when it comes to posting.
But, just in case he is...Howard, take a clue, and just put it in your sig. At least then you wouldn't be tooting your own horn so much trying to make people think you're so freaking cool. How Tapestry/HiveMind does things is not part of the subject. Maybe you should blog about it and have people click over to your site to learn about it.
Perhaps "take it to email" needs to be updated to "take it to your blog". That's why I'm posting this here and not on that thread! It's not relevant to the thread whatsoever.
Friday, February 04, 2005
Java Weenies Part 2
Checkout this crap.
This is what I mean when I talk about Java Weenies. It's not so much that they're bitching just to bitch. People wax poetic about open source solutions, but don't even want to contribute to the process to make the JCP standards better. It's just bitching upon bitching.
What really amazes me, is the Spring-like features of JSF that are largely ignored by these weenies. The faces-config.xml with it's dependency injection is amazingly powerful. It's a brilliant solution, and yet, people want to complain.
Here's the thing weenies. If you want to keep using Tapestry, or some other technology. Use it! But don't bitch years down the road when a JCP technology has more job postings or more people wanting to know about it.
You see, here's the thing about Tapestry, it's been around for how long now? It's on what version? And how many real users does it have, building real hard core sites? Freaking PHP has more real users than Tapestry!
But here's the thing...I'm glad Tapestry, WebWork, JSF, etc. are around. Competition is good! And admit it, you really didn't want Oracle or IBM mucking in with your OS framework did you?
NO! Wow....then stop bitching. Make constructive comments...but stop bitching and whining. It's not good for interviewing for your next job using JSF.
This is what I mean when I talk about Java Weenies. It's not so much that they're bitching just to bitch. People wax poetic about open source solutions, but don't even want to contribute to the process to make the JCP standards better. It's just bitching upon bitching.
What really amazes me, is the Spring-like features of JSF that are largely ignored by these weenies. The faces-config.xml with it's dependency injection is amazingly powerful. It's a brilliant solution, and yet, people want to complain.
Here's the thing weenies. If you want to keep using Tapestry, or some other technology. Use it! But don't bitch years down the road when a JCP technology has more job postings or more people wanting to know about it.
You see, here's the thing about Tapestry, it's been around for how long now? It's on what version? And how many real users does it have, building real hard core sites? Freaking PHP has more real users than Tapestry!
But here's the thing...I'm glad Tapestry, WebWork, JSF, etc. are around. Competition is good! And admit it, you really didn't want Oracle or IBM mucking in with your OS framework did you?
NO! Wow....then stop bitching. Make constructive comments...but stop bitching and whining. It's not good for interviewing for your next job using JSF.
Subscribe to:
Posts (Atom)