Ah

I don't like code generators
Especially if they define one set architecture/design

Because surely the people who made the templates/the generator have thought of every single valid use case

Code generators are darn imperative. One subtemplate today, another tomorrow, and you somehow must follow the useless breaking updates that tell you there is already different string/magic/approach Y for doing X.

There should have been intent! But they favor fragile structures. One-off projects are doomed, definitely.

I haven‘t used code generators since the old days of C++, Java and Objective-C. Don’t miss them.

@vintprox yeah pretty much. I feel like they don't strive for a good design or architecture, but rather "it compiles lets ship it"

@Lensflare I'm doing C++ right now...

The thing that pisses me off is people use code-generators (adding another dependency to their project), then turn around and shit on C and C++ for having a code-generator built-in.

I just dont get it...

Shouldn't you just design your architecture so that you use inheritance instead of using code gens. I haven't found a need for any of that stuff since I started and was unaware of how object inheritance functions.

With proper abstractions, they're super nice to work with and very useful. Without that, absolute trash fires.

@YADU not for having them but for needing them. Unless you like writing the same boilerplate code over and over.
Yes, it is a question of architecture and code design but in general, some languages tend to require code generators more than others.

I'm straight up convinced the openapi-generator people do not test their stuff whatsoever

@Lensflare no I've specifically heard people say C and C++ macros are bad because they lead to messy code, then turn around and talk about their cool new code generator in Java that saves them so much time...