The Ethics of Updating for VB3 a VB2 Hack That You Didn't Write

[speedway]

While I see some of the arguments here hold water, not all do. Updating code and releasing it as your own is wrong, definately.

Rewriting and using some of the same coding techniques is unavoidable, there are only so many ways to skin a cat. There is no way that anyone can lay claim to an if-else statement, a SQL statement or much else in the coding department. Complete packages - yes, look-and-feel - yes, the way it is coded - no. We all tend to copy someone else in one form or another throughout our lives - that is called learning by example. Can all the hack producers here honestly say that they did not get some assitance by readin books, looking at others code etc etc. I think not. So lets not be too quick to jump on the copyright bandwagon, especially where software is involved.

Bottom line is - do not claim someone elses work as yours outright if you are re-releasing or updating.