JavaScript: What, Why, and How
** This thread discusses the article: JavaScript: What, Why, and How **
Keep in mind that even though 6% use Netscape, it's probable that at least half of them also have IE on their desktop but choose to use Netscape instead. They COULD use IE if your application was compelling enough. So, if you program your application for IE you will have probably covered 97% of the market. What more could you want? Remember one thing to keep perfectly clear. It's not a religious war it's about business. Use the tools that work best. I would never think of telling a vendor that they must use UPS instead of FedEx, I only want the package delivered. chuck Opinions expressed are not necessarily those of my employer. "Joe Pluta" wrote in message news:6ae7eeba.11@WebX.WawyahGHajS... > Which browsers to support is always a difficult decision, but it's just a business decision. When you decide on support, you have basically the following choices: > > 1. Implement all features on all browsers > > 2. Do not provide certain features to some users > > 3. Provide only features that work on all browsers > > Option one is more expensive, in some cases MUCH more expensive, as time you could be spending on product features is instead routed to browser support. Option three is a lose-lose situation for everybody, especially if you decide to standardize on an earlier browser such as Netscape 4. > > It's a clear case of business goals. Since the vast majority of my clients are B2B as opposed to C2B, they find it easier to dictate IE choice to their end users. Especially since some 94% of users use IE anyway, as opposed to about 3% on various versions of Netscape. And since my clients want function key support and field editing, they are more than willing to use IE. I've found very few businesses thus far that have standardized on non-Windows desktops. > > You need to realistically assess how many users you have that have standardized on non-IE browsers. Then you have to decide what level of support you will give them, and how far down the chain you support. Netscape 7? Netscape 6? Netscape 4.57? Opera? Lynx? > > Currently, no PSC/400 clients require Netscape. One prospect bailed because they wanted to standardize on Internet appliances (thin clients) with Netscape 4.57, but that's the only time anybody ever balked. > > Are you writing B2B or C2B? B2B users tend to need power data entry, with heads down keying and function keys and the like. These folks are far more likely to standardize on IE. C2B applications, on the other hand, are usually much more of a point-and-click (or "point-and-think") type of interface. These don't perhaps need function keys and field editing, and can instead rely on the rather less powerful techniques supported by Netscape. > > Joe
** This thread discusses the article: JavaScript: What, Why, and How **
Keep in mind that even though 6% use Netscape, it's probable that at least half of them also have IE on their desktop but choose to use Netscape instead. They COULD use IE if your application was compelling enough. So, if you program your application for IE you will have probably covered 97% of the market. What more could you want? Remember one thing to keep perfectly clear. It's not a religious war it's about business. Use the tools that work best. I would never think of telling a vendor that they must use UPS instead of FedEx, I only want the package delivered. chuck Opinions expressed are not necessarily those of my employer. "Joe Pluta"
Comment