News for hackers. Stuff that matters.
Re:The broken promise of Web Components by jbergens on Thursday March 16, 2017 @08:52AM (#13884563)
Probably finding the right place of the dom to change and keeping track of what to change. React basically says "make it like this" and takes care of a lot of things.

jQuery code is well known to be hard to maintain when it changes things based on element-types, classes and id's nested in each other.

Re:The broken promise of Web Components by bigmanwalter on Thursday March 16, 2017 @09:03AM (#13884630)
It's quite simple to handle that situation with jQuery and modules. If many parts of you code need to make a change to the DOM in the same place, you wrap the DOM changing in a module.

  var widget = require('./widget');
  widget.foo('bar');
And the widget handles the jQuery'ing for you.

  module.exports = {
    foo: function(s) { $('.widget').text(s) }
  }
Re:The broken promise of Web Components by dmitriid on Thursday March 16, 2017 @02:54PM (#13887901)
Only:

- it breaks immediately if there is more than one '.widget' on the page

- your app will get out-of-sync DOM updates because different parts will flush changes to the DOM at different times (React is DOM = f(state, time), so if multiple changes happen in f, they all be flushed to DOM in one go)