Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Odd how well rust seems to manage to avoid them.

C was amazing when it was introduced, but is as archaic as COBOL today. We are stuck with it because of legacy.



Amazing only to those that never looked outside Bell Labs.

Amazing was what Burroughs was doing in 1961, 10 years before C came to be, IBM RISC research in PL/S and PL.8, VAX/VMS stuff in BLISS, Solo OS in Concurrent Pascal, Xerox XDE in Mesa, ....

Those were amazing in the 60's and mid-70's.


>"C was amazing when it was introduced"

It was not amazing. It was decent particular tool for particular job. That was all about it. Same thing about Rust. There are no silver bullets laying around.


Whether you want to say it was amazing or not, it’s a legacy tool now.


What do the cool kids use to write realtime or realtime-ish software with these days? What gets used for firmware? What gets used to write kernels? What gets used when you have to interact with hardware that uses memory mapped registers?

It might be C++ instead of C for some of the above, but that doesn't make C "a legacy tool".


I’m not saying it isn’t used.

I’m saying it’s a legacy tool from the early 70’s that is absolutely terrible compared to what we could have.

Cool kids use it because there is no alternative.


It is not


Two words: Buffer overrun




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: