Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Let it go

Freshness Warning
This blog post is over 20 years old. It's possible that the information you read below isn't current and the links no longer work.

Dear Client,

Netscape 4 is now six years old. Could we please stop catering to an old, buggy browser that is incompatible with all other browsers?


Jim Ray
June 9, 2003 12:55 PM

+1: succinct. As an addendum, could IT shops please stop supporting this old, buggy, inconsistent browser and prod their users to upgrade to something a bit more sane?

June 9, 2003 7:27 PM

Dear Vendor, Our relationship is now several years old. Could you please stop secretly thinking you're smarter than we are? After all, we hired you, so how stupid could we be? While our reasons for asking for certain features--like support for old, buggy browsers--may not always be perfectly understandable to you, we'd appreciate it if you'd accept our requests, and do your best to fulfill them in the spirit of a mutually-respectful business relationship. Yours sincerely, The Client a.k.a. The One Who Signs The Checks

Adam Kalsey
June 9, 2003 10:22 PM

That's a good point. Perhaps I should clarify a bit. Netscape 4 was released in June 1997, so this is the 6th anniversarry of its release. That's what prompted me to write this, not an actual discussion with a client. In most circumstances the client requests Netscape 4 compatibility only because they have been doing so in the past. Their specs -- and other specs they have read -- have always said Netscape 4 is the minimum browser requirement, but they don't really understand the implications. Except in specific situations, Netscape 4 is used by only 1% of worldwide web surfers. Making a Web application compatible with Netscape 4 requires a significant effort, limits the use of techniques and technologies employed, and may compromise compatibility with up and coming devices like mobile browsers. For general purpose Web sites there is no reasonable business case for providing Netscape 4 support. In fact, the time, money, and effort required to build in and maintain Netscape 4 support could be considered a business risk. Unless your decision to support Netscape 4 is based on real site analytics or user interviews, you are probably making a bad decision. As a consultant, it's my job to help you make good decisions, not blindly implement requests that have no basis in reality.

June 10, 2003 1:49 PM

"In most circumstances the client requests Netscape 4 compatibility only because they have been doing so in the past." Now that's where I think a consultant can add value -- helping the client understand why they should be willing to go without N4 support. Perhaps my knee-jerk reaction is due to recent experience with sites like, which until recently failed to recognize the Gecko browsers like Safari. When visiting their site with Safari, the user was presented with a message that basically said "our site doesn't work with your browser, please upgrade" along with links to MSFT and Netscape. How 1995 was that? At any rate, you're exactly right, the consultant's job is to assist in making good decisions. Point well made.

June 11, 2003 4:45 AM

"But 2% on Netscape, - that's a really big number!" So's 30%, kiddo, and that's what I'm lopping off your bandwidth bill. My number's bigger, bwa ha ha.

June 17, 2003 11:00 PM

What ever you do just don't do those javascript or whatever checks for os and/or browser version... just display what you have, cause I really really really hate the "you're not using IE under windows, this page isn't going to render so please click here to upgrade" pages when I'm using a perfecty compliant browser that *will* render your page properly. Just a personal complaint of mine :)

This discussion has been closed.

Recently Written

Great prodct managers own the outcomes (May 14)
Being a product manager means never having to say, "that's not my job."
Too Big To Fail (Apr 9)
When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.
Go small (Apr 4)
The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.
Start with a Belief (Apr 1)
You can't use data to build products unless you start with a hypothesis.
Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2024 Adam Kalsey.