Gin Hass. So this is kinda new, but it gained a very big popularity in Denmark: tendercrate.com/en/recipes/g...

Still part of the cool, for a year more 😎

Ohh that looks so nice 🤩

Please don’t tell my boss that I didn’t reach the Engineer level 🫣
Thanks for your talk and the management of the panel 🙂

i.imgflip.com/9ndbfy.jpg

Monaspace also has a handwritten variant. monaspace.githubnext.com - not sure if that is handwritten “enough” for your use case

Good take! Why don’t we add logo animations for “created with React” and epilepsy warnings and that “Please don’t. exit or refresh the page when the save icon appears”.
The excitement will be though the roof!

Lost Odyssey 😍😍😍

Take a look at the jsx transform here: new-jsx-transform.netlify.app
Everything is wrapped in a jsx function, that gives react the possibility, to set static data, so it can be accessed by hooks in your component.
It just hides it from you, by using the HTML/JSX syntax.

I think you are too keen on finding a way a method knows who is calling it. It really doesn’t. React just prepares some static variables - like a rendering context before each component call - that useState can access. One of these values is a reference to the DomNode it was rendered to last render

When you are calling setState it then, has the pointer to the place in the tree, where it has stored the component type, where it was mounted, its props from last render and the new state value. It will then render that component, and all of its children and then replace the html

When writing <Counter> it does not call your function directly. It wraps it in another function call where it, simply speaking, are storing in static memory: I am now rendering a Counter component: Let’s store its state in this position in the component-tree.

Yes this! And then use the negative selectors to filter out the things that should not get this styles. Let’s make a Iibrary for that and call it Headsuck 🤑