<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Do we really need HTML and CSS on the web?</title>
	<atom:link href="http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/</link>
	<description>baking cakes with CakePHP</description>
	<lastBuildDate>Tue, 31 Jan 2012 15:12:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Yebot</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-1018</link>
		<dc:creator>Yebot</dc:creator>
		<pubDate>Tue, 31 Oct 2006 05:41:50 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-1018</guid>
		<description>One can make beautiful websites with HTML and CSS.  One can make beautiful music with instruments and know-how.  Of course, the act of making music is a senseless one, but the world would be a boring place without beautiful music.  The act of making beautiful-looking websites may also be senseless, but a lack of beauty on the web would make it boring.

If content is king, beauty is queen.</description>
		<content:encoded><![CDATA[<p>One can make beautiful websites with HTML and CSS.  One can make beautiful music with instruments and know-how.  Of course, the act of making music is a senseless one, but the world would be a boring place without beautiful music.  The act of making beautiful-looking websites may also be senseless, but a lack of beauty on the web would make it boring.</p>
<p>If content is king, beauty is queen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markus Bertheau</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-815</link>
		<dc:creator>Markus Bertheau</dc:creator>
		<pubDate>Mon, 09 Oct 2006 04:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-815</guid>
		<description>Without doubt, content is the most important thing on a web page. But we humans perceive content with more ease if it&#039;s presented in a well readable form (See column layouts in all print media - It&#039;s not easy to make columns in your email or blog post). So on one hand HTML/CSS makes it possible to mark up content in an easily perceptable way, but on the other hand the same techniques -- font sizes, colors, faces, graphical elements -- can be used to create a web page that is overcrowded and distracts the reader from the real content.

In the end I think that just text wouldn&#039;t suffice. We could restrict the misuse of the presentational capabilities of HTML and CSS by using only semantical markup and a static CSS.</description>
		<content:encoded><![CDATA[<p>Without doubt, content is the most important thing on a web page. But we humans perceive content with more ease if it&#8217;s presented in a well readable form (See column layouts in all print media &#8211; It&#8217;s not easy to make columns in your email or blog post). So on one hand HTML/CSS makes it possible to mark up content in an easily perceptable way, but on the other hand the same techniques &#8212; font sizes, colors, faces, graphical elements &#8212; can be used to create a web page that is overcrowded and distracts the reader from the real content.</p>
<p>In the end I think that just text wouldn&#8217;t suffice. We could restrict the misuse of the presentational capabilities of HTML and CSS by using only semantical markup and a static CSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cakebaker</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-814</link>
		<dc:creator>cakebaker</dc:creator>
		<pubDate>Sun, 08 Oct 2006 16:58:35 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-814</guid>
		<description>@all: Thanks for your comments.

@Bret Kuhns: &quot;Do you really think the web would be as popular as it is today if everyone used a text-based browsers like they did in the early days of the internet?&quot; No, it was probably necessary to use design to attract new users to the web. But the more I use the web, the more unimportant the design of websites becomes. Nowadays, I read most content in my RSS reader ;-)

Yes, I know there are WYSIWYG tools out there. But for me it is not really WYSIWYG, because the &quot;what you get&quot; part depends on the browser you use.

@automagically: It is a good idea to use subdomains if you can automate that, but as soon as you have manually to maintain them, then it is too costly. 

@Leandro Ardissone: Well, even if a site is standard-compliant it could be unaccessible because a wrong font size was used, or wrong color combinations, etc. With removing the possibility to define such things you remove also such problems ;-)

@Hypercubed: Yes, HTML was intended for content, especially for structuring content. But is such a structure needed? Or wouldn&#039;t it be more interesting to see what structures would emerge?

@KesheR: Yes, design is important for humans. But there are areas where design is not that important: emails, forums, sms, newspapers, books, and IMHO the web.

I think it is not necessary to rebuild the web technologies from scratch (and almost impossible). An evolutionary process is better, and with RSS we currently see such an evolutionary step. 

@ryan &amp; scott lewis: That&#039;s true, with the blogging tools it is relatively easy to publish something. But for me the format used on the web should be like an extension of the plain text format, which even a non-technical person can edit with every editor.</description>
		<content:encoded><![CDATA[<p>@all: Thanks for your comments.</p>
<p>@Bret Kuhns: &#8220;Do you really think the web would be as popular as it is today if everyone used a text-based browsers like they did in the early days of the internet?&#8221; No, it was probably necessary to use design to attract new users to the web. But the more I use the web, the more unimportant the design of websites becomes. Nowadays, I read most content in my RSS reader ;-)</p>
<p>Yes, I know there are WYSIWYG tools out there. But for me it is not really WYSIWYG, because the &#8220;what you get&#8221; part depends on the browser you use.</p>
<p>@automagically: It is a good idea to use subdomains if you can automate that, but as soon as you have manually to maintain them, then it is too costly. </p>
<p>@Leandro Ardissone: Well, even if a site is standard-compliant it could be unaccessible because a wrong font size was used, or wrong color combinations, etc. With removing the possibility to define such things you remove also such problems ;-)</p>
<p>@Hypercubed: Yes, HTML was intended for content, especially for structuring content. But is such a structure needed? Or wouldn&#8217;t it be more interesting to see what structures would emerge?</p>
<p>@KesheR: Yes, design is important for humans. But there are areas where design is not that important: emails, forums, sms, newspapers, books, and IMHO the web.</p>
<p>I think it is not necessary to rebuild the web technologies from scratch (and almost impossible). An evolutionary process is better, and with RSS we currently see such an evolutionary step. </p>
<p>@ryan &#038; scott lewis: That&#8217;s true, with the blogging tools it is relatively easy to publish something. But for me the format used on the web should be like an extension of the plain text format, which even a non-technical person can edit with every editor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scott lewis (work)</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-813</link>
		<dc:creator>scott lewis (work)</dc:creator>
		<pubDate>Sat, 07 Oct 2006 21:27:54 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-813</guid>
		<description>I agree with Ryan. Basically, you&#039;re looking at the wrong level of abstraction. People want to &quot;make a webpage&quot; and &quot;get some information up there&quot;. That has nothing to do with writing HTML. Or, at least, it shouldn&#039;t. It comes down to tools. Blogger, et al. provide the tools to make a webpage and get some information up there without touching actual HTML.

To look at it from the opposite direction: HTML is a horrible format for presenting a document. Our minds aren&#039;t trained to jump over things like «BOLD» and «ITALIC» and just focus on the content. Not to mention the little dance you have to go through to get the page in the first place, I mean, who though GET / HTTP/1.0 was a human-friendly way to request HTML pages anyway?

We have these immensely powerful parsers, thick network clients, and renderers dedicated to reading HTML and presenting it&#039;s contents to us in a human friendly-way. When we read webpages we ignore the HTML and focus on the content. All that is required is to build tools that allow us to do the same when creating content.

WordPress, Blogger, etc.,  are just part of the infrastructure. The mythical &#039;average user&#039; shouldn&#039;t be expected to manage files in an Apache DocRoot any more than they should be expected to build a server, set up DNS entries, or write a TCP stack.</description>
		<content:encoded><![CDATA[<p>I agree with Ryan. Basically, you&#8217;re looking at the wrong level of abstraction. People want to &#8220;make a webpage&#8221; and &#8220;get some information up there&#8221;. That has nothing to do with writing HTML. Or, at least, it shouldn&#8217;t. It comes down to tools. Blogger, et al. provide the tools to make a webpage and get some information up there without touching actual HTML.</p>
<p>To look at it from the opposite direction: HTML is a horrible format for presenting a document. Our minds aren&#8217;t trained to jump over things like «BOLD» and «ITALIC» and just focus on the content. Not to mention the little dance you have to go through to get the page in the first place, I mean, who though GET / HTTP/1.0 was a human-friendly way to request HTML pages anyway?</p>
<p>We have these immensely powerful parsers, thick network clients, and renderers dedicated to reading HTML and presenting it&#8217;s contents to us in a human friendly-way. When we read webpages we ignore the HTML and focus on the content. All that is required is to build tools that allow us to do the same when creating content.</p>
<p>WordPress, Blogger, etc.,  are just part of the infrastructure. The mythical &#8216;average user&#8217; shouldn&#8217;t be expected to manage files in an Apache DocRoot any more than they should be expected to build a server, set up DNS entries, or write a TCP stack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ryan</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-812</link>
		<dc:creator>ryan</dc:creator>
		<pubDate>Sat, 07 Oct 2006 20:16:58 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-812</guid>
		<description>I think the current crop of popular blogging tools &amp; services - such as livejournal, wordpress, blogger, etc - have actually made content delivery as easy as you suggest; Opening up livejournal and making a new post takes about as much technical knowledge as firing off an email.</description>
		<content:encoded><![CDATA[<p>I think the current crop of popular blogging tools &amp; services &#8211; such as livejournal, wordpress, blogger, etc &#8211; have actually made content delivery as easy as you suggest; Opening up livejournal and making a new post takes about as much technical knowledge as firing off an email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KesheR</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-811</link>
		<dc:creator>KesheR</dc:creator>
		<pubDate>Sat, 07 Oct 2006 17:23:50 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-811</guid>
		<description>Damn, we are humans, we need colors and rounded boxes and all that makes an eye happy. It is necessary in some way.

For further discussion: should web technologies be rebuilt from scratch?</description>
		<content:encoded><![CDATA[<p>Damn, we are humans, we need colors and rounded boxes and all that makes an eye happy. It is necessary in some way.</p>
<p>For further discussion: should web technologies be rebuilt from scratch?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hypercubed</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-810</link>
		<dc:creator>Hypercubed</dc:creator>
		<pubDate>Sat, 07 Oct 2006 16:37:26 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-810</guid>
		<description>Like Bret said that was the intent of HTML.  HTML was all about content and nothing about markup.  Then people started to make very stylized web pages using images embedded in tables embedded in tables embedded in tables and so on.  Soon the HTML became so convoluted with style markups that the content became hidden.  That is where CSS and XHTML comes in.  If you move all the style to the CSS then the HTML/XHTML is only content.</description>
		<content:encoded><![CDATA[<p>Like Bret said that was the intent of HTML.  HTML was all about content and nothing about markup.  Then people started to make very stylized web pages using images embedded in tables embedded in tables embedded in tables and so on.  Soon the HTML became so convoluted with style markups that the content became hidden.  That is where CSS and XHTML comes in.  If you move all the style to the CSS then the HTML/XHTML is only content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leandro Ardissone</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-809</link>
		<dc:creator>Leandro Ardissone</dc:creator>
		<pubDate>Sat, 07 Oct 2006 16:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-809</guid>
		<description>The problem with the HTML and CSS is that WYSIWYG tools usually make the website non-standard compliant and this is the reason of the difficult of create HTML + CSS sites that looks good for everyone (including the standards geeks).

Otherwise, plain text is great. I love to read RSS for this reason, I have my reader with plain text and images from the post/article which becomes in a faster and clean reading. I think that this is the main reason for RSS is created apart of the read-all-at-the-same-place.

I will love to see all the internet like old BBS with only text and design means ASCII draws all around.</description>
		<content:encoded><![CDATA[<p>The problem with the HTML and CSS is that WYSIWYG tools usually make the website non-standard compliant and this is the reason of the difficult of create HTML + CSS sites that looks good for everyone (including the standards geeks).</p>
<p>Otherwise, plain text is great. I love to read RSS for this reason, I have my reader with plain text and images from the post/article which becomes in a faster and clean reading. I think that this is the main reason for RSS is created apart of the read-all-at-the-same-place.</p>
<p>I will love to see all the internet like old BBS with only text and design means ASCII draws all around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: automagically</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-808</link>
		<dc:creator>automagically</dc:creator>
		<pubDate>Sat, 07 Oct 2006 16:28:28 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-808</guid>
		<description>That does make sense.  I think another example of content being king is the fact that I read your site through my RSS on Netvibes, so whatever the site looks like, doesn&#039;t really matter, I just want the content.

I like the idea discussed on Digg a while back, of just providing different versions of the site under subdomains.  Like txt.example.com would be straight up text files, or look basic like Craigslist, since you gotta have links and forms at least!  Or do you?  Hmm.  I can see benefits of creating a basic version of your site, akin to craigslist.  Might be really helpful for people with disabilities (and avoiding law suits, unlike Target), and could just use the same content from the database of the normal site.  I start out with a basic wireframe skeleton type site with no styling while writing the php and testing forms anyways, why not keep it for that subdomain?</description>
		<content:encoded><![CDATA[<p>That does make sense.  I think another example of content being king is the fact that I read your site through my RSS on Netvibes, so whatever the site looks like, doesn&#8217;t really matter, I just want the content.</p>
<p>I like the idea discussed on Digg a while back, of just providing different versions of the site under subdomains.  Like txt.example.com would be straight up text files, or look basic like Craigslist, since you gotta have links and forms at least!  Or do you?  Hmm.  I can see benefits of creating a basic version of your site, akin to craigslist.  Might be really helpful for people with disabilities (and avoiding law suits, unlike Target), and could just use the same content from the database of the normal site.  I start out with a basic wireframe skeleton type site with no styling while writing the php and testing forms anyways, why not keep it for that subdomain?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bret Kuhns</title>
		<link>http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/comment-page-1/#comment-807</link>
		<dc:creator>Bret Kuhns</dc:creator>
		<pubDate>Sat, 07 Oct 2006 16:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2006/10/07/do-we-really-need-html-and-css-on-the-web/#comment-807</guid>
		<description>HTML was originaly designed for the very purpose that you mention. Its original incarnation was nothing more than a markup langage used to style text in a way that aided information sharing. If you look at the original HTML tags, there wasn&#039;t much in the way of stlyish formatting (images, layouts, etc). All of that changed, and perhaps for a reason? The web is now a maketable industry. News channels on TV are supposed to be so that people can get news information, but all the news channels are always working to make the nicest looking sets, get more attractive anchors, and use snazzy video effects with their news reports. None of this really affects the information they provide, it just gets more people to watch, and the more people watching means more advertisement revenue for the network. Do you really think the web would be as popular as it is today if everyone used a text-based browsers like they did in the early days of the internet?

And in response to &quot;HTML and CSS are (too) complex, which makes it difficult for non-technical people to create websites&quot;. Does WYSIWYG ring a bell? It&#039;s not the perfect solution, but it works for non-technical people. I can think of a few small businesses that rely on Dreamweaver to create their online presence.</description>
		<content:encoded><![CDATA[<p>HTML was originaly designed for the very purpose that you mention. Its original incarnation was nothing more than a markup langage used to style text in a way that aided information sharing. If you look at the original HTML tags, there wasn&#8217;t much in the way of stlyish formatting (images, layouts, etc). All of that changed, and perhaps for a reason? The web is now a maketable industry. News channels on TV are supposed to be so that people can get news information, but all the news channels are always working to make the nicest looking sets, get more attractive anchors, and use snazzy video effects with their news reports. None of this really affects the information they provide, it just gets more people to watch, and the more people watching means more advertisement revenue for the network. Do you really think the web would be as popular as it is today if everyone used a text-based browsers like they did in the early days of the internet?</p>
<p>And in response to &#8220;HTML and CSS are (too) complex, which makes it difficult for non-technical people to create websites&#8221;. Does WYSIWYG ring a bell? It&#8217;s not the perfect solution, but it works for non-technical people. I can think of a few small businesses that rely on Dreamweaver to create their online presence.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

