@hap
Grauw has indeed a lot of good information, but information is not by definition knowledge when you dont know how to use it (in my case 
)
The information on that site, combined with a steady codebase / library would increase the possibility to start experimenting.
@hit, I still have some MSX 2 machines left I think there are many MSX (2>) users here that are happy to try out the code.
@eugeny
I'll try not to curse here, but if developers (hard and software) would make their project more open / accessible (thus online) there is a bigger chance that project will be finished and or will inspire others to 'run with the idea's'.
Projectmanagement in the current scene is a bad idea, since everybody is working in their own haste.
Many idea's and projects were not finished due to... time, age, priorities etc. and got lost on old (corrupt) harddrives, disks, paper (tapes?).
As @hit mentioned, the wisdom within these crowds seems to be fading.
@snout
Good to hear there are plans to centralize all the scattered knowledge!
@hap
So if I read all the theory on how to drive a car, I am able to drive a car?
Knowledge = information x experience, attitude and skill
I agree that knowledge take a lot of time to gain, but without proper guidance I would still be a crappy driver. (that's not my reason of not having a driverlicence btw :evil
Of course, spoonfeeding != guidance.
You're missing determination, patience .. and willingness to FAIL epicly. 
but information is not by definition knowledge when you dont know how to use it (in my case )You see, determination here would get you somewhere. Download many technical manuals of MSX components, start your own little library on your harddisk and read stuff through. Google for a random Z80 tutorial, etc.
@hap
So if I read all the theory on how to drive a car, I am able to drive a car?
Yes, that is correct! This does not mean that you won't crash, but if you take the wheel to your own hands and drive to a tree you will learn from your mistakes faster than any guru in this world can ever teach you.
I would not recommend this with a real car, but for example in games this method works very well... Same thing with computer programming... You can't really hurt your self or the computer, so testing, doing all the wrong things etc is actually absolutely best way to learn. Sure you need to get some basic facts straight before you can get started, but after that you just need to hit your head to wall over and over again to become a good programmer. When you find a problem you can't solve your self, you need to ask for help or look for more information.
You can only become quite ok programmer if someone guides you all the time what to do next, but to become really good you have to learn solving your own problems. I think Norakomi is a very good example of this... One day he just wanted to do a sequel to Space Manbow, but he didn't have any idea what to do next or how to program. Then he started reading stuff and asked plenty of questions here in the forums. It actually didn't take even long before we had Manbow 2 in our hands. I also think that I'm pretty good example as an MSX tR programmer. I've learned to do what I want to do, but at the same time I'm also only one of my kind in my country. I must also say that when I started my contacts and documents about MSX were really narrow, but I still managed to write my own programs. Luckily later internet came available also to me and changed all that.
To wrap it up: No, you don't need guidance, you just need to want to do and learn.
