4 ms·
Strictly speaking, as soon as you looked at the GPL code you are tainted. A developer with a good memory will struggly not to pick up code he read through. Afte
by _ph_ 7y ago
Strictly speaking, as soon as you looked at the GPL code you are tainted. A developer with a good memory will struggly not to pick up code he read through. After all, if you are looking at others people code, you are looking at the interesting parts - and if you see a cleverly written function - so anything which is longer as a single expression - you are in risk violating the copyrights of the creator. As I am respecting the works of others, I try to keep legally and morally clean and not just "being caught". So, being a professional programmer, I usually avoid looking at GPL code myself.
- icebraining 7y agoSo do you provide attribution to every MIT/BSD project you look at? Otherwise, you're also in risk of violating the copyright of the creator.
- _ph_ 7y agoNot for code I just looked at. But if I find the MIT/BSD code useful enough that I want to have such a functionality in my program, I would just use the code and give attribution as the license requires. In all the cases, where I not intend to include GPL code in my project, I consider it unethical and legally improper to look at it and then write my own version of such a functionality.