wrongu wrote:To Ravener96, start chatting on IRC. Fork code, read it, mess with it. If you don't know C++, this is an opportunity to learn it, not a prohibitive barrier.
Regarding C as the language, it certainly can't be interpreted or compiled on the server. What's more likely is that the community will come up with their own simple C "compiler" that will output to Trillek (RS3200 or DCPU) assembly. I imagine that a best-practices protocol will emerge for interfacing with hardware, and someone more clever than I will write a "dcpu.h" or "rs3200.h" header-library for standard assembly I/O functions for things like thrusters/shields/other standard fare. In other words: C compilation can be done client-side, and probably in a separate program/IDE (at least to start).
ok, c as a native langage of our dcpu has been rejected (and rightly so). abstracting hardware a little is something we are probbably going to do to some extent as simulating the entire computer is quite exessive. cables for example i imagine will work by transfering data from divica a to divice b, my original question were mainly about how far we would take this simplifying of hardware to increase usability. the cpu would for example be able to pull data from the different ports directly if we dont have to think about the internals of the computer. if we take it one further it could pull data straight from the floppy reader without thinking about ports. one further it could find data on the floppy without thinking about the data placement on the floppy.
some of this is probbably incorrect but i think you get the point.