News for hackers. Stuff that matters.

A comment on Memory use in CPython and MicroPython. Parent comment

Re:Memory use in CPython and MicroPython by bramblerose on Sunday July 02, 2017 @04:07AM (#14681457)
Why would "makes your code run 1% faster" be a better sell than "saves you 1% development time by reducing the number of bugs"?
[ Parent | on HN ]
Re:Memory use in CPython and MicroPython by egwor on Sunday July 02, 2017 @04:18AM (#14681482)
That tends to be a more difficult sell because the counter-argument from further up is 'But we're not seeing those bugs right now, and won't we find bugs when we do this upgrade?'
[ Parent | on HN ]
Re:Memory use in CPython and MicroPython by snovv_crash on Sunday July 02, 2017 @05:00AM (#14681599)
It depends on a) the size of your deployment b) whether you are paying SV salaries to your developers c) how sensitive you are to speed.

In many things I'd be happy to double the number of bugs if it meant I could run the code twice as fast. Bugs can be fixed. Slow code is still slow.

[ Parent | on HN ]
Re:Memory use in CPython and MicroPython by netheril96 on Sunday July 02, 2017 @07:24AM (#14682025)
Because during the upgrade you would have an explosion of bugs and therefore development time fixing them. The 1% saved by purity wouldn't make a dent.
[ Parent | on HN ]