Geeks With Blogs
Jim Becher blog

I was at an interesting presentation the other day where Rocky Lhotka talked on “Creation of Distributed Object-Oriented Applications in .NET”.  His presentation was very well done and I enjoyed listening to all the information and ideas.  When he was speaking I caught something from him that I had not thought about before.   He mentioned that the web as we know it is dead.  And if you think about it he is correct.  

 

Let’s stop and take a look at this idea.  Do you know what features will be in http v3.0?  Well, you probably don’t because there is no v3.0.  In fact, there is no plan to enhance the v1.1 standard.  If you think about it, the http protocol was never intended to deliver audio, video, high volumes of reliable information.  Yet, this is what we call the web.   A great thought to go along with this is a web developer is essentially like a COBOL or mainframe programmer today.  It seems like we are just working with an outdated environment and are just keeping it going.   I’m not saying it is not being utilized, or there is not a lot of potential still there.  But, I have to imagine we are going to outdate the web as we know it soon. 

 

We have enhanced how we access the web (broadband, wireless and other things).  But the mechanism, a.k.a the browser is still really the same.  We have added some features, toolbars, tabs, and activeX to the browsers.  But, as far as I can tell I have not seen many enhancements since Netscape 4. 

 

I am not claiming to know the future, but there has to be something out there to allow us to use our networks (web) as a better medium.

Posted on Thursday, August 11, 2005 11:19 AM | Back to top


Comments on this post: Future of Web Development

# re: Future of Web Development
Requesting Gravatar...
You're full of crap!

Ok. Not really. Interesting point. However, you could say the same thing about cars too. The basic technology behind cars hasn't changed in 100 years, yet there's no change forseen in the auto industry.

The HTTP transport wasn't designed to do a lot of the stuff it is doing today, but that doesn't mean it can't handle it. I think HTTP is too ingrained to be yanked out any time soon (read, next 10-15 years). What you may see is a better transport come around, but the web will be on HTTP 1.1 for a while.

SOAP over HTTP isn't the best, and that may be the first place we see a new transport, but it'll always be backwards compatible with HTTP.

Joel
Left by Joel Ross on Aug 11, 2005 7:33 PM

# re: Future of Web Development
Requesting Gravatar...
Good points. I would not disagree. HTTP will be around for a long time. But, what is next? That I do not know. If we keep coding for HTTP are we missing something for the future to move us forward?

I had never thought of this before, so I am going to probably be collecting some thoughts on this for a while.
Left by Jim Becher on Aug 12, 2005 6:27 AM

Your comment:
 (will show your gravatar)


Copyright © Jim Becher - Untangle the Web | Powered by: GeeksWithBlogs.net