It’s me once again asking for some help😅 Are there any solutions/sales engineers out there who would be willing to chat with me about your experience?
Would love to chat! I’m trying to figure out if solutions/sales engineering could be a good fit for me
We were seeing misleading stacktraces in Bugsnag. Turns out the new Error object takes a stacktrace snapshot when you instantiate it, thus defining it in a variable far away from where it is thrown will mislead your stacktrace.
See this post for the explanation
andrei-calazans.com/posts/predef...
They likely oversell knowing the high churn rate.
Yes! I feel the same. Great times are ahead of us, specially if you had to build Android apps on early RN versions.
Do people actually make money on Medium?
Every once in a while I find something I actually want to read and can't bc I just can't get myself to pay Medium
This wiser than you think when you consider FlatList's default virtualization config. By default it renders 21 pages, so consider a page with 8 visible items that's 168 items rendered. Most usages don't fetch over 40 items at once
It's a complicated overlap between platform specific versus React Native knowledge, will be hard for RN docs to cover all the platform specific stuff.
There isn’t an alternative because the UIManager module that dispatched commands via node handler no longer exist on the new architecture.
With the above you should be able to see where the issue lies.
3/
Analyze JS CPU profiling in production. Use @margelo.com 's react-native-release-profiler github.com/margelo/reac... to capture release profiling. Use the --fromDownload option and explicitly pass the source maps generated from the release build.
2/
Profile the APK natively. Add <profileable android:shell="true" /> to your AndroidManifest then do a native profiling of your APK via Android Studio. Then edit the build configuration to start profile recording on startup.
ps: this crashes sometimes but be persistent, it's quite helpful.
This could be many things. If the scroll is choppy at the native level maybe the UI thread is too busy. Few tips, only do this with a release build:
1/
it was deprecated but then put back to ensure backwards compatibility.
:smile:
It seems like sharing posts on Instagram is also one
This is a great find by Dan Abramov, you can reduce the Reanimated serialization traffic by moving the different animation end states outside the frequently updating context by using makeMutable.
github.com/bluesky-soci...
started using Bluesky this week bc of that
and how do you use them?
sure I've had a few conversations with them but i still find it a bit cold and unable to perceive my emotions.
We built this! 💪
Hire us if you need advanced features like this 📩
Totally deserve, they were early on solving an entire set of challenges with handling server state.
Micromanaging is a big part for sure. But I also think that not everyone is fit for remote work. It takes high level of self agency to be productive in a such a free environment and to find such talent takes a bit of hit and miss.
Rocket
The compounding growth
It's a bit scary to see Elon Musk have so much control over the narrative on X/Twitter. I'm not american, nor do I support any one side, but there was a clear control of narrative on X during this election.
It's amazing see @expo.dev go from being rejected by anyone doing serious React Native development to becoming the best choice.
Appreciate this
Oh and Flipper is also dead now. Meta won't continue developing it.
fbflipper.com/blog/2024/10...
Let me try Bluesky for a bit. Let's see if it can expand my network beyond what X/Twitter can offer me.
FYI React Native Core is deprecating SafeAreaView. Use react-native-safe-area-context instead:
github.com/react-native...
