Because you don't know what's lurking and waiting for you X-periods of time from now. Sure, it works now and that's probably all that matters for most. Others like reliable solutions that won't just up and corrupt themselves at some point.

However, I've often been amazed at how "messy" code is. Code that does what it needs to, and works. Early bird get's the worm, and I applaud this guy for throwing something out (something perhaps that we were too busy taking our time "working on to get clean and perfect"). I'm sure it'll get refined and refactored as time goes by, if people latch on.

Have you ever heard the catch-phrase, "What could POSSIBLY go wrong?" before?

Many have been burned by PHP experts before. This guy is a beginner. I really like the app design and idea but I can't find a reason to let protect my data or compromise my server. Might be cute to host it inside my firewall, though.

I care. As I am a developer I like to understand what the code does. If they would refactor this project to use 3-4 classes and a coherent structure it would make their code easier to overview and maintain. I prefer the mix of a beautiful UI, a meaningful UX and a powerful codebase.

If it works but performs poorly due to poor design decisions I definitely care. Otherwise I'm with you -- I tend not to care about the skill level of the programmer as long as the application works and has no glaring security issues.

> If it works

That would be the question. Is it bugfree, or will it eat my data and let scriptkiddies run amok on my host?