5 Things I you might like to to see in the future.
1) stack-duino, why no stack 2 or 4 of them up on one another/but that would involve a peave of mine, a power pin that's not there.
Why would you want 2 or 4 arduinos stacked together? What would be the purpose? More programming memory? You'd have to spend a fair bit of that on a protocol to interface all 2 or 4 of them. Why not have them spread around or using a Mega board?
2) Higher level programing, the bottom line does it work, I have seen some really bad code that works really well and that's what counts.
Don't give me your mumbo jumbo about clock speed, If that's the most important thing for you, you be writing in machine language not C
I think you are looking at it the wrong way. Clock speed and memory size are the most important things... and for that matter writing in C/Assembly is the best approach. You are not writing programs in C when you use the Arduino... it's C++ and the overhead that it causes can be seen in almost all the libraries. So if you want to use a higher level language, why not using a raspberry Pi or a beagle board?
3) As the prices come down maybe integrate some WIFI, and multi-core processing.
Why do you need multicore processing? Are you ready to write libraries for that kind of processor?
Wi-fi would be nice... but then again, with such short memory, it's not a must have.
4) Plugs....those pins suck long term they fall out.
Not sure what you mean here... the USB B plug should disappear though.
5) Can some one write a good programing manual that's complete, we got them out there missing tons of info.
Again, you are looking at this the wrong way. If you program in C with the AVR-GCC, all the information you need is there for you to use. If you use third party libraries (like pretty much everything), then I guess you have to ask the third party for documentation. But, and this is the best part, if you really need to see what a library does, you can open its files and see for yourself.