6 ms·

> "I don't think we need new complicated technologies to solve the kinds of problems React solves. If anything, we need less, like an alternative to the current

by Andrex 8y ago

> "I don't think we need new complicated technologies to solve the kinds of problems React solves. If anything, we need less, like an alternative to the current DOM model." It seems to me as if you're saying: "We don't need new complicated technologies." "Also, we need a new, complicated replacement to the time-tested DOM." This probably wasn't the intent but it exposes the need for web components to be built the way they are: progressively enhanced from what's already standardized in browsers. Web components really aren't that complex, and comparing them to React in this way is a disservice.

jchw 8y ago
Yeah, the DOM the web layout engine isn't complicated at all ... display: block; display: inline; display: run-in; display: flow; display: flow-root; display: table; display: flex; display: grid; display: ruby; display: block flow; display: inline table; display: flex run-in; display: list-item; display: list-item block; display: list-item inline; display: list-item flow; display: list-item flow-root; display: list-item block flow; display: list-item block flow-root; display: flow list-item block; display: table-row-group; display: table-header-group; display: table-footer-group; display: table-row; display: table-cell; display: table-column-group; display: table-column; display: table-caption; display: ruby-base; display: ruby-text; display: ruby-base-container; display: ruby-text-container; display: contents; display: none; display: inline-block; display: inline-table; display: inline-flex; display: inline-grid; Of course that's just CSS/the layout engine. The DOM itself is sort of unrelated. But to that effect, I'd like to mention two filesizes. React 16.6.0 base library, minified: 6.21 kb React 16.6.0 DOM integration, minified: 100.39 kb
- pjmlp 8y ago
  Those file sizes miss the dependencies that are native to the browser. Web Components: 0 kb
  - jchw 8y ago
    You forgot the polyfills.
    - aitchnyu 8y ago
      Cynical me saw Youtube in Chrome loading instantly while Firefox was served a build with the high parsing cost of Polymer polyfills. And starry-eyed developers importing if and for statements and writing imperative dom updates, while running some JS transpiler just like a React guy does. Never mind two major versions made Googling impossible, or debugging methods available to only geniuses.
    - pjmlp 8y ago
      The browsers we target don't need polyfills.
      - jchw 8y ago
        So you aren't targeting Safari, Edge, Firefox ESR or any version of IE?
        pjmlp 8y ago
        Never had to deal with Firefox ESR, and very few customers are still stuck on IE 11, thanks to the ongoing migration to Windows 10. Latest versions of Firefox, Chrome and Safari support all necessary features for Web Components.

by Andrex 8y ago

jchw 8y ago

Yeah, the DOM the web layout engine isn't complicated at all ... display: block; display: inline; display: run-in; display: flow; display: flow-root; display: table; display: flex; display: grid; display: ruby; display: block flow; display: inline table; display: flex run-in; display: list-item; display: list-item block; display: list-item inline; display: list-item flow; display: list-item flow-root; display: list-item block flow; display: list-item block flow-root; display: flow list-item block; display: table-row-group; display: table-header-group; display: table-footer-group; display: table-row; display: table-cell; display: table-column-group; display: table-column; display: table-caption; display: ruby-base; display: ruby-text; display: ruby-base-container; display: ruby-text-container; display: contents; display: none; display: inline-block; display: inline-table; display: inline-flex; display: inline-grid; Of course that's just CSS/the layout engine. The DOM itself is sort of unrelated. But to that effect, I'd like to mention two filesizes. React 16.6.0 base library, minified: 6.21 kb React 16.6.0 DOM integration, minified: 100.39 kb

pjmlp 8y ago
Those file sizes miss the dependencies that are native to the browser. Web Components: 0 kb
- jchw 8y ago
  You forgot the polyfills.
  - aitchnyu 8y ago
    Cynical me saw Youtube in Chrome loading instantly while Firefox was served a build with the high parsing cost of Polymer polyfills. And starry-eyed developers importing if and for statements and writing imperative dom updates, while running some JS transpiler just like a React guy does. Never mind two major versions made Googling impossible, or debugging methods available to only geniuses.
  - pjmlp 8y ago
    The browsers we target don't need polyfills.
    - jchw 8y ago
      So you aren't targeting Safari, Edge, Firefox ESR or any version of IE?
      - pjmlp 8y ago
        Never had to deal with Firefox ESR, and very few customers are still stuck on IE 11, thanks to the ongoing migration to Windows 10. Latest versions of Firefox, Chrome and Safari support all necessary features for Web Components.