>>103282800
code that nobody can read is objectively less useful; unreadable code restricts who can contribute
everyone can read C and most C++, so we should stick to those
>they're piss-scared of making a singular mistake
but that's the correct attitude
only the White man cares for the consequences of passing off flawed code as good enough
who do you want writing your Boing software: some jeet trying to hit his 2,000 line KPI today, or the White man who spends days simplifying and checking the code?
>big bad basic pointer arithmetic
not only is it not hard, pointer arithmetic can make it easier to write correct code:
// jeet style
// it's very easy to slip up, and the compiler cannot help. It's particularly easy to make mistakes when passing things to subroutines: a pointer is a single thing; an array and an index must be believed to belong together in the receiving subroutine.
// https://doc.cat-v.org/bell_labs/pikestyle
parent->link[i].type;
parent->link[++i].type;
// hyperborea style
// with pointers, there's only one thing to advance
lp->type;
(++lp)->type;
