Allas, no telerik group yet, I assume this is the best group for this post.
I attended a kendo presentation in Rotterdam yesterday, and was already impressed before by the demos site (f.e. http://demos.telerik.com/kendo-ui/grid/editing-inline). But yesterday I heard about the two way binding that is used. I read some critiques on that that I would like to share.
Kendo-specific: http://blog.falafel.com/kendo-avoiding-the-set-performance-pitfall/
More in common / related to angular where two-way binding is used also:
http://webcache.googleusercontent.com/search?hl=en-NL&q=cache:YhwHUGTpZSAJ:https://medium.com/@mnemon1ck/why-you-should-not-use-angularjs-1df5ddf6fc99%2Bwhy-you-should-not-use-angular&gbv=2&&ct=clnk (allas only visible in cache at the moment)
http://tutorials.jenkov.com/angularjs/critique.html
http://blog.scalyr.com/2013/10/angularjs-1200ms-to-35ms/
React eschews two-way binding:
http://blog.ractivejs.org/posts/whats-the-difference-between-react-and-ractive/ (Michael Jackson's post)
Worrisome I find.
--
Kind regards,
Stefan Houtzager
Houtzager ICT consultancy & development
www.linkedin.com/in/stefanhoutzager
Hello Stefan,
Thank you for sharing these links.
Apart from the fact that probably angular v1.x is not the best framework for modern SPA's i don't think the inline editor is the best way to build complex apps. Its only useful for simple datasets.
BTW I don't think two way databinding is bad. I personally see more future in tools like Aurelia (aurelia.io), and the use of typescript or ES6. It's about an MVVM and binding is part of it.
I was not talking about angular, but about two-way binding / observable's.
"I don't think two way databinding is bad."
That can be so, but the links are clear about the con's. And contain more compelling reasoning than "I don't think two way databinding is bad.".
yes those people must be right........because they wrote an article....
No comment, because John wrote a reaction. :-)
Just what exactly are you questioning here Stefan, the observer pattern, the need to have a model? Is keeping the model in sync with the viewer(s) something that you find particular odd?
Other than that you are right, two-way binding come with a cost, that doesn't necessarily mean is something bad does it?
I don't want to repeat what you can read in the links. And said no more than finding the stated con's worrisome.
> In summary, when updating large amounts of data bound to the DOM,
> consider assigning values directly and then re-rendering the DOM versus
> calling set() on each item. The performance gains can be substantial!
Ok.
I don't see that as "worrisome". I see it as "good advice". Sort of
like: "when updating many db records, consider combining transactions
into groups of 100 or so instead of committing one record at a time"
doesn't make me think that transactions are a bad idea.
--
Tom Bascom
603 396 4886
tom@greenfieldtech.com
Just because they were acquired does not mean they have given up their own very active community:
Agreed, but I posted more links and I have no idea how much of advises could follow (in the case of angular: blog.scalyr.com/.../angularjs-1200ms-to-35ms). I do not like to fight frameworks.
Still more about two-way binding: programmers.stackexchange.com/.../pros-and-cons-of-facebooks-react-vs-web-components-polymer , see below the "Data binding" header.
Not bad to be a bit more informed no? :-))
Something worth to keep an eye on: isomorphic javascript (two-way binding not used)
www.sitepoint.com/isomorphic-javascript-applications
lots of other links to find on google. I posted something on this subject last year here: community.progress.com/.../9924.aspx
Last news: two-way databinding is no more supported in angular 2.
medium.com/.../why-do-developers-love-angular-7690ba927c92
blog.mgechev.com/.../angular2-first-impressions
Now don't tell me that they dropped it because two-way databinding is good. ;-)
--
Kind regards,Stefan Houtzager
Houtzager ICT consultancy & development
www.linkedin.com/in/stefanhoutzager