[Feature]: Remove old frameworks from NuGet.org framework pages and consider the same for EOL frameworks.

[JonDouglas]

Related Problem

No response

The Elevator Pitch

Let's consider removing old TFMs that have very low package usage nowadays in 2024:

Additionally, let's consider removing "out of support" TFMs from these pages after they have gone EOL.

Additional Context and Details

No response

[erdembayar]

@JonDouglas
What is the intention behind for this removal? is it for declutter UI? What is gate for low usage? For example tizen30 has very low download count because it has very niche use case.

[JonDouglas]

@JonDouglas What is the intention behind for this removal? is it for declutter UI? What is gate for low usage? For example tizen30 has very low download count because it has very niche use case.

At the time of doing this feature, these were still in a transition period.

Tizen probably should remain.

Other ones should be hidden for better UX now that new netX-<platform> TFMs exist for many

[erdembayar]

@JonDouglas What is the intention behind for this removal? is it for declutter UI? What is gate for low usage? For example tizen30 has very low download count because it has very niche use case.

At the time of doing this feature, these were still in a transition period.

Tizen probably should remain.

Other ones should be hidden for better UX now that new netX-<platform> TFMs exist for many

What is the intention behind for this removal? is it for declutter UI

[JonDouglas]

Declutter unsupported TFMs that have low adoption nowadays.