relay VS PropertyChanged

It's probable the core will always remain closed. That's both a business and practical decision. However, much like how Sentry have some of their services open-source, we may follow that route.

There's rust stuff too: https://github.com/getsentry/relay

Sentry uses Rust in their backend, check out relay.

Sentry (sentry.io) | senior software engineer, Rust | Vienna, Austria OR Remote (EU) | https://sentry.io/careers/4635809/

As a Senior Software Engineer on our client infrastructure team, you'll join a cross-functional group of Software Engineers that is responsible for the client-facing operation of Sentry. This includes building and maintaining our event ingestion and processing pipeline, most notably Relay (https://github.com/getsentry/relay). This means you will be involved in the design and evolution of both external and internal services, as well as create new mission-critical software at Sentry.

If you like system programming, know Rust (or another systems programming language) and want to work on mission-critical high-volume services, this is the role for you. And your contributions are open source!

Apply here: https://sentry.io/careers/4635809/

Try https://docs.sentry.io/product/relay/

We have no Nim usage in the company. One of our engineers nominated it as something they find personally interesting, and we wanted to give at least a little bit to every project that our employees nominated.

By contrast, we use Rust quite heavily, including our core ingest component: https://github.com/getsentry/relay.

That's why there's such a discrepancy in this case.

Add [AddINotifyPropertyChangedInterface] attribute to the class for change notification.

All the weaving libraries (also called weavers or addin) using Fody need to have the .Fody suffix, so it's quite easy to recognize them. As an example, if you ever had to implement INotifyPropertyChanged manually in a class with dozens of properties you would probably welcome weaving (and Fody) with open arms. By creating all the plumbing code directly in IL, libraries like PropertyChanged.Fody allows to inject the necessary notification code without the need to modify anything in the original source code.

You can rewrite auto-props (as used this this lib https://github.com/Fody/PropertyChanged) with Fody.

If you're not familiar with Fody and specifically the PropertyChanged weaver, I highly recommend checking it out: https://github.com/Fody/PropertyChanged

Now the ugly part - you need to implement INotifyPropertyChanged. It can be done either manually, or automated with this or this

https://github.com/Fody/PropertyChanged and Android background makes WPF pretty easy. At least the surface level stuff.

If you really don't want to deal with it ever again, just add this Fody - PropertyChanged NuGet package. Any class that inherits from INotifyPropertyChanged will be updated at compile time to inject in the boilerplate code for handling the property change and you never even need to think about it again. All you need to do is just add plain old properties. The only downside that some people see is that it is not immediately transparent as the change notification code is injected in during compile and is not in source code.

And GitHub is the place where employees of billion dollar companies pester unpaid maintainers because they won’t support a 12 year old version of .NET

https://github.com/Fody/PropertyChanged/issues/270#issuecomm...

If you need more info, check the docs https://github.com/Fody/PropertyChanged