rust-rdom VS symbolicator

There are two steps there: (1) rust-rdom working enough to be used by Yew, and (2) SSR support built out in Yew utilizing rust-rdom. Part (2) is pretty far away, but (1) is probably about halfway there. I think a more realistic use-case for the library is Sycamore which is much earlier and simpler than Yew. Sycamore support has a tracking issue here: https://github.com/rust-rdom/rust-rdom/issues/15

Hey, thanks for the suggestion. It already is largely generated - if you look at https://github.com/philip-peterson/rust-rdom/blob/a805f9439c380b3bf8b02572197a6b81eb425516/src/node/raw/mod.rs#L145 everything up to line 145 is basically defining the templates and then afterward is just instantiating that template for the different node types, with a few one-off customizations like for Document. The same is done in a few other places.

- 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 readable, not overly terse. Compared to rust, e.g. [0], anyone who has any programming experience can probably figure out most of the syntax.

We've got a few internal services and things in Go,vanr we use them for onboarding. Most of my team have had PR's merged with bugfixes on their first day of work, even with no previous go experience. It lets us care about business logic from the get go.

[0] https://github.com/getsentry/symbolicator/blob/master/crates...

> 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/

2022: https://blog.sentry.io/we-just-gave-260-028-dollars-to-open-...

In addition to that, there are contributions to open source done in the form of code that is, open source, such as the symbolication service: https://github.com/getsentry/symbolicator and many others: https://github.com/getsentry/

Digging up the topic, I also found that 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 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.