C++ has a LHS ternary operator.

The number one good thing that React brought to front end development was the pure render function. Pure functions can be composed out of other pure functions and this gives us a more powerful way to reuse existing code.

https://medium.freecodecamp.org/higher-order-components-the-ultimate-guide-b453a68bb851

You don’t know JavaScript

Probably the best introductory article to custom elements v1.

https://developers.google.com/web/fundamentals/web-components/customelements

I just did a WebNow talk about custom elements, hyperHtml and polymer.

There may even be a video of it which I’ll post if it’s watchable.

With the React framework winning on all fronts, everyone else is consolidating around Custom Elements, a built in capability of modern browsers and polyfillable back to IE11.

While React doesn’t exactly preclude their use, the momentum here is coming from people wanting to guard against the effects of framework lock-in and monoculture.

The web platform has advanced sufficiently that some key features provided by them are no longer so important. One of the key value propositions of frameworks is the ability to make components.

https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements

In which someone else attempts to explain monads to the great unwashed JavaScript masses.

http://jrsinclair.com/articles/2018/how-to-deal-with-dirty-side-effects-in-your-pure-functional-javascript

The virtual DOM is an implementation detail.

I agree with this statement “React’s true strengths: composition, unidirectional data flow, freedom from DSLs, explicit mutation and static mental model.”

https://medium.com/@dan_abramov/youre-missing-the-point-of-react-a20e34a51e1a