News for hackers. Stuff that matters.
Re:My personal C coding style as of late 2023 by SkeuomorphicBee on Monday October 09, 2023 @10:44AM (#37820966)
> Like, using u8 or i32 instead of the standard uint8_t or int32_t might save a few keystrokes [...]

It is not about saving keystrokes, it is about reducing sensory load when reading it.

Sorry, I know it may sound like I'm splitting hairs, but every single time when the argument of verbosity vs conciseness in programing languages comes around, this "keystrokes" argument is thrown and it is extremely flawed. The core belief that conciseness is only better for faster typing but that verbosity is somehow always better than conciseness for reading is just plain wrong and we should stop using it. And yes, verbosity has some advantages for reading comprehension, but so does conciseness, no side is a clear winner, it is all about the different compromises.

Re:My personal C coding style as of late 2023 by __loam on Monday October 09, 2023 @06:28PM (#37826248)
I think you completely missed the point of his comment. C isn't a new programming language. There are well worn conventions and making custom types because you don't like them is like forking your own custom dialect nobody can understand for very little benefit.
Re:My personal C coding style as of late 2023 by tuatoru on Tuesday October 10, 2023 @04:47AM (#37829807)
No experienced C programmer is going to misunderstand u8 in a declaration.