Basically I want to make it completely free to use for whatever purpose, commercial or otherwise, only thing I ask for is credit, so they can't say they built it, in their license somewhere it would have to say "build on yadda ydadda".
The basic requirements that you described are probably met by either Apache2 or BSD. Others like GPL meet your requirements but add other requirements as well (eg derivative works must be open as well).
Often times licensing can become a religious debate. Read the major ones and choose the one that is best for you.
That's if i'm remembering licensing conventions correctly.
1. Programmer hostile. For the most part, the people who can make money off GPL licensed software are system administrators, people selling support and training, and so forth. If you are a developer and try to use the software, you better be careful with how you use it.
2. Riddled with nonsensical legal fiction. The limits regarding linking are arbitrary. What about "linking" with the software by using its output with pipes, speaking to it over sockets, and so on?
3. A poor choice for people who love open source. Are you an author who creates open source software, and you want to link your software with a library written in GPL? Careful, or the GPL monster will eat you and make your code GPL too.
My own hate of the GPL aside, the main thing to take away is that it doesn't fit OP. People who create software can pick whatever license they wish, and I respect that. I just reserve the right to despise the GPL.
OP, perhaps the ISC (http://en.wikipedia.org/wiki/ISC_license)? It is BSD style and keeps it to a minimum.