yeah, a lot of times. i had software licencing responsibilities for a product for a while, and they really didn't want gpl stuff in there for the reasons stated in the thread.
the interesting wrinkle in this situation is: if rossman is distributing all of bambu's code, including the account stuff that far as i can tell is another codebase, and he hasn't gotten it from his own printer (which wouldn't have the sources) then no "agreement" has taken place. if bambu is told to distribute sources and they say "no", they're in the wrong. but if they haven't said anything, then technically rossman is stealing the code. it would most likely get thrown out, but the case can be made.
oh yeah i remember that. pretty sure that was gpl.
this is sort of a predecessor to that situation thus far: bambu is obviously in the wrong with regards to not handing out gpl'ed source, but they are in their full right to refuse handing out stuff they've built on top. so the question then is, is rossman in the clear for having taken their source code? if he has bought one of their printers (most likely) it's pretty cut and dry, but if he took the code from somewhere else he has technically stolen it and the license does not apply. at least that's my read.
what i'm reading from that is that both parties must agree that the work has been conveyed. with the risk of going all sovcit, if the conveyed item is a binary, and the producer does not send the source code to the consumer as instructed by the license, can the consumer really pull the source and distribute it? surely if the license is broken the work falls back on default permissions, e.g. all rights reserved?
maybe my thinking is off then, but in my mind it's mainly for first and second parties? as in, orca and bambu both have to share the source when sharing the binary, not necessarily immediately but on request. anything built on top of gpl code can be closed unless it's agpl. as a third party to all this, can rossman share the code bambu has made on top of orca?
snapmaker has been really nice about that sort of thing. they sent out review units of the u1 early, got roasted, and fixed most of the things people didn't like. i've run mine without any sort of account from the start. you can take it completely offline or run it in "lan mode", and the only things that get more annoying are firmware updates and remote control. you can still do them, there's just a bit more setup.
if you want my opinion (<- see now you can't tell me i'm wrong, it's an opinion) then the difference is that an array is by definition a memory address that's designated as the beginning of an array, and it's got an offset because the first element is at that specific address and further items are offset from that address. so you add the offset to the address to get the nth item. a list, meanwhile, can be basically any implementation under the hood, but it's commonly a linked list. the way you get the nth index there is you count up from the first position. since the implementation is opaque and may be spread out in memory you can't arithmetic your way to an index, you need to follow the pointers.
java's arraylist is a list backed by an array. java's vector is a list backed by a linked list.
yeah, a lot of times. i had software licencing responsibilities for a product for a while, and they really didn't want gpl stuff in there for the reasons stated in the thread.
the interesting wrinkle in this situation is: if rossman is distributing all of bambu's code, including the account stuff that far as i can tell is another codebase, and he hasn't gotten it from his own printer (which wouldn't have the sources) then no "agreement" has taken place. if bambu is told to distribute sources and they say "no", they're in the wrong. but if they haven't said anything, then technically rossman is stealing the code. it would most likely get thrown out, but the case can be made.