5 ms·
I was extremely happy to see this as I have been trying to find a single-threaded memory allocator (one which doesn't have any reliance on any form of threading
by saurik 9y ago
I was extremely happy to see this as I have been trying to find a single-threaded memory allocator (one which doesn't have any reliance on any form of threading primitives that I simply don't have on the platform I am dealing with, which I point out to make clear that I am not looking for this due to any delusion about performance), but since this doesn't have a license on the code it is essentially useless :(.
- jstimpfle 9y agoI don't think we need license stickers on each little piece of code (not trying to belittle OP's work). Why don't you just read and understand it and make your own? It's just 200 lines. You can then also much more easily adapt and extend. EDIT: I know it breaks the guidelines in multiple ways, and I'm past the age where I should care, but * * * * you downvoters. This is a reasonable comment, and if you disagree give some argument.
- saurik 9y agoI don't do that for the same reason no one should do that: because if I read this code and then write my own code that uses the same techniques and structure due to my having read this code, it will be a derived work of this code, but this code is not under a license that allows me to do that. The legal reality is that yes: if you want to write code that other people are to be using or reading you do need to put "license stickers on each little piece of code"; this is sadly a big problem with hackathons and classes that encourage people to put stuff haphazardly on GitHub because "yay open source" without teaching people enough about copyright to make that worthwhile.
- jstimpfle 9y agoBe sure that this is how OP made his code himself... And that you can easily find other code that your work is "derived" of, even if you did it completely on your own with only basic ideas from wikipedia. Of course, check back with your lawyer if you're that concerned. But nobody wants to live in a world where you can't make your own 200 lines of code based on ideas found somewhere else (ideas which are not owned by anybody).
- saurik 9y agoThe legal reality of copyright is that the color of the bits matters: unlike with a patent, if you independently somehow manage to come to a similar result and can prove that, you are supposed to be fine (though there was one devastating ruling with respect to photographs that I think most people consider to have been a mistake that may lend some precedent to such an argument, I think you would still have a difficult time pulling it off). This just isn't about the world in which I want to live: it is about the world in which I actually live.
- jstimpfle 9y ago> This just isn't about the world in which I want to live: it is about the world in which I actually live. Based on your own arguments, I think you are theoreticizing. It's also your own decision in what world you live. I would not want to spend my time this way. But again, your own decision. (It would be of course a nice gesture to drop the author a thank you, or whatever)
- saurik 9y agoDo you seriously believe that you can ignore laws by simply deciding to live in a world where they somehow don't apply? FWIW, if you want a reference for "even with seemingly no causality a related work was classified as a derivative work for copyright", here is the particular case: https://en.m.wikipedia.org/wiki/Temple_Island_Collections_Ltd_v_New_English_Teas_Ltd https://en.m.wikipedia.org/wiki/Temple_Island_Collections_Lt...
- jstimpfle 9y agoNo, as I said I think you are theoreticizing. Why are you not asking me whether I avoid leaving my house just because there could be some crazy guy shooting at me? Here's why I still leave my house most days. My life would not be worth living. I have a moral right to leave my house. I have good faith in the state to protect this right, although I know some people have indeed been shot (even by policemen!). It's not worth my time theoreticizing about this possibility. Note that the situation is different if you move to advanced engineering projects and parties involved with huge amounts of money. The possibility of a mean-spirited lawsuit there is a lot more realistic (while probably still as unrealistic as batshit crazy).
- katastic 9y agoDo you make sure to never copy code from Stack Overflow because the submissions may be copied from somewhere else?
- saurik 9y agoI definitely do not copy code from Stack Overflow that is more complex than a line or two (and so will be under the deminimus threshold for copyright); are you?
- bonzini 9y agoNo, if you write your own code it is _not_ a derived work of this. Copyright is not on the idea ("use this or that data structure"), only on the expression.
- cellularmitosis 9y agoIf that were true, then why are "clean room implementations" a thing?
- vidarh 9y agoBecause in a lot of cases the most logical expression of a given idea in tech will be quite similar, and in that case having clear documentation that shows that your implementation is an independent expression of a description may help prevent allegations that you just copied someone elses code and changed it a bit.
- copperx 9y agoThat sounds reasonable, but why are Wine developers and the like discouraged from looking at the original source code they're trying to emulate?
- bonzini 9y agoBecause that source code is not supposed to be publicly available (in the case of Wine and ReactOS).
- saurik 9y agoThat just means it was copied without permission... like this code, which is by default All Rights Reserved. For maybe more on-topic examples, though, note companies that are very careful about employees looking at open source code.
- bonzini 9y agoWhile this code is "all rights reserved", you do have the right to view it according to the GitHub terms of service. This is not true for Windows. Alleging that Wine authors have participated in illegal sharing of source code would be a powerful accusation, and the authors clearly want to avoid it.
- deleted 9y ago[deleted]
- yxhuvud 9y agoDid you consider opening an issue about it?