hueyp

7 ms·

31.
by hueyp 14y ago
speculators. http://en.wikipedia.org/wiki/Tulip_mania
32.
by hueyp 14y ago
Because you need to know what events you care about. If instead you declaratively define the state of a component via a shared model then you don't have to care how something was updated, just that it was. Any new way you come up with muta
33.
by hueyp 14y ago
> It's agnostic to ... if you render your HTML on the client or the server I love Angular, but if you are rendering server side HTML (either as partials, or bootstrapping a page) it is currently lacking.
34.
by hueyp 14y ago
Thanks, I was honestly confused, not trying to nit pick. --- Anyone know the best way to make it so set defaults to {validate:true}? Override Backbone.Model.set, extend options and call original?
35.
by hueyp 14y ago
From the changelog: > Model validation is now only enforced by default in Model#save and no longer enforced by default upon construction or in Model#set, unless the {validate:true} option is passed. From the documentation on Model#set:
36.
by hueyp 14y ago
And from the comment above: "...but because there are fewer elements in the DOM tree, relayouts are cheaper as well" If I understand, this also applies? When I add the 400th (or whatever) ListItem it does trigger a layout when its added to
37.
by hueyp 14y ago
Its much faster for me as well. In order to calculate the size of each ListItem you add it to the dom briefly when its appended to the ListView. This seems to be a fast operation since you do it hundreds of times yet the page is loading qu
38.
by hueyp 14y ago
It wasn't a knock against relational databases. The issue is update in place. If you have a relational database that is append only there is no problem. He actually wrote one (datomic). The criticism of a primary key is again not anythin