Closed jtsom closed 4 months ago
It's as alive as any other single-maintainer library 😃 I'm actively working on adding trimming & native AOT support. But this is OSS, there's no guarantees I'll keep working on it. But you can always fork it and maintain it yourself if that happens.
Hi @DamianEdwards will there be an example using RazorComponentResult in .NET 8?
@garrettlondon1 not in this repo. This is adjacent to Razor Components. Razor Components use stateful rendering in order to enable the features of Blazor but that comes with a cost (memory, processing, etc.). Razor Slices are optimized for a different set of trade-offs with forward-only, unbuffered rendering.
Just wondering if this project is still alive, or there are plans to keep it going. Looks like a very useful library and would be very useful in a furture app, but it it dies, I don't want to depend on it.
Thanks