3 ms·
building a "standard graphics library" into a language that is not part of a write once run anywhere managed environment is a terrible idea and has never worked
by easytiger 14y ago
building a "standard graphics library" into a language that is not part of a write once run anywhere managed environment is a terrible idea and has never worked.
On the other hand a more solid native 2d drawing library like java2d would be more welcome.
Weekend project #34532
- deleted 14y ago[deleted]
- easytiger 14y ago> "write once run anywhere managed environment" that is not even remotely what that is. A sufficiently advanced graphics library will do considerable amounts of non trivial interaction with system dependent and even hardware dependent libraries. The parent cited SDL. Which sits atop other libraries. Which imposes certain runtime constraints.
- laumars 14y agoYou're now talking specifically about SDL, where as I was commenting about your generalisation about Go as a language (which was the context of your previous comment). I'd already said Go lacks any kind of standard graphics library and never tried to argue otherwise. But the standard packages that are included with Go's SDK are cross platform. I can (and frequently do) write Go applications using just the standard libraries that I then run on different platforms (both in terms of OS and CPU architecture) without any code changes what-so-ever. Anyhow, even that being my point, I don't agree with it myself. Thinking properly about it, Go's base packages are little more equivalent to ANSI C than JRE; Go isn't managed and thus base packages are really just a set of standard libraries rather than a runtime environment.