>> Common sense says: write to standards,

Color me stupid but I am not understanding what that means, "Write to
standards". I ran across the same thing here on this page.

http://paulirish.com/2011/browser-market-pollution-iex-is-the-new-ie6/

“Corporate users should be testing their applications against standards,
not browser version numbers.”


What does that mean, " testing their applications against standards"? Any
elucidation, or clarification would be greatly appreciated.

Many TIA,
G!


On Thu, Nov 17, 2011 at 3:17 PM, Judah McAuley <[email protected]> wrote:

>
> Oh, I agree Russ, but you were making absolutist statements, not using
> common sense. Common sense says: write to standards, tweak as required
> for individual customer needs, plan periodic refreshes to better take
> advantage of improving/changing technology.
>
> Cheers,
> Judah
>
> On Thu, Nov 17, 2011 at 12:13 PM, Russ Michaels <[email protected]>
> wrote:
> >
> > you have to use a bit of common sense here, obviously every app in the
> > world was not written by you and does not work the same as yours, if
> > they did then this thread would not exist nor would the previous
> > comments.
> >
> >
> > On Thu, Nov 17, 2011 at 7:01 PM, Judah McAuley <[email protected]>
> wrote:
> >>
> >> Not at all true, Russ.
> >>
> >> Here's a website that I wrote in 1994 that is archived (archive.org
> >> only has it back through 1996) that works just fine in Chrome 16, IE 9
> >> and FireFox 8 on a Windows 7 box.
> >>
> >>
> http://web.archive.org/web/19961018091409/http://babel.uoregon.edu/yamada/guides.html
> >>
> >> None of those browsers even existed when I started that in 94. I was
> >> targeting HTML specs and, lo and behold, still works fine 15+ years
> >> later on browsers I could not have imagined at the time.
> >>
> >> Judah
> >>
> >> On Thu, Nov 17, 2011 at 9:45 AM, Russ Michaels <[email protected]>
> wrote:
> >>>
> >>> not exactly true.
> >>> If you have a 5 year old app that was written for the browsers of the
> >>> time, it wont matter whether it was written for just 1 browser or for
> >>> all browsers, it will still be out of date now and will still need
> >>> updating for the latest browsers.
> >>> If however it was only written to work for say IE then it only needs
> >>> to be fixed for IE, much less work/time and cost.
> >>> Making an app cross browser does not magically make it future proof.
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:348799
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to