Originally Posted by Matridom
You know, I've done my fair share of programming, and i've always taken upon myself to "idiot" proof the application. That means i make it work no matter what. On average, about 1/4 to 1/2 of my code is to prevent Joe Bloe from doing something stupid, so that means testing it on odd configurations, trying to break it, and in general causing hell for the app to debug it.
Clickhere, since you wrote the program to connect to the internet, you then have to deal with other applications. I'm sure that if i installed NIS and downloaded your application (not that i have nor want either) i'm sure i can figure a way to make it work. Once i know EXACTLY what is causing the issue, i would then take the steps to work around the "supposed" bug in NIS.
I mean, seriously, people get an app, they want it to work, you are responsible for the app. So rather then complain about how Symantec can't get their act together, why don't you reprogram your app to work around the "bug" in NIS, if you can ID the bug, then symantec may be more willing to talk to you. Maybe this "bug" is standard working for NIS and you wrote a bad program?
Either way, you'll be a better programmer for solving the issue and learning hwo to deal with problem then complain about other people doing a piss poor job on theirs.