Can somebody please fucking explain to me what dumbass developer defined the phrase “synchronous operations” to mean “one after the other” when the word “synchronous” literally means “happening at the same time”
@dan_abramov Yes, because if "const myList: number[] = [];" is valid at static time, "myList.every((el) => typeof el === 'number');" should be valid at runtime.
The Stately Editor beta is now open for everyone! 🎉
🚀 A low-code visual editor for building app logic
🪄 Create executable diagrams and use them in code
Try the beta now at: https://t.co/SqbjrUs5af
My Little Storybook 🪶- An interactive story about a bird family crossing the river. It is how we reimagine children books can be done these days leveraging the immersive Web technology. Check it out!
👉https://t.co/CX7QeGlops
#webgl#threejs#monthlyexp#anime#b3d#zbrush
Such a seemingly simple question, but it sparked a fascinating discussion🙂 I tend to think, that in practical terms () => [] is not pure. That's why we have useMemo(...)
This is the most awesome demo I've ever seen. You may have heard that the Commodore 64 had a second CPU in its disk drive. But you've probably never seen anyone prove it quite like this:
https://t.co/sfdfJtiaMM
My talk from @YGLF_IL, 'Rethinking Reactivity', went online yesterday — https://t.co/eoGiBBAkKI. You probably don't have time to watch a 35 minute video though, so I'm going to pull out a few key slides into a quick tweet thread: