I like C but not its syntax

Why hasn't anyone made C that doesn't look like dogshit?

>>22
Also ugly and stupid. Why does the return type come before the function name? Why do I have to visually fish the line to get the fucking name of what's being declared?

def func_name(type1 arg1, type2 arg2): ret_type { ...

would be much better.

>>22
Another thing that's wrong with C's syntax is that the "pointer" operator at the type level is the same as the "dereference pointer" at the value level. Because of that I always want to throw up when I see C code. These are two fucking opposite operations, who had the idea to denote them with the same (*) sign? Fucking idiots.

Also the array syntax is stupid. Why is it int arr[] if it's not an int? It's an array of ints, the [] needs to go to the type, ya incestuous drunken faggots. Hey, it's equivalent to int* arr (at least in function arguments), so why does the * go to the type if the [] goes to the identifier? Fucking disgusting.

>>23
Personally, it looks better with the type before, but it's harder to parse. I'm not sure why they did that. I wouldn't, in a language I made.