Originally posted by asdf

---

I know what you mean, Hyperhacker. Java often freezes my computer up completely. Other things do it too, but it seems to do it more often than what would be considered tolerable. That's why I tend to stay away from it.

---

Originally posted by Kyoufu Kawa

---

HyperHacker fails at grammar

---

• Re-inventing the wheel. Program X is a very complicated program that took years to develop, and has a nasty bug/lacks feature Y/doesn't run on operating system Z and is no longer in development/etc. With the source code you can just add or fix things and there you go. Without it you have to code the whole thing over again. FCEUXDSP is a great example. I doubt many people would have been willing to write an entire emulator just to add debugging features, and even if they did, it probably wouldn't be as good as FCEU for quite some time.
  
• Source > Documentation. Some people just suck at documentation. It also takes longer to write it after you've already written the code. Well-commented code is documentation. Also, you can't possibly document everything. Your own FZX editor is a great example. Since it's a 3D editor I can assume it does things like translate up/down/left/right/forward/backward camera movements into axis movements. I've never managed to get this working and there doesn't seem to be one single piece of documentation on Google (it's all about doing similar things that work totally different). If your program does indeed do this, and I have its source, I can just look at how you did it to get an idea of how it works. On the other hand, if you just release documentation, I think it's a safe bet that if I'd never said this, the documentation wouldn't contain any such information, because it's not information about FZX.
  
• Learning. People see your code and point out ways you can fix/improve things. You learn from what other people tell you about your code. Heck, maybe some random person points out how to fix that annoying bug all your programs have that you could never figure out. Just look at Linux, most bugs in it are found by hundreds if not thousands of people testing it, finding a problem, and looking at the code to see what causes it. Now imagine trying to debug a closed-source Linux by yourself, without this input. Not something I'd want to do.
  
• Portability. You can easily port code written in most any language if you have its source. You've used Sappy as an example of how this isn't true, but I disagree. Writing a C++ clone using only documentation of the music format would almost have to be a lot harder than basing it on the original VB6 code. In fact a few regular expressions can turn large amounts of VB6 code into working C++ code. Again, quality of documentation is another issue. A single typo may go unnoticed until you get to implementing that part and can't figure out why it refuses to work. A typo in the source code should be found pretty quick.
  
• Helping others. You've just written a large piece of code, and it was a huge pain. Wouldn't it be nice if other people could just use that code instead of having to go through the same experience?

Originally posted by Koitenshin

---

I don't read posts, and editing quotes is totally hilarious, not lame at all.

---