I like c/c++ headers because you can put the “code” in one file, and use the header file in your others where you need access to that code. And you can do that on a compile level. No need to for example compile a c# library that you’ll then use.
In c# (for example) you’ll include all the code in another file, when you just need one function. In c++ you include only all the definitions, if that makes sense.
In c# it quickly becomes a garbled mess IMO.
Sure, you can make libraries, but make libraries for every file? That’s not optimal either.
So I guess I like it as it lets you split up code on a lower level, very convenient IMO.
I like c/c++ headers because you can put the “code” in one file, and use the header file in your others where you need access to that code. And you can do that on a compile level. No need to for example compile a c# library that you’ll then use.
In c# (for example) you’ll include all the code in another file, when you just need one function. In c++ you include only all the definitions, if that makes sense.
In c# it quickly becomes a garbled mess IMO.
Sure, you can make libraries, but make libraries for every file? That’s not optimal either.
So I guess I like it as it lets you split up code on a lower level, very convenient IMO.