c: *bloats memory allocation with size information, cause stupid ass programmer can't keep track of a number*
stupid ass programmer: *still has to keep track of the size to be able to use the memory in any meaningful way*
🇳🇱
@namark the ineffiencies in raw C are a legitimate problem and why, particularly when it comes to memory management, things like Java can be 40x faster or more out of the box.
Slated memory allocation in C is ultimately the way to go but since its not built-in a lot of programmers dont do it.
That said nothing stopping someone from coding up C properly and making sure they do exactly that. I just wish more coders did.
benchmarksgame-team.pages.debi…
and it's just comparison with C++ which is slower and fatter than well-coded C.
you may look for any other performance comparisons but they all are the same and performance in C is usually taken as a primary measurement unit for performance for other languages.
and yes, writing in C demands brains. no-brainers have no chances with C.
That doesnt remotely address what I specifically said now does it. I never said C cant be made to be as fast as Java. I said out of the box memory allocation in java is over 40x faster than C (using malloc), this is fact. Slkated memory allocation in C can get around this but is mor work for the coder, which is fine, and as such with additional work C can be as faster or faster than java.
