zlacker

>>belter+(OP)
Isn’t “rewrite the example code in your own style” accepted best practice for human coders, when working from an example that does what you need?

I’m not sure what would be acceptable output for a code generation tool if rewriting the examples isn’t ok and reimplementing something that performs the same function still isn’t ok. Are we automatically granting de-facto code patents on all published code now?

>>taneq+he
The point here is that this isn't some example from a textbook or even stack overflow, but licensed pieces of work with all the legal complications that come with that. This is about the potential use of this code in proprietary code (or code otherwise incompatible with the original licenses), and I really don't think anyone would say it is "accepted best practice" to copy out someone else's work you find online, licenses be damned, in a professional setting.

>>l__l+Wg
No, you're missing the point.

There are two worlds.

In one, everytime someone publishes code with a license attached, they've taken a chunk out of the set of valid lines of software capable of being permissibly written without license encumberance. This is the world the poster you are replying to is imagining we're headed toward, and this case basically does a fantastic job of laying a test case/precedent for.

The other world, is one where everyone accepts all programming code is math, and copyrighting things is like erecting artificial barriers to facilitate information asymmetry. I.e. trying to own 2 + 2. In this second hypothetical world, we summarily reject IP as a thing.

The 2nd world is what I'd rather live in, as the first truly feels more and more like hell to me. However, given the first one is the world we're in, I'd like to see the mental gymnastics employed to undermine Microsoft's original software philosophy.

EDIT: Voir dire will be a hoot. Any wagers on how many software people make it onto the jury if any?

>>salawa+Fj
in many cases a snip;routine;proc...whatever you work with, is rote procedure. such as device access. ie retrieving a directory listing.

code that reverts to a conserved sequence of bytes interchanged ,no functional variations.

code that is so common knowledge it has become street graffiti, belongs in world 2

versus code that creates a functionality not available by direct command, is innovative and should be attributed. this sounds like what 1st world should be.

>>rolph+5n
That’s not actually how it works. Purely functional code, such as code that it written in a certain way to achieve maximum performance, is not deemed expressive and therefore not covered by copyright. This code would be covered by patent.

>>willia+Bp
i think we are actually talking about the same thing.

in simpl terms:

mov bax eax ; an obvious function; no IP

mov eax eax ; seems useless unless you know what de-referencing is. probably IP

this is of course example not considering granularities at level of patents on a language, or macro directives