this post was submitted on 28 Nov 2023
599 points (97.9% liked)

Programmer Humor

32710 readers
89 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] mordack550 16 points 1 year ago (2 children)

Your assumption that "using reflection means the code is wrong" seems a bit extreme, at least in .Net. Every time you interact with types, you use reflection. Xml and Json serialization/deserialization uses reflection, and also Entity Framework. If you use mocking in test you are using reflection.

We have an excel export functionality on our sites that uses reflection because we can write 1 function and export any types we want, thanks to reflection.

[–] [email protected] 2 points 1 year ago

Modern .NET is reducing dependence on reflection. System.Text.JSON and other core libraries have leveraged source generation to produce AOT + trim friendly, reflection free code. But yeah, it's not a taboo like say dynamic, it's perfectly normal to use reflection in idiomatic C# code.