411 karma · joined September 29, 2011
However, "it's implementation specific and it's most probably this, or that if you use such and such a compiler flag" is different from "I don't know".
As a rule of thumb, don't assume things about C's abstractions, read the standard instead, or ask friendly humans who do if they check out.
Is your prediction that companies will start compiling their UI toolkits for browsers?
would be proprietary software you don't have to reverse engineer
>[AGPL + another] still allows any 'customer' to use your software for commercial work without contributing anything back other than attribution
How so?
Obviously to explain was my exact intention, which is why I provided several arguments to your one.
Honestly, I find your first sentence hard to believe.
You've already shared your opinion on the past tense and I've disagreed. I'll add to that the use of third person instead of the first. Hopefully this will be my last referral to the OC.
I'm simply claiming that it is probable that it was an attempt at manipulation and that my reaction had reason and purpose outweighing it's "harshness".
EDIT: Admittedly I did assert there was a theme.
If you can imagine a more tactful yet still effective alternative deterrent, I'm open to suggestions. I don't believe that just pointing out the fact of the use of the inappropriate tense would have been enough.
While I certainly can be be wrong, I also wasn't assured it wasn't intentional by the way it was explained. I suggest we all mind phrasing and get along this way.
P.S. I don't find it gracious of you to imply that I might be a lying cheat.
Umm no, I handle errors which I expect to be reported to me.