Linked by Thom Holwerda on Thu 6th Dec 2007 16:27 UTC
Permalink for comment 289020
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



Member since:
2005-04-01
Know what else doesn't solve a problem? CSS. HTML outputs plain old Times New Roman in most browsers, and that would be perfectly readable.
Come to think of it, colored clothes don't solve a problem - all clothes in white or tan - whatever cottom is - would be just fine.
Let's get rid of spices, the only problem solved by food is nutrition, and we don't need it to taste good to meet our caloric and nutritional requirements.
Obviously, the point here is that the world is not black and white. HTML email does solve problems for most people: inline images are useful and quicker, formatted text grabs attention and higlights important text, etc.
In fact, if you ever use bold tags in your articles, you ought to understand why some people believe that the ability to use HTML in email is worthwhile.
So if my problem is that I want to present an image to someone inline with instructional text, what is the solution? Suck it up and attach a rich text document at 200K or just go HTML email and do it in 40K?