31–40 of 58 posts
Earlier quoted context omitted.
Content on Stack Overflow isn’t technically offered freely. It’s offered under a specific license with specific conditions.
https://stackoverflow.com/help/licensing
They're seriously saying closed source software companies can't use content on Stackoverflow? What if I write a piece of closed source software while consulting SO, is that my own work or a transformed version of the work on SO?
I like how the west is worried about copying/pasting some code and whether that would lead to some obscure licensing issue in the future where lawyers battle it out for 4 years, costing $3M in attorney fees; while some engineer in Shenzhen going off and copying stuff without any worries and infact openly teaching others in his team to learn how to cook some copy pasta. IMO software licensing and patent litigations, a…
The pitchfork entitlement, to my observation, is reactionary to the force of law backing something that should be an individual's responsibility if they want to keep it secret but not supported by the threat of government-sanctioned violence.
Contrast another industry where secrecy is key. A magician never reveals their secrets, and there's material value in being able to pull off a trick that nobody else can. But what's the ramification if somebody figures a trick out and publishes it? It certainly isn't a crime. The worst of person might face is sanction from a magician's guild.
Given that we have a world where somebody can be sued for taking apart a physical artifact that they own and discovering secrets of its implementation, sharing those secrets, and modifying the thing based on knowledge of those secrets, the pitchforks are somewhat understandable.
I think I might have a few hundred copies of: ``` # From https://stackoverflow.com/a/246128 DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )" ```
I think shell is the most plagiarized code in existence. So many sysadmins have rudimentary skills and simply copy what works. I have seen some folks with huge repos of code snippets like that
DIR=$(dirname $(readlink -f $0))
I started using the longer one, and then I gave up on shell scripting on OS X for other reasons, and didn't go back. So yeah there is a lot of random cargo culting.
In Oil I hope to provide an even simpler method that's built in (and it also has readlink builtin to support this)
I like how the west is worried about copying/pasting some code and whether that would lead to some obscure licensing issue in the future where lawyers battle it out for 4 years, costing $3M in attorney fees; while some engineer in Shenzhen going off and copying stuff without any worries and infact openly teaching others in his team to learn how to cook some copy pasta. IMO software licensing and patent litigations, a…
I like how the west is worried about copying/pasting some code and whether that would lead to some obscure licensing issue in the future where lawyers battle it out for 4 years, costing $3M in attorney fees; while some engineer in Shenzhen going off and copying stuff without any worries and infact openly teaching others in his team to learn how to cook some copy pasta. IMO software licensing and patent litigations, a…
> Not everyone is interested in open sourcing their work - but somehow that's looked down upon. Why!? It is their work and respect it, there are so many people with pitch fork entitlement. The pitchfork entitlement, to my observation, is reactionary to the force of law backing something that should be an individual's responsibility if they want to keep it secret but not supported by the threat of government-sanctione…
Often times reverse engineering is harder than building the damn thing in the first place.
Earlier quoted context omitted.
I think shell is the most plagiarized code in existence. So many sysadmins have rudimentary skills and simply copy what works. I have seen some folks with huge repos of code snippets like that
For sure, and the funny thing is that it can be replaced often by replaced by the simpler and more readable DIR=$(dirname $(readlink -f $0)) However OS X doesn't have readlink, so the longer BASH_SOURCE thing makes sense there. I started using the longer one, and then I gave up on shell scripting on OS X for other reasons, and didn't go back. So yeah there is a lot of random cargo culting. In Oil I hope to provide an…
I like how the west is worried about copying/pasting some code and whether that would lead to some obscure licensing issue in the future where lawyers battle it out for 4 years, costing $3M in attorney fees; while some engineer in Shenzhen going off and copying stuff without any worries and infact openly teaching others in his team to learn how to cook some copy pasta. IMO software licensing and patent litigations, a…
I like how the west is worried about copying/pasting some code and whether that would lead to some obscure licensing issue in the future where lawyers battle it out for 4 years, costing $3M in attorney fees; while some engineer in Shenzhen going off and copying stuff without any worries and infact openly teaching others in his team to learn how to cook some copy pasta. IMO software licensing and patent litigations, a…
Will this lead to huge, science-fiction-like conglomerates? Within a company, there are no licensing restrictions. So copying code, or other media like videos or pictures, stops being an issue.
I like how the west is worried about copying/pasting some code and whether that would lead to some obscure licensing issue in the future where lawyers battle it out for 4 years, costing $3M in attorney fees; while some engineer in Shenzhen going off and copying stuff without any worries and infact openly teaching others in his team to learn how to cook some copy pasta. IMO software licensing and patent litigations, a…
I had a similar philosophy in my youth, and it still resonates with me. Hanging around Slashdot and doing oss development, I learned enough about IP law to understand that it's not as simple as we'd like.
There's actually a risk that your unlicensed code will be picked up by somebody in a jurisdiction with different IP laws than you're familiar with. They can copyright the code (did you say "free for any use or modification?), and issue C&D to anybody hosting your code online. You could find yourself in a very awkward position where you published it first but they've done so in a legally defensible manner. CC0 and MIT are prudent licenses -- not to ensure that you get credit, but to cover your own ass.
I like how the west is worried about copying/pasting some code and whether that would lead to some obscure licensing issue in the future where lawyers battle it out for 4 years, costing $3M in attorney fees; while some engineer in Shenzhen going off and copying stuff without any worries and infact openly teaching others in his team to learn how to cook some copy pasta. IMO software licensing and patent litigations, a…