Samuel Gomez (@gamuez) header
Samuel Gomez (@gamuez) profile picture

Lead Front-End Developer, ReactJS, NodeJS https://xitter.gq/t.co/diuL4J4VCP

Versailles, France
Joined April 2015
Photo by Samuel Gomez (@gamuez)Photo by Samuel Gomez (@gamuez)Photo by Samuel Gomez (@gamuez)Photo by Samuel Gomez (@gamuez)Photo by Samuel Gomez (@gamuez)Photo by Samuel Gomez (@gamuez)Photo by Samuel Gomez (@gamuez)Photo by Samuel Gomez (@gamuez)Photo by Samuel Gomez (@gamuez)Photo by Samuel Gomez (@gamuez)
Gecko: Intent to ship: CSS Anchor Positioning bit.ly/3MCaGWo
13
5
44
32,704
Samuel Gomez retweeted
🥳 CSS functions have arrived!!! 🥳 And they are *AWESOME* Now, you can do things like this: @​function --alpha(--color, --opacity) { result: rgb(from var(--color) r g b / var(--opacity)); } div { background: --alpha(red, 80%); } (*arrived = in the latest stable Chrome)
60
166
60
1,385
165,063
It was always more than about performance. I started Solid because I liked the mental model of Knockout more than React. Retained mode fit with the DOM better than this immediate mode abstration that React put out there. I needed to focus on performance initially to undo the damage caused by DOM slow, VDOM fast. A lot of benchmarks looked at diffing speeds when diffing wasn't what users primarily need to be doing. This starts pre-React Hooks. React adopted this language later and honestly for some people on this side of things that was enough. But it became more obvious just how different these these things end up being. The key difference is React conflates state with UI organization. On change of state the declared body (and descendants) need to re-run if things change. With Signals it is only the computations that need to re-run. It looks similar but it means that state runs through components rather than are the components. I do think there is some preference here. I'm not saying everyone will find Signals better fit for their mental model. But we shouldn't be just suggesting it's a performance thing. People will point to this run-once mentality being simpler to understand once there are multiple isolated states involved, but the real power is that you can describe more complicated states in a hoisted manner and have isolated updates. If something changes in a complex data structure in React it has no choice but to re-run all the way down that UI tree. Memoizationn can prune branches but it needs to run all the way from declaration to usage. Yes Signals need to run along their portion of the graph but that is scaled on the derivation of the data not the UI. More so if your application is data dependency aware it opens up different sorts of problem space solutions. Granular partial Hydration/Resumability. I was hired at eBay because they recognized the importance of being able to separate the state from the UI which could stay on the server. My recent research has been into self healing graphs and granular derivation. These are areas where we will see tangible differences when it comes scaling of larger granular/incremental data systems. Things like sync engines. I'm glad that @ryanflorence is asking these questions because these are common thoughts, and it provides an opportunity to refine education in these areas, because unlike React the communities here smaller and have had less time to really refine the message.
My read on the React alternatives is their primary selling point is better performance through alternative dependency tracking approaches When I look at the APIs they look identical with mostly identical semantics - state thing - effect thing - elements What am I missing?
16
43
6
466
76,263
Samuel Gomez retweeted
Firefox 126.0a1 does indeed support transitioning `@property` variables 🎉 funny, cuz just today I made an progressively enhancing @property example, and yep, works great in Firefox Nightly! codepen.io/argyleink/pen/LYv…
Wake up, wake up, wake up! @FirefoxNightly finally supports animating custom properties (registered via `@​property`)! 🥳🎉 For the past 6-7 years, I have made ~200 such demos on @CodePen and they should now work in Firefox Nightly! codepen.io/thebabydino/pens/…
1
14
1
121
15,709
Information ; Dear Friends and Partners en.dragon-ball-official.com/…
25,361
196,863
107,358
647,040
93,025,010
Samuel Gomez retweeted
🚨🚨🚨🚨 Apple will NOT remove PWA support on iOS 🥳🥳🥳🥳 👉This is an official statement form Apple that replaced today the previous excuses published around the removal. We did it, folks!
54
421
109
2,283
348,848
Samuel Gomez retweeted
By the end of 2024, you’ll likely never need these APIs again: • useMemo, useCallback, memo → React Compiler • forwardRef → ref is a prop • React.lazy → RSC, promise-as-child • useContext → use(Context) • throw promise → use(promise) • <Context.Provider> → <Context>
123
814
229
4,502
623,481
Samuel Gomez retweeted
🤯 Today I learned about the media scripting feature. It's about detecting JS support via a CSS media query. Soon, we won't need the `.no-js` or `.js` classes once this is widely available. Currently supported in Chrome 120, Firefox 119, Safari 17.
7
95
4
624
92,166
Samuel Gomez retweeted
Replying to @merittthomas
@merittthomas Hi, I came across Epic Easing epiceasing.com/ and noticed it's adding needless prefixes. Opera & Firefox unprefixed transitions back in 2012, over a decade ago. Global usage for pre-Chromium Opera that needed the -o- prefix is now 0%.
1
2
2
408
Entangled #fxhash
1,888
9,016
3,404
62,650
10,204,341
🎉 Announcing MSW 2.0! 🎉 🌎 Migration guidelines: mswjs.io/docs/migrations/1.x… 📰 Release notes: github.com/mswjs/msw/release… 365+ days in development, 200+ commits, 40+ contributors involved. The future of API mocking is here, and it has never been brighter.
19
129
21
715
161,362
Dupliquer le code d’un projet sur deuxième git ne fait que doubler le coût de développement et de maintenance du projet. A l’inverse, travailler ensemble sur la même base de code tire le code, la qualité vers le haut et diminue le coût de développement du projet. 😘
2
5
272
Chez @AXAJobs_fr, on se lance dans les #bbl #meta #hybride : en salle, sur teams et dans le #metaverse #spatial en temps réel ! C’était top de parler #metaverse dans le #metaverse! Merci @cyrillemagnetto @johankroger et toute la team 🚀 – at Bondues, France
1
1
15
1,737
#VSCode tip ✨ If you want to commit only some of the modifications you made within a file, you can stage these changes with ‘Stage selected ranges’
2
4
39
Il existe une version pure javascript de react-oidc avec une petite démo à améliorer mais c'est déjà ça 😃 npmjs.com/package/@axa-fr/va…
4
4
Import maps bring bare module specifiers to browsers: 2ality.com/2022/01/esm-speci… − import * as THREE from '.../build/three.module.js'; + import * as THREE from 'three'; Supported soon in all major browsers: caniuse.com/import-maps xitter.gq/mrdoob/status/13653029…
Feels good to be able to use bare specifiers in the browser 💆‍♂️ github.com/mrdoob/three.js/p…
2
5
29
Wow, that’s impressive! The Wix team has edited 7643 error messages to design clear, helpful, respectful and inclusive messaging and error handling. wix-ux.com/when-life-gives-y… #ux #design
47
907
95
6,826
Devenir "Le/la Meilleur.e Étudiant.e en Informatique de France 2022" en 15 min, c'est possible avec le #ChallengeITAXA ! Découvrez toutes les étapes ⤵
1
7
13
My new book is now free to read online: “Shell scripting with Node.js“ exploringjs.com/nodejs-shell…
8
173
10
699
Bravo à tous les contributeurs du blog #JustTechIT ! Profitez de l’été pour approfondir vos connaissances dans le domaine #IT ! 👉🏻 https://xitter.gq/t.co/Vxxr89wLyN
6
7