You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- 2I really like this answer. I think the issue is if you can use the code as a learning point, and then re implement that. I think it's about a 200~ LOC script, so it's not that tricky. I just really wanted to start from a working example for my learnings, and so it seemed to make sense to start from there. If I wrote the whole thing in psudo code and GPL'd my port would that put me in a reasonable position? I really think the title of the post has sparked the debate more than I was expecting.Chris Barry– Chris Barry2011-06-26 14:05:20 +00:00Commented Jun 26, 2011 at 14:05
- Re: sparking debate, consider the nature of the question: a professional dev pours her heart and soul into her craft whether she wants to or not. Hours of my time, buckets of blood sweat and tears because the nature of software is to be a beast. And on top of that, our craft is so difficult that truly excellent contributions to open source (js libs, php frameworks, etc) - at this point, who among us doesn't rely on open source to keep our heads above water, professionally? So this question like this is deeply personal for all of us whether we realize it or not.OpenSorceress– OpenSorceress2011-06-26 19:56:11 +00:00Commented Jun 26, 2011 at 19:56
- That stated, I learned most of what I know from open source wizards like John Reisig and Mark Story and their gang of whiz-kids. JQuery is my little friend. CakePHP is my bread and butter. There is nothing at all wrong with this. Hence the difference between jacking and porting. This is what we're talking about when we say, we stand on the shoulders of giants.OpenSorceress– OpenSorceress2011-06-26 20:03:06 +00:00Commented Jun 26, 2011 at 20:03
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you