I'm cautiously optimistic. > Moving to a single .NET implementation raises important questions. What will the target framework be? Will NuGet package compatibi

I'm cautiously optimistic. > Moving to a single .NET implementation raises important questions. What will the target framework be? Will NuGet package compatibility rules be the same? [...] How does writing code for a specific architecture work? [...] We are working through these issues now and will soon be sharing design docs for you to read and give feedback on. This, however, is my biggest worry. Between runtimes, content files, analyzers, native references, asset visibility rules, etc., packaging has become kind of a mess. I'd love to see a move away from monolithic packages, but IDK if that's on the table. Fingers crossed.