« Messenger Spam | Main | Win32 Blog Clients for MT »

April 20, 2003

Old vs Current vs Next Web

While I was playing around with CSS, learning a bit about XHTML, I got the exact same feeling as Sterling Hughes. As he noted: I want my web back. Isn't these technology supposed to be more obvious to human? I don't know. I am a long time C/C++ developer and ever developing with Java/VB. It's easy for me to start HTML coding (as nature as other programmer or non-programmer) without keep following the standard and trend. Maybe it's because of the non-concentration on this web technology, where I still pretty much stay at the old client-server and Unix programming world. Or maybe it's just the same stuff where vendors' implementation/own benefit collide with the standard, then causing all the mess....

Even though, I still prefer the current going with CSS/XHTML/XFORM...but I wonder how many web developers out there have adopted it? More than 50%? I 've got a feel of like C++ communities, where one of the gruop focusing on all pragmatic issue regarding their product, without knowing much of deployment of C++ template/generic programming; and other group focusing much on the standard compliant, complicated semantics issue (it take how many years for one C++ developer to understand most of the its semantic?), and the exciting template experiments.

Whatever it is, choose what are you comfortable for. Let the market decide by itself.

April 20, 2003 11:52 AM | Computing
[ Trackback URL for this entry: http://www.yowkee.com/cgi-bin/mt-tb.cgi/12 ]
Comments/Trackback
Related entries in yowkee essential
Related blogs from Waypath
Waypath
Old Coding Habits Die Hard - asterisk*
[asterisk*] - Friday, August 29, 2003
Old Coding Habits Die Hard August 28, 2003 | 2 Comments | Post a Comment Or, The Tale of The Table. ... I mean if you ve been doing something the same way for years and it works the same every time it can be a hard habit to break. ... I d bet even the most forward-thinking designers and developers revert back to old habits now and then. ... The point here is the more comfortable, old second nature way of doing this was actually much more complex than the new way I did it. ... It's a true case of old habits die hard, and some people cannot ...
Standards don't necessarily have anything to do with being semantically correct (kottke.org)
[kottke.org] - Wednesday, August 27, 2003
Standards don't necessarily have anything to do with being semantically correct posted August 26, 2003 at 11:52 pm ET Since the push toward good HTML/CSS/XHTML standards started a few years ago, browsers have gotten better at rendering standards-compliant code correctly and web designers have gotten better at writing standards-compliant code. ... But what I feel like is being implied in the effort to get more people to embrace standards compliancy is that coding a page in valid XHTML with valid CSS involves improving the semantic meaning of ...
White Noise: Standards and Semantic markup Archives
[White Noise] - Monday, September 1, 2003
Standards and Semantic markup Kottke.org on the complimentary, but not necessarily interdependant concepts of XHTML/CSS design and semantically correct markup: Coding web documents in valid XHTML doesn't make them semantically useful nor does coding semantically correct documents mean the documents are standards-compliant; they are two distinct things but a powerful combination. ... As web designers, we need to be aware of what we're getting with standards compliancy and semantically rich documents and that one does not necessarily lead to ...