Daniel Barreiro

Please, don't add Y.Model to Mojito as it is. It has several architectural shortcomings and it would be a bad thing if those propagated to Mojito. - It mixes data...

As a proof of the bad design of Y.Model allow me to point to the following methods of Y.Model itself, which are originally defined in Attribute (or one of its...

All the attribute issues would have been avoided if data and meta data had been split from the start. If you look at my gallery-md-model, it has a 'coalesced' data...

Have I mentioned performance? Y.Model is based on Backbone.Model. Both have a get method. This is the original 'get' method of Backbone: https://github.com/documentcloud/backbone/blob/master/backbone.js#L236 This is my getValue method, which is...

Whatever you show in the examples and tutorials is what developers will end up using. Implicitly and in the minds of most people learning Mojito, you would be endorsing Y.Model....

@focuzz I don't want Mojito samples with my custom Model. My goal was to show the design errors in Y.Model and have those fixed in Y.Model itself and, to do...

I installed that one but the sample files made no sense to me. I wasn't sure which parts were optional, how could I do simple stuff and only late grow...

You can see it at work in Facebook's own [prop-types](https://github.com/facebook/prop-types/blob/master/index.js#L8) where the whole code for the property checker is enclosed in an `if (process.env.NODE_ENV !== 'production') {` block. In that...

It is the best way to provide them without concern as to how they may affect the performance/size of the end product. With this trick, they will be gone. As...