Shopify: yeah we stop using React Native because AI can do the code
Also Shopify
fortune.com/2026/09/17/shopi…
20 years of writing code and I finally made a proper résumé.
Mostly useful when you're available. And know what ? I'm available.
moox.io/resume
Is there anyone working at Meta on RSD that could give some insights? github.com/react/react-stric…
Is anyone using RSD (react-strict-dom) around here ? github.com/facebook/react-st…
MoOx retweeted
Apple today took a shot at React Native and other cross-platform frameworks.
I have thoughts.
First, the quote in question, from their keynote (around the 40 minute mark):
"Some other frameworks promise the ability to write code once for Android and iOS.
And that may sound good, but by the time you've written custom code to adapt each platform's conventions, connected to hardware with platform-specific APIs, implemented accessibility, and then filled in functionality gaps by adding additional logic and relying on a host of plugins, you've likely written a lot more code than you'd planned on.
And you are still left with an app that could be slower, look out of place, and can't directly take advantage of features like Live Activities and widgets.
Apple's native frameworks are uncompromisingly focused on helping you build the best apps."
MoOx retweeted
Garmin ou apple watch pour partir à l'aventure?
@MoOx a fait son choix pour sa participation à pekin express 🗺️
I just published `sf-symbols-svg` because I find myself to do this often by hand. Hope this will be useful for others.
github.com/MoOx/sf-symbols-s…
MoOx retweeted
📰 You are using @cursor_ai incorrectly...
ghuntley.com/stdlib/
Dad, it's like you are teaching it how to build and ride a bike. First you are describing what pedals are, what their purpose is and how to install them onto a bike. When the AI attempts to screw the pedals in clockwise, you are correcting it to so that it screws counter-clockwise which means that you'll never have to do that again. Eventually you'll have a fully functioning bike that can assemble another bike by itself and then can be used to make a Ferrari...
- my son
Worst idea ever. Link are not accessible with keyboard when using display: contents;
I think I found a tip to replace next/link legacyBehavior without touching too much your tree (especially interesting if you use your own text component)
<Link href="/" style={{display: "contents"}}><Text ... />...
Seems to work well.
It all started by working on chatbot for my personal website...
I was like "ok I need a name & an avatar for this bot".
Let's go with "botmax".
Which gave me an obvious "Baymax" idea.
Then it escalated quickly.
Super cool video about #React performance and React Compiler youtube.com/watch?v=INLq9RPA…
I am working on a theme concept that need to work on
#React Native and the web (Next). Main API is a "useTheme" hook. I don't like the idea of this hook because currently it requires "use client" on all components that use it. Am I incorrectly thinking that's a bad requirement?









