Because hello is so simple you don't need complicated. When you are doing something complicated though you have to accept that it is complicated. I could concatenate all 20 million lines of C++ (round number) I work with into one file and building would be as simple as your hello example - but that simple building comes at great cost (you try working with a 20 million line file, and then merging it with changes someone else made) and so I'm willing to accept more complex builds.

▲

ho_schi 3 days ago | parent [-]

Thank you. That's right and where usually issues arise and tools challenged. If the hello worlds case starts that complicated already I'm going to being careful.

I'm eager to gather info but the weak spots of headers (and macros) are obvious. Probably holding a waiting position for undefined time. At least as long Meson doesn't support them.

Wikipedia contains false info about toolings: https://en.wikipedia.org/wiki/Modules_(C%2B%2B)#Tooling_supp...

Meson doesn't support modules as of 2025-09-11.

PS: I'm into new stuff when it looks stable and the benefits are obvious. But this looks complicated and backing out of complicated stuff is painful, when necessary.

	▲	bluGill 3 days ago \| parent [-]
		> If the hello worlds case starts that complicated already I'm going to being careful. If the tool is intended for complex things I'm not sure I agree. It is nice when hello is simple, but if you can make the complex cases a little easier at the expense of making the simple things nobody does harder I don't know if I care. (note that the example needed the -o parameter to the command line - gcc doesn't have a good default... maybe it should?)