Re:Building Sentry, a service to process native crash report...
by the_mitsuhiko on Friday June 14, 2019 @11:19AM
(#20183691)
> Sentry went with unifying the API across language boundaries and I’m not super happy with the results but I don’t have like 30 packages to maintain
Yeah, that move and the docs did not go exactly as planned. There are a few reasons why we did it: a) the old SDKs had no sensible state management which caused endless issues such as incorrect breadcrumb collection in async code. b) it's really hard for customer support to understand the number of SDKs.
We're working on improving that, in particular docs.
Yeah, that move and the docs did not go exactly as planned. There are a few reasons why we did it: a) the old SDKs had no sensible state management which caused endless issues such as incorrect breadcrumb collection in async code. b) it's really hard for customer support to understand the number of SDKs.
We're working on improving that, in particular docs.