Well, why not simply using the base language to create meta-data objects which describe our classes and methods?
The case against annotations
Adam Warski
1.7K13

Annotations divorce configuration from coding, data from execution, allowing for multiple realizations and augmentation of some aspect/trait/concern/…we can always make config be code and config be code…but there is a trade-off…and invariably this diminishes the value of annotations when completely abused which is probably the underlying problem for many reassessing the usage of annotations…knowing when to stop.

Like what you read? Give Autoletics a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.