No so sure given they have functionally only just got to a release candidate stage with V4 That will depend on if they learn from this experience or just continue to try and cover it up. Unfortunately I am not at all confident they will learn so expect them to make the same mistake again next time.
Unless another company takes over nod32, I doubt it. Been using nod for about 10 years, and the motivation behind making the product has quite obviously changed as it's got so popular. That being said, a lot of products start to look less appealing when they become popular. I blame business though, so many business networks buying, ESET starts getting rich, motivation changes. The most obvious and notable recent event is as you've stated, version 4. v4 was rushed out to release for the CeBit marketing event when it was still in beta 1, ofcourse they tried to cover that up by releasing a RC close to the event, but the fact that the release version was beta 1 code kinda buggered them there. I've recently been switching 14.5 networks away from ESET, but I doubt I'll manage to tear away completely and leave 1 network on it to see how they go. I'll look forward to checking out v5 when it's out.
It's good to remember that not all users are having problems at this point. Since a specific support question wasn't posted in this thread, it is closed.