3 ms·
Because its a broad enough space, on the programmer and user sides, that there's not going to be One True Standard that works well enough for everybody. Not ev
by h2odragon 7y ago
Because its a broad enough space, on the programmer and user sides, that there's not going to be One True Standard that works well enough for everybody.
Not everyone thinks the same way, and UI is close enough to "how the user thinks" that you've got to cater to the differences. Some people and situations need UI concepts that don't belong in the toolkit (dump ram to framebuffer for debugging by color); other users should have controls that have minimal effects and those controls wrapped in foam so they don't hurt themselves any more than necessary.
That breadth of "UI" is barely covered by the boiling chaos of interface ideas we're still watching evolve.
- tabtab 7y agoRe: not going to be One True Standard that works well enough for everybody. One could say that about anything, yet we have HTML, SQL, etc. as standards, despite their limits and imperfections. Oracle Forms allowed a single client to handle multiple different applications. I don't know how it worked under the hood (it's proprietary), but it had characteristics of a "GUI browser" and at least got the job done. It shows one "GUI client" can serve multiple server-centric CRUD apps without local per-app installs. Focus on data-centric CRUD first. Things like word processors, flow-chart editors, and Photoshop clones can wait for a later stage or level. Walk before you run. Some reference the X-Window system, but it's pixel-based, not vector, and has no input buffering feature, meaning every key-stroke has to make a round trip from client to server before it shows up on the screen. This was okay on LAN's, but questionable over HTTP.