I don't know how you concluded that nothing can beat C because Go is most of the times slower.
You can see it has pretty similar performance for a problem [0] pretty similar to yours.
[0] http://benchmarksgame.alioth.debian.org/u64q/revcomp.html
Looking at that benchmark that tiny difference in performance would have have been very magnified in my use case.
Though I will concede that it is possible that while slower it might still max out disk I/O and once the bottleneck isn't RAM or CPU it doesn't much matter what language you use.
And based on that, Rust does beat C.
That is something I have not done in Go and is good to know. But I could be wrong on this one, I have no idea how Go buffers are performance optimized but reading a character from a C array is one CPU instruction... it feels intuitive that in Go just the fact the extra layer of abstraction is added on top means it will be more instructions on the CPU.
But that is just a gut, I have not tested it.
Which in my use case would make a big difference over time.
But my intuition also tells me that it would still max out disk access in Go with modern CPUs.
Edit:
I should mention that my use case was to processes as many gigs of files on as cheap an AWS server as possible while maintaining a very strict SLA on how fast processing should be (the data became obsolete in hours and when we tried higher level languages the data was obsolete before a single file could finish). So I was trying to squeeze out as many CPU cycles as possible.
I should also mention that Go didn't even exist yet in a stable state when I did this project.
Sorry if it's a naive question. My experience with C is limited.
90% of your program performance is going to be dominated by cache usage(unless you're doing something really dumb). With C you can place things next to each other explicitly so that your prefetcher/etc is automatically pulling in the data you need to the L1 cache.
Any ref'd/GC'd language is going to make that really hard(not impossible, but you have to jump through a million hoops like sun.misc.unsafe in Java).
Look up Data Oriented Design if you're interested in this stuff, Mike Acton does a great job covering it.
Not true at all.
Oberon, Active Oberon, Component Pascal, Modula-2+, Modula-3, D, System C#, Nim all offer ways to manually control memory outside GC control, just like C and C++.
Glad to provide Modula-3 examples to any C tricks you might want to do, or in D if you prefer something more modern.
Note that I didn't say that it was impossible, just that the ergonomics of GC'd languages don't tend to focus on performance in the ways that languages with explicit memory control do.
GC systems programming languages offer exactly the same explicit control as C does, in unsafe memory blocks.
Do you want to shot yourself like C in Modula-3? Declare a variable as UNTRACED REF, 100% like a C pointer.
Do you want a C union? Declare a tagged RECORD type.
Do you want a packed record to fill you cache line? Compiler alignment pragmas.
Allocation of value types on the stack or global memory section? Great, it is the default allocation type.
Bit fiddling to prepare a statically allocated buffer for a DMA transfer? UNSAFE code section.
Yet you just talked past my point to give some sort of soliloquy about Modula-3.
It doesn't matter how those languages died, it just matters that they did. The ecosystem and number of people who know how to write a language is almost, if not more important than the language when it comes to shipping software.
We should not think of Java when comparing system programming languages with GC against C.
Yes, the languages you mention meet all the technical requirements(congrats, here's your 10 internet points) it doesn't matter if I can't find people who know how to write it.
Since you seem to want to avoid talking about anything I raise I don't think it's productive to continue this conversation.
For example, all the work with System C# done in Midori has been being applied to C#, with .NET Native, ref returns, local ref variables, value tuples, regions with disabled GC, memory slices, with a few more down the roadmap, like effectively manual memory management presented at OOPSLA 2017.
Or the ongoing @nogc and BetterC improvements in D, Wallmart, EBay, Netflix, Remedy Games among many others, seem to be able to find people that know how to write it.
All it takes is 4-5 of these and now you're incurring performance hit of ~1ms which gets you into SSD territory[1].
As always, profile before making these optimizations but the OP was asking why something like this isn't possible in managed languages.
[1] https://arstechnica.com/information-technology/2012/06/insid...
For instance, I had a ETL program I was writing to process 100+ GB files. I pre-allocated all the memory I needed for exactly one row of data and immediately printed out the data when it finished that row (stream style).
The entire program processed 100 GB with lightning speed in less than 1K of memory. Maxing out the performance of the disk.
Best of all, I only had to free my memory at the end. Completely safe. No danger of double freeing and no extra memory allocation at all. Literally a dozen mallocs at the start and a dozen frees at the end.
Could I do that in Go? Sure. Would it have as optimized memory access? Maybe... but probably not. And C my entire program was 200 lines of code and absurdly fast.
Don't get me wrong, I love Go. I write programs in Go often. But for simple apps where the code can fit in a single file nothing can beat C. No bloat, no extra memory operations, and a code optimizer that has been being optimized for 30+ years. Go's code optimizer is not even close yet from what I can tell.