oh my god, so LOUD lol - i didn't read the post just clicked the link LMAO

I'm sorry!

I know this doesn't help you now, but I changed the default volume to be significantly lower...

> Sometimes I wonder if we are really equipped to navigate it and understand it. Maybe AI/computation is really the only way to try to have a holistic view of the complexities. Perhaps trying to understand biology with our biological brain has inherent limitations like a piece of software trying to understand the hardware it resides in.

This is a fascinating thought.

Fair enough, not my article though. Here's the original proposal for webpack on github:

Merge Proposal: Module federation and code sharing between bundles. Many builds act as one #10352

https://github.com/webpack/webpack/issues/10352

Legends is better anyway ya'll ;)

In my experience classes are one of the few boring, easily understood parts of react for almost everyone I mentor/work with.

I had this thought as well. Ironic isn’t it, given that the main reason for hooks is that “classes are hard”.

I'm unsure what's ironic about it. Hooks feel significantly easier to me than classes in a bunch of dimensions.

Classes come with a whole lot of syntax & concepts like constructors, instance vs class properties, autobinding, that are otherwise not used at all in React. They present barriers to optimizing code with compilers, and property names don't get minified.

Hooks are Just Functions though. They don't even have to deal with the most confusing aspect of functions in JS: "this"/calling context. You could easily consume them in ES3 by just not using array destructures and function keywords and it would barely get less readable.

Contrast this with classes, where new devs are often pushed to learn experimental and often-changing syntax just to avoid the awkwardness of working with the current specification for classes in JS. The following isn't allowed per the spec or any stage 4 proposal, but it's all over intro tutorials so that people don't have to manually bind methods in the constructor.

  class Foo { handleClick = event => {...} })

Here's another talk that illustrates some of the emerging thoughts around inline styles in React https://www.youtube.com/watch?v=ERB1TJBn32c

Yep, was thinking the same exact thing when I saw "actions".

born & raised in Austin, just might have to move back (from Silicon Valley) :)