> Most of GRASS' performance issues arise from the fact that code > simplicity takes precedence over perfomance.
I can't imagine how much faster could be GRASS! I mean, it's faster than most other GIS tools... so if "performance programing" would be mandatory for "core modules" then it would ...flyyyy!!! (?) > Writing optimised code requires a fair amount of effort, and > maintaining optimised code is even worse. Consequently, most of GRASS > is written without even basic optimisations, let alone more extreme > measures such as using a GPU as a co-processor. Thanks for the detailed information ;-)
signature.asc
Description: This is a digitally signed message part
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
