Earlier quoted context omitted.
That doesn't make any sense. The reason regulation is suggested is effect on society, and the effect is the same regardless of the engineer's personal status. An engineer designing bridges is liable regardless of his salary, and same must apply to a programmer. Besides, it's trivial to launder everything if you give such an out. The regulation can apply equally to everyone, or don't expect it to go anywhere at all.
> The reason regulation is suggested is effect on society, and the effect is the same regardless of the engineer's personal status. Amateur programmers are not professional engineers. A profession is an activity people are compensated for. If you're not being compensated, it's not professional work. If it's not professional, you should not be held liable for it. Someone publishing a personal project should not be hel…
Right, it's not the publishing but the use which is proscribed - same applies for engineering. But that would apply regardless of whether the software you're using is open-source or not, and regardless of how much you're paid.
A social-media site operated by an amateur in the bedroom being paid nothing and using only open-source software would still be liable under any sensible and realistic regulation.
>>Besides, it's trivial to launder everything if you give such an out. >That would require companies to not only refuse to compensate their programmers for their labor but to also open source their source code. Doesn't seem trivial to me.
You can compensate for code with this regulation, it's not difficult. e.g. create a non-profit, and pay the non-profit which pays the programmer. So long as the programmer is one step removed from you it's fine.
Open source isn't much of an impediment either, just have a suitably restricted licence. Or don't, it's not an impediment for many types of businesses.