On Fri, Apr 06, 2012 at 10:45:30AM +0200, Chusslove Illich wrote: > > [: Oswald Buddenhagen :] > > even small inefficiencies add up, so a functionally equivalent but > > more efficient solution is generally preferable. > > You have got to be kidding me. [...] > if you consistently apply this attitude to "small things", you easily waste 10% code size (or performance in other cases) *for no good reason at all*. this may not sound like a lot, but may be the difference between make or break on an embedded device. it's a mindset thing: "we optimize, bacause we can", rather than "we ignore it, because we can (usually)".
- RFC: i18n: strict translation call-to-catalog mapping Chusslove Illich
- Re: RFC: i18n: strict translation call-to-catalog ... Albert Astals Cid
- Re: RFC: i18n: strict translation call-to-cata... Chusslove Illich
- Re: RFC: i18n: strict translation call-to-catalog ... Thomas Zander
- Re: RFC: i18n: strict translation call-to-cata... Chusslove Illich
- Re: RFC: i18n: strict translation call-to-... Thomas Zander
- Re: RFC: i18n: strict translation call... Oswald Buddenhagen
- Re: RFC: i18n: strict translation... Chusslove Illich
- Re: RFC: i18n: strict transla... Oswald Buddenhagen
- Re: RFC: i18n: strict tra... Chusslove Illich
- Re: RFC: i18n: strict tra... Oswald Buddenhagen
- Re: RFC: i18n: strict translation... Thomas Zander
- Re: RFC: i18n: strict transla... Chusslove Illich
- Re: RFC: i18n: strict tra... Thomas Zander
