symbolicator

I work on large c++ code bases day in day out - think 30 minute compiles on an i9 with 128GB ram and NVMe drives. Rusts compile times are still ungodly slow. I contributed to a “small to medium” open source project [0] a while back, fixing a few issues that we came across when using it. Given that the project is approximately 3 orders of magnitude smaller than my day to day project, a clean build of a few thousand lines of rust took close to 10 minutes. Incremental changes to the project were still closer to a minute at the time. I’ve never worked on a 5m+ LOC project in rust, but I can only imagine how long it would take. On the flip side, I also submitted some patches to a golang program of a similar size [1] and it was faster to clone, install dependencies and clean build that project than a single file change to the rust project was.

> Go feels like a massive step in the right direction I agree. Go has it's warts, but given the choice between using net/http in go, tomcat in java, or cpprestsdk in c++, I'll pick Go any day. In practice: - The toolchain is self contained, meaning install instructions don't start with "ensure you remove all traces of possibly conflicting toolchains" - it entirely removes a class of discussion of "opinion" on style. Tabs or spaces? Import ordering? Alignment? Doesn't matter, use go fmt. It's built into the toolchain, everyone has it. Might it be slightly more optimal to do X? Sure, but there's no discussion here. - it hits that sweet spot between python and C - compilation is wicked fast, little to no app startup time, and runtime is closer to C than it is to python. - interfaces are great and allow for extensions of library types. - it's

I know for a fact that your competition is using your code, even where they've built a differentiated service. e.g. Embrace is using Sentry Symbolicator. Having built my own symbolicator before yours existed, that's easily months of work that requires highly specialized knowledge. Like maybe a few dozen developers on the planet could write that. I know you get a lot of flack over BUSL, but I'm not sure folks appreciate just how much of Sentry is open source and how much you're giving away, some of it of very high value almost exclusively to your competition. I mean who but a Sentry competitor would need your symbolicator? No one. Meanwhile looking at https://github.com/getsentry/symbolicator/graphs/contributor... I'm not seeing what looks like too many, if any, outside contributions.

> Aren't they slower or about as slow as C++, which is notorious for being frustratingly slow, especially for local, non-distributed builds? Yes. Significantly slower. The last rust crate I pulled [0] took as long to build as the unreal engine project I work on. [0] https://github.com/getsentry/symbolicator/

Sentry’s license change on the fork was a mistake. It has been fixed though: https://github.com/getsentry/rrweb/pull/92 The fork exists as a ‘buffer’ to get some changes (features or bug fixes) out without the need to couple with the npm release of rrweb itself. Sentry engineers have several PRs in upstream rrweb merged and the goal is to increase the upstream contributions and close the gap between our fork and upstream. We’re currently porting our changes from v1 to the v2 branch. I believe Sentry has made financial contributions to rrweb but directly to a maintainer. I'll let others who know details to comment on this. I'm sure more contributions will be done, as this is very much in the interest of Sentry anyway. Worth noting, Sentry has been making larger contributions to OSS every year, as the company grows: 2021: https://blog.sentr

Digging up the topic, I also found this new framework https://github.com/tokio-rs/axum, which already seems to be popular. Sentry is rewriting some of their libs from Actix to Axum: https://github.com/getsentry/symbolicator/commit/b6ef7cb00b7...

Disclosure: I work at Sentry. > My personal term for this sort of "We're OK with little people using the software but we don't want any competition" Large companies are free to use Sentry. There are Fortune 50 companies running Sentry at scale internally without paying us a cent. That's totally cool. You're also free to compete with Sentry. You're not free to repackage Sentry for the purposes of competing with us. There are lots of competing error and performance monitoring products out there that do perfectly fine without it. I should also note that many components of Sentry are distributed with OSI-approved licenses that you are free to use to compete with us. For example, our Symbolication service (https://github.com/getsentry/symbolicator) ships with an MIT license, and it's an important part of our business.

I really hope so! I added support for it (https://github.com/getsentry/symbolicator/pull/142) the moment I saw the announcement :)

Take a look at the symbolicator service from sentry: https://github.com/getsentry/symbolicator

We (sentry.io) use actix-web (though not yet 1.0) for our symbolicator project. It’s the service that handles all of our native events for symbolication. That’s for minidump processing, dwarf/pdb based symbolication and much more. Couldn’t be happier with it. It’s super fast and stable and does it’s job really well. We run three machines for it and it didn’t manage to go past 10% CPU usage yet. Code is here for the curious: https://github.com/getsentry/symbolicator