To say I don’t like when this happens would be __UNDER_STATEMENT__. You’ve been there before… your random open-source app crashes, it bugs you enough where you go ahead fetch the source, compile it, track down the dependencies for 1 hour… finally compile it; now your read to fire up the gdb, after about 5 minutes it’s crystal clear why your app crashes (null pointer? unallocated memory?) your like wow, that was simple.
AND THEN IT DOWNS on you… you would have to spend like a day figuring out the code base to do it the “proper way.” It took you long enough to get to this point — you really deserve that break after all you tracked the bug down — so you go grab a glass of wine (insert preferred beverage of choice here, or smoke break). So now you got your beverage in your hand, so you pop in a your favorite dvd and you’ll watch the first 10 minutes while you enjoy your drink (or read your favorite news feed)… Right, 2 hours later it’s time to do something else &| sleep.
Next time you have the app crash you can feel the pain travel thought your body. The very same pain you felt when you figured out that the simple error doesn’t have such a simple fix (at least to you). So what do you do, you do what any other self-respecting open-source user does you go onto good and find another OSS application that does the same exact task and hope it doesn’t crash.
It hurts, because it’s true.
Post a Comment