beta2 XHTML compliance? is this necessary. OR STUPID...read UP MICROSOFT

[rhat]

I heard that beta 2 now makes ASP.NET xhtml compliant.

Can anyone shed some light on what this will change and it will break stuff
as converting HTML to XHTML pages DO break things. see,
http://www.alistapart.com/articles/betterliving/

I read on
http://msdn.microsoft.com/netframewo...etfxcompat.asp

It said they changed stuff like this

" Standards Compliance: The HTML rendering in ASP.NET was updated to be
XHTML 1.0 Transitional, which is standards compliant "

which is again another STUPID standard compliance mindnumb robot type of
thinking. Standard compliance is and will NEVER be important as getting it
to work on multiple browsers, period. What good is standards if the app
doesn't even work? How about a new standard? It's called getting it to work
instead of listening to some stupid committee who sits around all day in
conference talking to each other but know nothing of the real world in
getting things to actually work.

[Logan Greenlee]

Gary,

You replied to my post and not our difficult developer friend, Rhat.

"Gary Bond" wrote:

rhat

You ought to be ashamed of yourself. All of these guys here are trying to
help, and all you can do is be rude like a spoilt brat. Look at the last
line of Teemu Keiski's post, it said

"Maybe we can help? "

Grow up and leave these newsgroups for people who appreciate the help here,
and can be polite and not throw a tantrum like a 3 year old.
"Logan Greenlee" wrote:

Your line of thinking is exactly why you have to code for multiple browsers
in the first place. If everyone agrees, and complies with the same standards
one will get the same result. If everyone makes an effort to be standards
compliant - then everything will perform the same way.

Also you'll find that standards compliance its not required. You can
certainly continue to write your non compliant browser breaking code. VS.NET
helpfully points out your errors and you have an opportunity to correct them.

"rhat" wrote:

I heard that beta 2 now makes ASP.NET xhtml compliant.

Can anyone shed some light on what this will change and it will break stuff
as converting HTML to XHTML pages DO break things. see,
http://www.alistapart.com/articles/betterliving/

I read on
http://msdn.microsoft.com/netframewo...etfxcompat.asp

It said they changed stuff like this

" Standards Compliance: The HTML rendering in ASP.NET was updated to be
XHTML 1.0 Transitional, which is standards compliant "

which is again another STUPID standard compliance mindnumb robot type of
thinking. Standard compliance is and will NEVER be important as getting it
to work on multiple browsers, period. What good is standards if the app
doesn't even work? How about a new standard? It's called getting it to work
instead of listening to some stupid committee who sits around all day in
conference talking to each other but know nothing of the real world in
getting things to actually work.

[Logan Greenlee]

Gary,

You replied to my post and not our difficult developer friend, Rhat.

"Gary Bond" wrote:

rhat

You ought to be ashamed of yourself. All of these guys here are trying to
help, and all you can do is be rude like a spoilt brat. Look at the last
line of Teemu Keiski's post, it said

"Maybe we can help? "

Grow up and leave these newsgroups for people who appreciate the help here,
and can be polite and not throw a tantrum like a 3 year old.
"Logan Greenlee" wrote:

Your line of thinking is exactly why you have to code for multiple browsers
in the first place. If everyone agrees, and complies with the same standards
one will get the same result. If everyone makes an effort to be standards
compliant - then everything will perform the same way.

Also you'll find that standards compliance its not required. You can
certainly continue to write your non compliant browser breaking code. VS.NET
helpfully points out your errors and you have an opportunity to correct them.

"rhat" wrote:

I heard that beta 2 now makes ASP.NET xhtml compliant.

Can anyone shed some light on what this will change and it will break stuff
as converting HTML to XHTML pages DO break things. see,
http://www.alistapart.com/articles/betterliving/

I read on
http://msdn.microsoft.com/netframewo...etfxcompat.asp

It said they changed stuff like this

" Standards Compliance: The HTML rendering in ASP.NET was updated to be
XHTML 1.0 Transitional, which is standards compliant "

which is again another STUPID standard compliance mindnumb robot type of
thinking. Standard compliance is and will NEVER be important as getting it
to work on multiple browsers, period. What good is standards if the app
doesn't even work? How about a new standard? It's called getting it to work
instead of listening to some stupid committee who sits around all day in
conference talking to each other but know nothing of the real world in
getting things to actually work.