Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get rid of Backbone Models for native javascript objects #788

Open
balupton opened this issue Jan 27, 2014 · 3 comments
Open

Get rid of Backbone Models for native javascript objects #788

balupton opened this issue Jan 27, 2014 · 3 comments

Comments

@balupton
Copy link
Member

Now that javascript objects have native getters, setters, and mutation observers, we could actually get rid of backbone models.

This would remove a whole lot of confusion about why toJSON() is needed etc.

It would also pave the way to having queryengine have live collections for native javascript objects.


Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

@pflannery
Copy link
Contributor

👍

@dimitarkolev
Copy link

I am calling toJSON here and there and i am quite sure that most of the time i should not. We are putting a lot of metadata in the documents from external systems and toJSON is slow. If it works without me having to think of it and having all the metadata without explicit get will be a great plus.

@balupton
Copy link
Member Author

This may actually help with memory consumption and performance too, so I've linked it to #529

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants