notbrent.dev
Working on expo.dev, attempting to play guitar. Dogs.
172 posts
1,604 followers
392 following
Regular Contributor
Active Commenter
comment in response to
post
👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀👀
comment in response to
post
open.spotify.com/track/7uWS4z...
comment in response to
post
well, good effort anyhow. cya mitch haha
comment in response to
post
last chance for this core!
comment in response to
post
go leafs! but also, leafs in game 7 🥵🥵
comment in response to
post
here's a pr to show what i mean. we used the data from your app to seed it. i hope this isn't too weird, we can change any of that if you like. also let's grab a hot chocolate or coffee some time! i'm in vancouver as well. github.com/expo/expo/pu...
comment in response to
post
hey! thanks for building this. you might find this to be entertaining - we at @expo.dev have been using your app as a reference for a simple but non-trivial ios app with standard platform ui. a test case for our expo/ui library is that you should be able to rebuild the hot chocolate app with it :)
comment in response to
post
i was thinking more along the lines of trying to bring this whole south africa thing up at any opportunity but ok sure
comment in response to
post
it’s ok i forgive you, you have never eaten an apple and are just aping
comment in response to
post
i meant your response was savage. weird wink but ok
comment in response to
post
savage
comment in response to
post
i’m deeply offended
comment in response to
post
explain why you are wrong please
comment in response to
post
what’s the best kind of apple and why is it the cosmic crisp?
comment in response to
post
what do you think about @expo.dev?
comment in response to
post
if you run into any sort of performance regression, create a minimal reproducible example and post an issue and i assure you that @cortini.co and the rest of the react native team at meta will be all over it. you'd be amazed how much they care about this rollout and the effort they put in
comment in response to
post
i'd take what you read from +1 commenters and random folks on reddit with a grain of salt. try it for yourself, let us know how it goes.
comment in response to
post
and then there's this post from the folks at kraken blog.kraken.com/product/engi...
comment in response to
post
for example, check this out from the very app we are conversing on bsky.app/profile/samu...
comment in response to
post
we also didn't just do this based on vibes, of course. along with tracking some metrics, we worked directly with a group of companies maintaining large apps to help them migrate over, we met with them regularly and worked on the issues that they encountered.
comment in response to
post
we were pretty clear about how people should expect and report issues, and we documented that as best we could. with our incremental rollout, nobody was forced into migrating to the new arch. now that we are happy with it, it's the default on all projects.
comment in response to
post
predictably, some of the most common perf issues came from the most complicated, useful (and thus widely used) libraries, such as react-native-reanimated. those maintainers did an incredible job to get it working great with new arch (and it'll be even better in v4).
comment in response to
post
for something as ambitious as rolling out a complete rewrite of the internals of react-native, i think this actually went incredibly well. some amount of pain is inevitable, but generally speaking the new arch works great these days. prior to that, it was opt-in/opt-out.
comment in response to
post
- in sdk 51 / rn 0.74 new arch was opt in
- in sdk 52 / rn 0.76 it was default for new projects (with opt out) and opt in for existing
- in sdk 53 / rn 0.79 it's default for all projects and opt out if you want to.
in each phase meta, expo, and many other folks found and fixed a bunch of issues.
comment in response to
post
hello! living in the future, my man! sdk 54 is probably out in august.
can you elaborate on the issues?
below are my thoughts on your comment, which i think is perhaps a bit hastily and unfairly worded.
comment in response to
post
we are an honest people, we say it when we mean it. “sorry” on the other hand…
comment in response to
post
as a canadian, i agree!
comment in response to
post
british culture: stiff upper lip
also british culture: damn that cli didn’t say please when it told me how to fix my problem
comment in response to
post
hm, yeah, i don't say please often in code reviews. i think i'm more inclined to say it in a review message ("please ping me before this lands so i can ...") but not in comments on specific lines ("use x method instead").
comment in response to
post
interesting! typically if i'm asking someone to do something for me, then i'll say please, and if i'm just giving advice then i'll just say it directly.
i wonder if maybe living in the UK has an impact on your preference here!
comment in response to
post
related: github.com/expo/expo/pu...
comment in response to
post
my take is that you dev tools should almost never say please. i just want them to tell me what to do.
comment in response to
post
if trump was a star wars character, which would he be?
comment in response to
post
i've seen that shade of green somewhere before!