project: remove clang-format for good

[F1F7Y]

Removes clang-format and replaces it with a code standards document. Doesn't format any files.

First commit (8a4948e) is the important change.

Second commit(2f02a69) just removes all the clang-format comments.

[GeckoEidechse]

My take on this is that we should definitely have the code standard documentation merged ASAP but I disagree with with removing clang-format.

If the formatting is shit (it is), the clang-format config should be adjusted instead. Maybe we could find the settings that are close / the same as valve source engine so that comparing diffs is easier?

[GeckoEidechse]

In fact, @F1F7Y can you make a PR with just the code standards and I'll merge it ASAP.
(Alternatively I'll make it but then I'll get co-author on it hehe :P)

[F1F7Y]

My take on this is that we should definitely have the code standard documentation merged ASAP but I disagree with with removing clang-format.

If the formatting is shit (it is), the clang-format config should be adjusted instead. Maybe we could find the settings that are close / the same as valve source engine so that comparing diffs is easier?

My take on it is if we remove all the annoying settings from clang-format we're just left with a glorified .editorconfig. If we want programmers to format the code the way we want we should format the code base so they have good reference. Just trying to perfect configs doesn't help.

[F1F7Y]

To expand on it a little more when I write code I try to format it the same as the codebase. PRs having shit formatting isn't caused by the lack of auto formatting but rather by the lack of a well formatted codebase ( and written down rules :3 ).

You could argue that just making clang format less strict would work, which it partially would, but I'd argue at that point it just becomes an annoyance. I don't care whether you put a space after an if statement, I care that you wrote readable code with good names and documentation and clang format can't enforce that.