🚀 We’ve just wrapped up our 3-hour deep dive into @LynxJS_org fresh new framework from ByteDance. Nearly 700 viewers joined us live!
Here are the key takeaways from our session. 🧵👇
And here’s the full stream:
x.com/i/broadcasts/1…
Here are the key takeaways from our session. 🧵👇
And here’s the full stream:
x.com/i/broadcasts/1…
Lynx take #1: More than just a framework
ByteDance is clearly aiming for something much bigger than just “another” JS framework. They dropped everything at once:
🔹 Lynx
🔹 ReactLynx
🔹 Rspeedy
🔹 Lynx for Web
🔹 Lynx Devtools
🔹 PrimJS
Check it out: github.com/lynx-family
ByteDance is clearly aiming for something much bigger than just “another” JS framework. They dropped everything at once:
🔹 Lynx
🔹 ReactLynx
🔹 Rspeedy
🔹 Lynx for Web
🔹 Lynx Devtools
🔹 PrimJS
Check it out: github.com/lynx-family
Lynx take #2: Already running at scale
Lynx is already in production for millions of users. TikTok has been shipping Lynx-based features for Search, e-commerce, and even high-profile events like Disney100 and The Met Gala.
Not many new JS runtimes can say that on launch day.
Lynx is already in production for millions of users. TikTok has been shipping Lynx-based features for Search, e-commerce, and even high-profile events like Disney100 and The Met Gala.
Not many new JS runtimes can say that on launch day.
Lynx take #3: React is just the start
While React is the only available framework right now, LynxJS is framework-agnostic. Bytedance says half of Lynx apps don’t use React at all.
While React is the only available framework right now, LynxJS is framework-agnostic. Bytedance says half of Lynx apps don’t use React at all.
Lynx take #4: Under the Hood - Threads & Runtimes
We spent a good portion of the stream breaking down LynxJS’s internals:
🔹 How many threads does it use? 4?
🔹 Custom JS runtime: PrimJS (plus JSC & V8 support)
🔹 Lynx claims to be faster than RN, but we need benchmarks
We spent a good portion of the stream breaking down LynxJS’s internals:
🔹 How many threads does it use? 4?
🔹 Custom JS runtime: PrimJS (plus JSC & V8 support)
🔹 Lynx claims to be faster than RN, but we need benchmarks
Lynx take #5: First dev experience
🔹 Bootstrapped a project in under 2 minutes—solid start
🔹Some CSS support missing
🔹Hot reload exists but broke a few times—we had to restart app and/or dev server
🔹 Similar feeling to Expo Go!
🔹We hacked together some CSS animations, bottom tabs, safe areas, and more live on stream (and by "we" I mean @ChmalSzymon through liveshare in vscode)
🔹 Bootstrapped a project in under 2 minutes—solid start
🔹Some CSS support missing
🔹Hot reload exists but broke a few times—we had to restart app and/or dev server
🔹 Similar feeling to Expo Go!
🔹We hacked together some CSS animations, bottom tabs, safe areas, and more live on stream (and by "we" I mean @ChmalSzymon through liveshare in vscode)
Lynx take #6: Native APIs and/or Navigation
🔹How will React Router feel on a mobile-like framework? Will it be "native" though? We have react-navigation and react-native-screens for a reason ...
🔹What about Camera, File Picker, and other native modules? I guess there is a way of getting there myself, but the out-of-the-box support seems to be missing.
Lots of unknowns here. Or I'm really bad at searching
🔹How will React Router feel on a mobile-like framework? Will it be "native" though? We have react-navigation and react-native-screens for a reason ...
🔹What about Camera, File Picker, and other native modules? I guess there is a way of getting there myself, but the out-of-the-box support seems to be missing.
Lots of unknowns here. Or I'm really bad at searching
Lynx take #7: Shockingly Polished for a 2-Day-Old Release
We were amazed by how usable LynxJS already is!
Or maybe we shouldn’t be? - ByteDance has clearly been using this internally for some time before the public launch.
We were amazed by how usable LynxJS already is!
Or maybe we shouldn’t be? - ByteDance has clearly been using this internally for some time before the public launch.
Lynx take #8: What’s next?
🔹Will the community pick this up?
🔹What’s Bytedance’s collaboration plan?
🔹Could Lynx-level optimizations inspire other frameworks (e.g., React Server Components at a system level)?
Exciting times ahead.
🔹Will the community pick this up?
🔹What’s Bytedance’s collaboration plan?
🔹Could Lynx-level optimizations inspire other frameworks (e.g., React Server Components at a system level)?
Exciting times ahead.
Lynx take #9: Should you get in early?
🔥 Hot take from @syke :
"If you believe Lynx will be big, now is the time to get in.
Early adopters can shape the ecosystem and potentially replicate the success of pioneering companies like @callstackio, @swmansion, and @infinite_red did for React Native."
If you want to be part of this from day one, now’s the time.
🔥 Hot take from @syke :
"If you believe Lynx will be big, now is the time to get in.
Early adopters can shape the ecosystem and potentially replicate the success of pioneering companies like @callstackio, @swmansion, and @infinite_red did for React Native."
If you want to be part of this from day one, now’s the time.
Lynx take #10: React Native vs. Lynx?
We got this great chat comment from @dzienko:
“This is a new project, but you treat it like a scary ‘opponent.’ Why see it as a threat to React Native when a former core React member created it? Maybe a fresh perspective is exactly what’s needed!”
My take: I feel completely opposite!
Healthy competition drives innovation. Flutter pushed React Native to improve, and Lynx could have an even bigger impact.
Why? Unlike Flutter, Lynx is built on the same foundations as React Native:
🔹It’s a JavaScript-driven runtime
🔹It uses React (at least for now)
🔹It shares performance goals and constraints
🔹It even reuses some of the same ecosystem tools
This means cross-pollination is not just possible, but inevitable.
🔹Libraries like React Navigation or Reassure could be adapted
🔹Dev tools could be shared (or at least inspired by each other)
🔹Performance optimizations in Lynx could influence React Native, and vice versa
🔹Instead of a direct competitor, Lynx might become a parallel evolution—something that strengthens the React Native ecosystem rather than replacing it.
This is a win-win, and I’m excited to see what comes next!
We got this great chat comment from @dzienko:
“This is a new project, but you treat it like a scary ‘opponent.’ Why see it as a threat to React Native when a former core React member created it? Maybe a fresh perspective is exactly what’s needed!”
My take: I feel completely opposite!
Healthy competition drives innovation. Flutter pushed React Native to improve, and Lynx could have an even bigger impact.
Why? Unlike Flutter, Lynx is built on the same foundations as React Native:
🔹It’s a JavaScript-driven runtime
🔹It uses React (at least for now)
🔹It shares performance goals and constraints
🔹It even reuses some of the same ecosystem tools
This means cross-pollination is not just possible, but inevitable.
🔹Libraries like React Navigation or Reassure could be adapted
🔹Dev tools could be shared (or at least inspired by each other)
🔹Performance optimizations in Lynx could influence React Native, and vice versa
🔹Instead of a direct competitor, Lynx might become a parallel evolution—something that strengthens the React Native ecosystem rather than replacing it.
This is a win-win, and I’m excited to see what comes next!
Lynx take #11: Live stream thoughts
3 hours, almost 700 people watched—insane turnout!
I think this is a hot topic for react universe community, we'll definitely talk more about it in the future.
Thank you @grabbou @ChmalSzymon @syke for great conversation :)
And everyone: thanks for joining, see you at the next one 🚀
3 hours, almost 700 people watched—insane turnout!
I think this is a hot topic for react universe community, we'll definitely talk more about it in the future.
Thank you @grabbou @ChmalSzymon @syke for great conversation :)
And everyone: thanks for joining, see you at the next one 🚀
• • •
Missing some Tweet in this thread? You can try to
force a refresh
