RE: [PHP] stripping white space?
| From: | Maxim Maletsky | Date: | Tue, 10 Jul 2001 07:58:14 +0000 |
| Subject: | RE: [PHP] stripping white space? | ||
| Groups: | php.general | ||
| Request: | Send a blank email to php-general+get-57108@lists.php.net to get a copy of this message | ||
The fact is:
getting discouraged about using double quotes in HTML on integers I was
wondering what are the drawbacks of it. Maybe something I missed. Maybe
there's someone hating me using this style because his browser goes wild or
even crashes or does something else I never came across of.
It was a good question to ask and a good topic to make sure of other's
opinions.
---just my reasons of keeping this discussions.
-maxim maletsky
-----Original Message-----
From: Maxim Maletsky
Sent: Tuesday, July 10, 2001 4:54 PM
To: 'NavidYar2@home.com'; 'Bart Veldhuizen'; php-general@lists.php.net
Subject: RE: [PHP] stripping white space?
well, my dear patriot, I do.
Contaminating the web is not my main purpose. The usual life time of a web
application is around one year. I think our project will be changed ten
times before uncle Bob gets online.
Since there's no plans for us to use XML, since there's no way W3C goes
broke, since there's no way a 100MB large browsers will be released and,
most importantly, since there's no way in THIS ONE YEAR I AM TALKING ABOUT
anything rush will be changed to the planet's internet connection speeds - I
will build my site in the way that saves my and my team's development time
and with it our money, as well as the healthy page load time reduce.
Be rational, Navid.
...and don't take it personally.
-maxim maletsky
-----Original Message-----
From: Navid A. Yar [mailto:NavidYar2@home.com]
Sent: Tuesday, July 10, 2001 4:47 PM
To: Maxim Maletsky; 'Bart Veldhuizen'; php-general@lists.php.net
Subject: RE: [PHP] stripping white space?
"We do nothing with XML, so that is why I am so shocked why people
here discourage me that much."
Even HTML is headed toward a more efficient structure. The current browser
companies won't hold on to old code for long, just to make everything
backward compatible. Next thing we know, we'll have to download a 100MB IE
browser just cause it supports backward compatibility of older HTML and
client-side coding practices, which in turn will discourage people to
download a newer version of a browser. Imagine the year 2010, where uncle
bob is still stuck with IE 4.0 while everyone else is using IE 15.0. And
guess what? Uncle Bob is the one with the money to shop online, not little
joey who was born to see the 10.0 version and nothing earlier.
W3C will not maintain older DTDs for HTML 3.2 for long, language practices
die too, just like browsers and Windows 3.1/95. Standards are emerging to
make it easier for everyone. Technology moves forward, not backward. By
using good HTML practices, you're helping technology move in a steady upward
motion. Saving a few bytes will soon not make a difference once everyone
jumps into the high speed bandwagon, or when the broadband bottleneck
phenomenon is broken and when no one needs to worry about broadband anymore.
If you want small file sizes use other practices such as decreasing image
size or quality, etc. Just don't contaminate the web with the architecture
drawings of the prehistoric wheel. And I don't mean to sound so harsh,
please don't take it personally.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net
For additional commands, e-mail: php-general-help@lists.php.net
To contact the list administrators, e-mail: php-list-admin@lists.php.net