Good points in this article. Note as well that the LGPL requires you to permit reverse-engineering of your proprietary code. There are good reasons for this, bu

Good points in this article. Note as well that the LGPL requires you to permit reverse-engineering of your proprietary code. There are good reasons for this, but it's unrealistic in a lot of organizations. A lot of developers (and a lot of lawyers!) rely on the rule of thumb that you're fine under the LGPL as you don't modify and don't statically link. That's a fine rule of thumb, but that's all it is.