|
AGGGGGGGGGGGGGH! Honestly, these conversations are getting absurd. No offense, Doug, but by your definition even Windows doesn't have a native GUI; it requires a graphics controller to render the graphics. And most Unix machines use some sort of X-Windows approach, which is a non-graphical data stream being rendered by a very intelligent workstation or PC. Unless your primary CPU is actually calculating the position and RGB values of each pixel of your graphical device, it's not really a native GUI. And the point is that we don't WANT our primary CPUs doing that stuff; it's a waste of precious processing power. Instead, we want to send terse but robust GDL commands to a processor that actually renders the data. And whether this is a micro-language like those used by the graphics cards drivers or a high-level definition language descended from XML, it's all the same thing: you don't paint screens with your business CPU. But this is common sense. Joe > From: Doug Hart > > It can be argued that the System i5 still can't do GUI even with HATS , > etc.. > We still need a GUI enabled client (OS) to display a graphic interface. > When I can do a native VNC connect to the system and see GUI then it's > there.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.