Group: Forum Members
Posts: 2,
Visits: 3
|
The problem is that LVP is jolly useful! One tends to orgnanise ones processes around it, rather than vice versa, so suddenly missing it would mean onward costs in time and money to get back to a working state. Or, more likely, a different working state. You are not holding data hostage, but imagine if you had a system crash and Windows stopped working. Your only choice is to use Linux or pay a costly support fee - they are not holding your data hostage either but it would be a serious disruption. How about your dev tools? Maybe on a new PC you have to buy Visual Studio all over again to get back to work. It's not what you want to do at that time, and another issue is that you forget, so it comes as a surprise just when you fire it up to use it for something.
Being dead useful to me is actually a bad selling point in this situation. I know I'm going to get bitten at some point, and the more useful it is the more pain that will cause. So I am encouraged to find a solution that doesn't have that upcoming pain associated with it. LVP is really very good and I appreciate the time we spent early on in fine tuning it. With any other app I would be perfectly satisfied with what it does for me, but I am actively looking at other log viewers. I am considering if my processes really need to be the way they are, if I can achieve a similar end, perhaps a bit less easily, with a different app.
|