Those who know their history know MSX was born from the chaotic wildgrowth of homecomputers with no compatibility between them.



Now, a similar (and even worse) wildgrowth can be seen in the mobile phone and PDA markets. Hardware Abstraction Layers like Windows CE and DirectX offers are not the answer. And even in HAL's there's already a wildgrowth too!



I think a new MSX specification can do today what MSX did 20 years ago: bring order to chaos.

Yes, but isnt that just what MSX-A wants? To be able to (standard) communicate through different platforms? I think they can do that they once did. MSX was a very good example of how a standard works. They can do it again!

Abolutely. the MSX community was able to remain active until now, because of the standard. The current 'alternatives' have two major drawbacks



- You need drivers to create some sort of standard

- There are many many many many legacy limitations



Standardization is what MSX Association wants (and should want) indeed

Quote:

Yes, but isnt that just what MSX-A wants? To be able to (standard) communicate through different platforms? I think they can do that they once did. MSX was a very good example of how a standard works. They can do it again!

Internet has become sort of a standard. Only things you would need to do to communicate through different platforms with MSX is to put it online and work on internet clients/servers for MSX.

Quote:

Abolutely. the MSX community was able to remain active until now, because of the standard. The current 'alternatives' have two major drawbacks - You need drivers to create some sort of standard - There are many many many many legacy limitations Standardization is what MSX Association wants (and should want) indeed

I can only agree with snout here. IMHO MSX should stay a standard as it was launched from the very beginning. With as little extra stuff like drivers (to make something a standard) as possible.

Of course, with the FPGA, you are free to create your own litte standards