News for hackers. Stuff that matters.
Re:Removing jQuery from GitHub.com frontend by petilon on Thursday July 26, 2018 @11:01AM (#17617997)
Did you miss the fact that this component is interactive? You can't do interactivity declaratively.
Re:Removing jQuery from GitHub.com frontend by moretti on Thursday July 26, 2018 @12:06PM (#17618510)
By declaratively I mean that in React you typically declare how an element should be render given the current (props, [state]).

For example, in vanilla JS, you might have something like:

  const btn = document.createElement('button');
  btn.className = 'btn red';
  btn.onclick = function(event) {
   if (this.classList.contains('red')) {
     this.classList.remove('red');
     this.classList.add('blue');
   } else {
     this.classList.remove('blue');
     this.classList.add('red');
   }
  };

In React instead:

  class Button extends React.Component {
    state = { color: 'red' }
    handleChange = () => {
      const color = this.state.color === 'red' ? 'blue' : 'red';
      this.setState({ color });
    }
    render() {
      return (<div>
        <button 
           className=`btn ${this.state.color}`
           onClick={this.handleChange}>
        </button>
      </div>);
    }
  }
I find it simpler to understand, because render, given its state, describes exactly how the UI should be.
Re:Removing jQuery from GitHub.com frontend by petilon on Saturday August 04, 2018 @08:12AM (#17686544)
This only works for simple cases. Where this breaks down is when you have to inspect the current state of the DOM before deciding what changes to make to it. Example: scroll an element into view if it is not already visible. More examples: drag & drop, interactive resize, etc.