On Tue, Apr 8, 2014 at 11:13 PM, Roy Smith <r...@panix.com> wrote: > And the cost of hardware keeps going down, while the cost of > good programmers keeps going up.
Like everything, it's a matter of trade-offs. Spending a moment thinking about what you're doing before you do it might cut your RAM usage by 20% without materially increasing your programmer time cost. But coding everything in C "for efficiency" is almost certainly a bad trade, for the reason quoted. There can be special boundaries in resource consumption. Fitting something inside an Amazon Micro instance might be important for you, in which case you get just 613 MB of RAM (a weird figure, I know). Or maybe you need to stay within 8GB so you can allocate the other 8GB to the database. Or whatever it is. But any time it's flexible (where you basically just pay twice as much to get twice as much), it's usually worth going as far as you can. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
