2 ms·
And what if what you're doing is just a quick, one month project? Is it likely you must absolutely dig into the sources then? I would say no. The fact is, your
by mherrmann 8y ago
And what if what you're doing is just a quick, one month project? Is it likely you must absolutely dig into the sources then? I would say no. The fact is, your original comment completely fails to address or take into account the context of the individual project. You think you're being reasonable, and of course there are great advantages to open source. I too would prefer this library to be. But the dogmatism and fanaticism is not just offensive to the author who claims elsewhere in the thread that he spent 4 years on this, it's also irrational and leads to suboptimal results.
- Sir_Cmpwn 8y ago>And what if what you're doing is just a quick, one month project? Is it likely you must absolutely dig into the sources then? I would say no. You would be surprised. I can't even count on one hand the number of times I've send a patch upstream within the first 2 hours of using a new dependency. I don't really care how long he spent on it. It was a waste of 4 years if it's just going to be proprietary.
- mherrmann 8y ago> It was a waste of 4 years if it's just going to be proprietary. Dogmatism all over again.
- asddgsgsaxg 8y agoSir_Cmpwn, i too find myself sending drive-by patches after trying out a new package. Don't bother with this hateful guy, you rock!