The blog post seems to imply that he came up with the idea and code for Jekyll all by himself. But also as he's a Ruby guy, it's likely he would have ported over the code and concepts to his own project.
The blog post seems to imply that he came up with the idea and code for Jekyll all by himself. But also as he's a Ruby guy, it's likely he would have ported over the code and concepts to his own project.
Start a podcast/educational website on the history of tech.
For anyone who wants to do it together and see if it's a fun project to pursue, email me :) (in my profile)
Or are there already podcasts on it? If so, I haven't seen it appear on HN.
http://www.internethistorypodcast.com/
I'm not aware of anyone successfully doing a more expansive history of tech podcast (and actually filling it out).
Others will claim it was their own work, spice up the wording and build their own personal brand.
Could we refer to these cases as "plagiarism"? It's the proper definition after all. Forking is different as it relates to code, not ideas.
You can see this in almost every discussion about computer science topics.
Look for example how many programmers are shit-talking about Java and they have no clue about certain design decisions back in the day.
Java was the language that made byte compilation and VMs mainstream. Together with XML (another heated topic) it liberated us from unnecessary binary data formats.
And even the language itself was a gift from the programming gods at a time when the most viable programming languages were C, C++, or Perl.
I will forever be thankful to Java for saving me from C++.