"Nice" and "garbage collected" do not belong in the same sentence insofar as people continue to build stop-the-world garbage collectors.
Replace "company" with "community", and his post can still hold up.
Funnily enough, nobody sold C as a low-level-language to us back in my day, but rather the exact opposite: A high-level-language, as you could compile standard-compliant C code on every platform having a standard-compliant implementation without the requirement of having to know about the platform specific machine code or the OS it runs on. It was the Java of our time.
This is funny because it's consistently unreliable on non-Element clients. Coincidence?
Tabs are allowed in zig now. Unused variables are an error in zig though, but this makes sense considering that without that you could easily miss that a function returns an error and not handle it. Unused parameters make less sense, but if you change the name of the parameter to _ then it will be ignored.
we have known how to build nice incremental collectors since like 1970, so there are many nice garbage collected languages out there
i am sure it will be completely reliable and usable the entire time as well
...and even that wasn't true when the size of int, for example, was never guaranteed.
...and nobody uses any of them, instead using babby's first garbage collector for their language. None of this matters, of course, as reference counting is superior, and RAII superior still. Jannies masquerading as software engineers need to drop their keyboards and go take up their true calling.
Fat-ass LOL. Have you ever even played the game?
Your "Mark 2 Piece of Shit(tm)" can handle GTA V at 80fps, dickhead.
Did an absolutely tiny project last year and had someone very inexperienced trying to help with it. He kept using AI despite my insistence not to. What difference did AI make? Well it took him from hitting a wall and asking me how to do something, to producing working but wrong code that I had to continuously keep an eye out for and which took ages to unpick when I did. Just mistaken or unscalable or a completely inconsistent approach with other code. The guy would cheerfully go off, type something into an AI and check the results in. I'm not exaggerating when I say his help probably more than doubled the amount of effort the project took me.
That's Rugby vs. American Football. The latter actually has more and more severe injuries statistically, largely because with the helmets and pads people are less cautious and impact each other harder.
unwrap() is one of the few designated "shut up compiler, I know this is correct and doesn't need checks" functions. Normally you'd have to handle both cases via pattern matching or a different function. It's still memory-safe, type-safe, and you do technically handle the error, you just handle it by aborting the program.
It's not a low-level language, it is a high-level language that was designed to be portable at a time where systems varied a lot and compilers were simple. Though, you can use it for low-level / non-portable code if you really want to.
They are guaranteed to be at least a minimum size. It is part of what makes it portable. Also guaranteeing consistent behavior and fixed width words on systems where the native word size is some schizo shit like 17 bits probably would complicate the compiler and make code needlessly slower.
true, c is really only low-level insofar as it doesn't need quite as big a runtime as other languages and its semantics are pretty close to the isa (e.g. everything is really just a number and your array is really just syntax sugar for address+offset)
it also expects a large amount of easily usable stack space to be available, which is why languages like glsl are popular for gpus
I mean you can write iso-c for bare metal that isn't really runtime based at all, most languages don't have that
Orange language bad