Axiom and Deker didn't belive me....

w3c on hiatus = na na na na na-na...told you so:


http://www.cnn.com/2001/TECH/internet/12/17/web.standards.project.idg/

http://www.zdnet.com/zdnn/stories/news/0%2C4586%2C2832845%2C00.html?chkpt=zdnn_nbs_hl

And in an interview with Jeff Zeldman, one of the founders of the w3c:

Why disband now? Aren't Web standards more important than ever?
Well, we're not disbanding. We're taking a short break of sorts, chiefly in acknowledgement of two things. One: To a great extent, the browser makers have complied with the demands spelled out in our mission statement of 1998--thus some of our reason for being has gone away. Two: Much work remains to be done, particularly in the field of education--developer and client. But at this moment, we do not have the internal resources to do all the work that is necessary.

If that changes in the next few months, we will come back strong. If not, then we will speak from time to time from our WaSP pulpit--and individual members will continue to act as standards evangelists inside or outside the WaSP. The Web Standards Project is not magic. The standards developed by W3C, if seized upon as a resource by the design and development community, could make an almost magical difference in the way the Web works.

For all the "efforts" that the w3c group has made, creating webpages is still a crazy process of trial and error for cross-browser compatibility for me. I hope this is a permanent hiatus.

Imagine what it would have been like without the w3c mrbogus... no CSS...

For all the "efforts" that the w3c group has made, creating webpages is still a crazy process of trial and error for cross-browser compatibility for me. I hope this is a permanent hiatus.

Ahh. Ignorance is bliss...is it not.

1 - The efforts of the consortium will do absolutly no good if browser builders do not adhere or take into account the recommendations made by the consortium.

2 - Creating webpages is not a tiral and error process if you know what you want to create and how to create it. There are work arounds for the short comings of every browser ever developed. If someone has found it, it's on the internet. All you have to do is look.

3 - If it were not for the w3c, you would have no standardization of HTML/XML/CSS or any of the other things that make site development 100 times easier than it was 3 years ago.

Do not blame the fact that developing sites is difficult for you on an organization that has done more for web development and design than any browser builder.

Not Microsoft.

Not Netscape.

Not even Opera. Although, they have come the closest to support the recommendations than anyone else.

As for you matt. I never disagreed about the w3c being on hiatus. I haven't been around much lately, so I assume anything is possible.

I don't have to take that from a guy who doesn't even have a sig!

All I know is, I make pages in Dreamweaver & Indesign. Many times they do NOT look the same in all browsers.

All their standards haven't helped me one bit and that is the truth, and nothing but the truth.

if it wasn't for the w3c, we would all be speaking german right now!

Nah.... you control your own code...

I make my pages in Dreamweaver and notepad.. and will careful editing, i'm able to make my pages appear the same in 3 browsers, IE, netscape and Opera

The only thing i can't control is how the browser accepts css..

All I know is, I make pages in Dreamweaver & Indesign. Many times they do NOT look the same in all browsers.
All their standards haven't helped me one bit and that is the truth, and nothing but the truth.

*shrug* put down your crutch for a while and you might appreciate the w3c's work.

Originally posted by mrbogus
I don't have to take that from a guy who doesn't even have a sig!

OMG! you're right! Bann Axiom! No sig... tsss.
No sig!????????

Arrgghhhhh!!!!!!!

Really no sig! :eek:

you can't do your html right, caus' you don't have a sig.

If someone's site doesn't look the same in all three browsers, then it's their own fault for being too lazy to make standards compliant code so that it will look the same in all three browsers. Dreamweaver does not write standards compliant code. Therefore it is Dreamweaver's, and the designer's fault, not the W3C. All of the browsers are getting closer and closer to supporting standards compliant code, and when they do, we won't have to worry about it anymore.

Some of my sites don't work in all of the browsers either, but I know that that is my own fault, not the W3C's or Dreamweaver's or even Bill Gates.

If you have to blame someone;

Blame dreamweaver

Blame the people that make web browser that don't support the standards

Blame yourself for being too lazy to code your page to work in all the browsers

Don't blame the W3C. They are the only people trying to fix this huge mess.

As for them being on hiatus... I think I actually read that somewhere too, I just wanted to argue with you, Matt.