Comments on: If you are a web developer, please learn HTTP

By: Stephen

Stephen — Thu, 13 Dec 2007 06:21:23 +0000

What a great reply. I really appreciate the thought you put into the response.

Upgraded to A ;-)

By: Sam

Sam — Wed, 05 Dec 2007 15:04:31 +0000

@Stephen: Fair enough. I’m frustrated, I sound like a condescending ass. I know. Not one of my best posts. I almost stopped at the first sentence but figured I’d explain what was bugging me.

If I’d let it sit a day, I would have rewritten this to sound less condescending. As it stands, I agree that it’s not a convincing exhortation. Lesson learned.

What does “communicating directly with Java objects” mean? Perhaps a poor choice of words, but I still think of calling methods as sending messages. Sending messages sounds a lot like communication. Metaphors are common in programming.

Using DWR helps support the illusion of using JavaScript in the browser to call methods directly on Java objects that live on the server. My putting “directly” in quotes was meant to underscore that it is an illusion. If a developer believes that JSP code executes directly in the browser, though, there’s nothing illusory about what DWR does: to them, it makes a direct method call. That conceptual misunderstanding causes real problems.

By: Stephen

Stephen — Wed, 05 Dec 2007 06:09:53 +0000

Just came across this blog entry, quite randomly.

This is really condescending post, and it’s not much of a contribution. Not even technically accurate (communicating directly with Java objects? haha, what does that even mean?)

Blog grade: D-

By: Michael Kohout

Michael Kohout — Tue, 04 Dec 2007 16:42:55 +0000

You know, every time you say Java objects aren’t passed directly to the browser through some sort of magical portal, an idealistic young junior developer dies.

CLAP CLAP CLAP!!!!!!!

Don’t worry. I saved him.