Fuck, and I cannot stress this enough, code generators.

Yes! Fuck them! They are all crap!

Except for the ones I have made - they are amazing. But the rest are utter crap!

Fuck and I cannot fuck this enough

@hinst I also don't get to...

Wait, nevermind, misread your comment.

I dunno, are we counting the likes of c++ templating/metaprogramming as code generation? They're complicated as all hell but they do have a use.

@atheist macros are evil, but no this isn't about templates and such.

This is specifically about custom meta language into C/C++/whatever other language translation.

I had a very frustrating afternoon with one that's supposed to generate a HTTP/REST server for me.

@LotsOfCaffeine yeah, but macros aren't idiomatic c++ 😉

I think there's *almost* a use, for stuff like api design. When there are different languages, having something like "json schema to class declaration in language x" has a certain appeal (mostly if you're dev on both front and back end), but I think a lot of front end is evil.

@netikras this tbh

I mostly only trust code generation that I wrote for my specific purposes. Generic solutions are never specific enough

@atheist it can be useful if it, you know, worked properly :/

one PR and two issue reports today

Depends on what someone wants to achieve.

I tend to write DTO generators when I had to deal with specs from arsehole clients.

Small python script in git repository. Git repository to proof that the clients are useless monkeys who piss on the keyboard to describe their wishes... Without the pissing I couldn't explain the fuckton of spelling / grammar and logical mistakes.

Was always interesting to look in the git repository and to think of how much money we just made by the stupidness on client side.

Some export / import APIs needed 6 months plus till they were properly defined...

Hateful 6 months plus.