3 ms·
> "oh, it only works if you install in in X directory...". Sure it sucked to read 3000 forum posts and google things for 2 hours, but, once it worked, it worked
by ttt0 6y ago
> "oh, it only works if you install in in X directory...". Sure it sucked to read 3000 forum posts and google things for 2 hours, but, once it worked, it worked.
I had similar problems with proprietary software and I most often ended up with the answer that the thing I want to do just cannot be done. Or sometimes with no answer at all.
I prefer having an option to look up the source code to see what it does, file a bug report or even fix the problem myself than receiving a response "you're an outlier, so we don't care about your problem and there is nothing you can do about it".
- drewzero1 6y agoSo true! No answer, can't be done, or redirected to a sales rep to purchase additional licenses for software that may or may not completely interoperate with the stuff you're already paying them for. Want to write your own program that extends or interfaces with an open-source software package? It can probably be done with some amount of work, depending on documentation, forums, and readability of the (available!) source code. Want to do the same with a proprietary software package? Buy the SDK for $X000, there aren't any forums, and the documentation that is basically eyes-only. Maybe a screen-scaper could work, but that would be unreliable and tie up a licensed terminal (not to mention probably violates the EULA!).