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.
On Thu, Nov 17, 2011 at 4:22 PM, Maureen <[email protected]> wrote: > > Marrying themselves to proprietary technology was wrong 15 years ago, and > it's still wrong now. Unfortunately for the taxpayers and consumers, we're > the ones who have to pick up the tab when the obsolete tech bites them. > > On Thu, Nov 17, 2011 at 3:47 AM, Roger Austin <[email protected]> wrote: > >> >> Many companies will make policy on "standard" browsers. They write >> those standards in the specs for applications when they buy or write >> them. Back during the time of IE6, it was commonly the standard >> browser for businesses so developers created applications using IE6 >> only techniques like COM and/or ActiveX objects. >> >> This is still happening. Making applications work in all browsers is >> a specification that adds to costs. We might think that apps working >> in all browsers is a no-brainer, but many people in businesses look >> at it differently. >> > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:348793 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
