aleidk/master-wiki
1
0
Fork 0
Code Issues 11 Pull requests Projects Releases Packages Wiki Activity Actions

Update from obsidian -

Browse source 
Affected files:
.obsidian/plugins/obsidian-omnivore/data.json
Read Later/How Game Reviews Actually Affect You.md
Read Later/Use cases for Rust.md
Read Later/What the Rust Book didn't tell you about testing....md
Read Later/Why Signals Are Better Than React Hooks.md
projects/quests.md
projects/todos-notes/Update dots.md
This commit is contained in:
Alexander Navarro 2023-11-02 10:30:48 -03:00
parent be8dfe9cf5
commit 98ee2cd224
7 changed files with 241 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

32
Read Later/Why Signals Are Better Than React Hooks.md Normal file
View file

@ -0,0 +1,32 @@
---
id: e41b4086-963e-45e7-9ef7-2cfee7061047
title: |
Why Signals Are Better Than React Hooks
status: ARCHIVED
tags:
- read-later
date_added: 2023-11-01 14:16:42
url_omnivore: |
https://omnivore.app/me/https-youtu-be-so-8-l-bvwf-2-y-8-si-zy-gl-ie-hl-ai-pg-w-5-xo-18b8be328e5
url_original: |
https://youtu.be/SO8lBVWF2Y8?si=zyGlIeHlAiPgW5Xo
---
# Why Signals Are Better Than React Hooks
## Notes
Signals ayuda a la performance y legibilidad de una aplicación haciendo que la funcionalidades que normalmente se realizarían con los hooks `useState` y `useEffect` se realizen dentro de `signals`.
Esto permite compartir este _"estado"_ entre componentes pero solo actualizar los involucrados y no todos los desendientes del componente mayor.
Además, podemos extraer toda la lógica del estado a un archivo aparte que solo tenga código relevante, y en los componentes se mantiene solo la implementación.
Es obviamente más rápido de implementar y más limpio que hacer custom hooks, pero es añadir otra dependencia, habrá otras ventajas y desventajas??
---
## Original
[Why Signals Are Better Than React Hooks](https://youtu.be/SO8lBVWF2Y8?si=zyGlIeHlAiPgW5Xo)
By [Web Dev Simplified](https://www.youtube.com/@WebDevSimplified)