[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GEM/X

====================================
X is a nice ideal, but it's barely practical on a TT, let alone a Falcon
or <gasp> an ST.  GEM is sleek.  GEM is pretty weak too, but that's what
you get in exchange for speed.
====================================

What about NeXT ?  X uses by far the most CPU resources, and GEM the least,
so what about something in between .. like the NeXT GUI?  It could be
simulated either by adding to GEM, or rewrite GEM to call NeXT-like objects.