On 2/17/17, 3:22 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> wrote:
>2017-02-16 23:34 GMT+01:00 Harbs <harbs.li...@gmail.com>: > >> > Well, that's not PAYG (yes, I'm being picky). >> >> I disagree. For string it certainly is PAYG. There’s no extra cost. (and >> considering the three bytes of ‘=“”’ in the source code is getting petty >> IMO) Adding an extra TextModelWithEmptyStringDefaults is totally >> unnecessary. >> >> >+1 > >and right that Array or Object are other kind of problem but usually use >to >be defaulted to null and in that cases programmer needs to make a special >code to handle. But Strings and Numbers....it's clear for me that should >has a default when needed since is more cost to handle it in other way. >It's like an exception on the rule of PAYG. > Lots of little bits of code add up to something. If you want proof, go look at the Flex UIComponent. Please, let's stick with PAYG and make just-in-case code optional. It is simple enough to swap in a different model with defaults. Otherwise, please allow me to inject 1000 extra assignment statements in each application. I really don't think we want that. My 2 cents, -Alex
