@sregg@getsentry Also worth considering having two categories of error boundary’s. Widget and Screen. A screen could be a crash, but a widget on a dashboard is just a partial failure.
I’m starting to think my glass balcony door must be made of some kind of secret military grade radio-proof material. Inside, almost no cell service. Outside, almost no wifi.
My whole life is constantly turning wifi on and off so I can access the outside world!
explain this.
@QuinnyPig@payloadcms every damn day of the week. It’s the CMS I was dreaming of for years. Fully typescript. Everything is customizable with simple React and every lifecycle hook you could ask for. Wouldn’t change a thing.
@RobertMSterling I think for the comparison to be fair, we must also include the fact that the US is using taxpayer money to fund part of the research, to the tune of billions a year. It’s not exactly a solo venture.
@sregg@expo@sentry In a non-expo app you can add performance marks between key execution steps to understand native timing. I imagine you’d need to eject or create a mod to the same in expo. Either way it’s pretty brittle and very manual.
@sregg@mobile__dev@gptdriver I’ve found GPT driver to be pretty slow / flakey, while sacrificing too much control. It’s pretty much a black box, so you’re stuck with whatever features they implement, rather than extending functionality yourself when needed. Curious about https://t.co/fFRU8buTkV.