Ciro Santilli @cirosantilli 37

React function components do produce shorter code. But they are also impossible to understand without knowing what is their corresponding class component.

Hooks were introduced much after classes, and just require less code, so everyone is using them now instead of classes.

Dummy example of using a React ref This example is useless and to the end user seems functionally equivalent to react/hello.html.

It does however serve as a good example of what react does that is useful: it provides a "clear" separation between state and render code (which becomes once again much less clear in React function components.

Notably, this example is insane because at:we are extracing state from some random HTML string rather than having a clean JavaScript variable containing that value.

In this case we managed to get away with it, but this is in general not easy/possible.

React function component version of react/ref-click-counter.html using useRef.

Minimal React hello world example. As you click:By opening a web inspector, you can see that only modified elements get updated. So we understand that JSX parses its "HTML-like" into a tree, and then propagates updates on that tree.

By looking at the terminal, we see that render() does get called every time the button is clicked, so the tree of elements does get recreated every time. But then React diffes thing out and only updates things in the DOM where needed.

Ciro Santilli reproduced on Dell Inspiron 15 3520 with factory defaults. This bug prevents "wipe windows" installation without workarounds, one of which is to disable encryption in Windows.

Happens at startup without doing anything, and then keeps happening randomly infinitely many times... on a almost clean 24.04 ISO install on Dell Inspiron 15 3520... God how can it be so bad.

Viewing the apport issue a bit further shows title:

Possibly related:

This should only be used for things that happen outside of the state that React trackes, e.g. window event handlers.

Examples:

"Quantum interconnect" refers to methods for linking up smaller quantum processors into a larger system.

As of 2024, seemingly few organizations developing quantum hardware had actually integrated multiple chips in interconnects as part of their main current roadmap. But many acknowledged that this would be an essential step towards scalable compuation.

The name "quantum interconnect" is likely partly a throwback to classical computer's "chip interconnect".

Sample usages of the term: