[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(FC-Devel) AFL 5: thin clients
architecture + feature list part 5
> Hoever Argo is no "thin client" by any means. Argo will probably
> always be a memory and CPU hog.
Maybe we could relax on that requirement and not demand
thin-client ability for every task and apply some
contingency here. Simply model/code browsing (any supported
language, not just java) for instance should not need such
a hog, whereas debugging might.
> Luckily memory and CPU time are cheap
> and plentiful. Some of the best features of Argo come from its
> relatively tight integration of model with analysis, model with code
> generation, and model with reverse engineering.