121–130 of 138 posts
Earlier quoted context omitted.
Angular 2way is based on dirty check. Ractive and vue.js are really data binding with atomic changes.
I said nothing about Ractive and Vue. Their 2 way binding is better, but with large quantities of bindings, it's still slow.
Earlier quoted context omitted.
I said nothing about Ractive and Vue. Their 2 way binding is better, but with large quantities of bindings, it's still slow.
Virtual dom consume more computation processor while data binding consume more memory.
Earlier quoted context omitted.
No, the perf's pretty bad if you do a lot of binding, and the manual binding gives you a better sense of what your app is doing, the performance tradeoffs you're making, and more control over an area where you'll probably have to optimize.
Vue.js 2 is an hibrid between virtual dom and data binding.
Earlier quoted context omitted.
It might not have a explicit opinion stated anywhere but in any library or framework, the API provided influences how those APIs are used. By having the central unit of work start with a query selector is one such influence which I feel implicitly encouraged DOM manipulations. Taking a look at the original jQuery website on web.archive, this is the introduction to the $() function: "The functionality of jQuery center…
> [...] I feel implicitly encouraged DOM manipulations. That's jQuery's primary job. It isn't DOM manipulation that causes code/architectural issues. "All" (I'm simplifying) jQuery does is provide mechanisms to select and manipulate DOM. How to organize its usage is an exercise left to the reader, and most readers did it poorly. It's not jQuery's fault that people wrote shitty code with it. And, in fairness, when Pro…
Of course you can architect those flexible, extensible, testable and clean projects. But straight out of the box you do not get that with jQuery. It requires planning and architecture engineering.
Whereas every React project starts off with those principals.
In other words, the ways people can use jQuery wrong is worse than the ways people can use React wrong.
Earlier quoted context omitted.
It might not have a explicit opinion stated anywhere but in any library or framework, the API provided influences how those APIs are used. By having the central unit of work start with a query selector is one such influence which I feel implicitly encouraged DOM manipulations. Taking a look at the original jQuery website on web.archive, this is the introduction to the $() function: "The functionality of jQuery center…
> [...] I feel implicitly encouraged DOM manipulations. That's jQuery's primary job. It isn't DOM manipulation that causes code/architectural issues. "All" (I'm simplifying) jQuery does is provide mechanisms to select and manipulate DOM. How to organize its usage is an exercise left to the reader, and most readers did it poorly. It's not jQuery's fault that people wrote shitty code with it. And, in fairness, when Pro…
Earlier quoted context omitted.
It might not have a explicit opinion stated anywhere but in any library or framework, the API provided influences how those APIs are used. By having the central unit of work start with a query selector is one such influence which I feel implicitly encouraged DOM manipulations. Taking a look at the original jQuery website on web.archive, this is the introduction to the $() function: "The functionality of jQuery center…
> [...] I feel implicitly encouraged DOM manipulations. That's jQuery's primary job. It isn't DOM manipulation that causes code/architectural issues. "All" (I'm simplifying) jQuery does is provide mechanisms to select and manipulate DOM. How to organize its usage is an exercise left to the reader, and most readers did it poorly. It's not jQuery's fault that people wrote shitty code with it. And, in fairness, when Pro…
Earlier quoted context omitted.
It might not have a explicit opinion stated anywhere but in any library or framework, the API provided influences how those APIs are used. By having the central unit of work start with a query selector is one such influence which I feel implicitly encouraged DOM manipulations. Taking a look at the original jQuery website on web.archive, this is the introduction to the $() function: "The functionality of jQuery center…
> [...] I feel implicitly encouraged DOM manipulations. That's jQuery's primary job. It isn't DOM manipulation that causes code/architectural issues. "All" (I'm simplifying) jQuery does is provide mechanisms to select and manipulate DOM. How to organize its usage is an exercise left to the reader, and most readers did it poorly. It's not jQuery's fault that people wrote shitty code with it. And, in fairness, when Pro…
Earlier quoted context omitted.
Well, React has one huge disadvantage: It requires you not suing FB, even if they abuse some of your own patents. That patent license they have in their project basically means you can only use React as dev in a company if your company does not have patents or noteworthy IP.
Not true any more: https://mobile.twitter.com/paul_irish/status/754864479460929...
Earlier quoted context omitted.
Vue.js 2 is an hibrid between virtual dom and data binding.
All VDOM systems are. The difference is how explicit the data binding is: I maintain implicit 2-way binds, Angluar style, are a Bad Idea.
http://blog.ractivejs.org/posts/whats-the-difference-between...