So long as we are all wrong. Java is for managers who are insecure about there ability to manage highly trained C programmers so they get together and with elitest academians and design some dingo language to try to get a set of cut rate cogs they can fit in their machines, and expect C programmers to do memory allocation for their dozens of Fred Foobar programmers through a crummy API.
Stay in the sand box. -Robin On 6/15/07, Dave Dyer <[EMAIL PROTECTED]> wrote:
> >So if there was any language which allows a programmer to port their code to be compileable and executable on a wide variety of systems it is C. > Java and C support two fundamentally different approaches to portability. The approach that C supports is "chaos: deal with it". Figure out exactly what platform you're dealing with, compile code accordingly. You end up with godawful kludges like "configure". It can work, but it requires constant maintenance to keep up with the latest twists in the "compatible" environments. Java's aproach is to define a virtual machine, and implement it faithfully on each platform. Java programs run the same everwhere; they don't know what OS or CPU they're running on. The same kind of approach is used to virtualize for whole platforms - I can also run linux or windows on my intel mac. I can run my old PDP10 system in a window on my PC (and incidentally, MUCH faster than it ever ran on real hardware) Both approaches suffer from not offering access to useful (but not modeled) aspects of the targeted platform. _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
_______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
