|
|
|
|
|
by happy_dino
4737 days ago
|
|
Yeah, let's use a memory unsafe language, handle memory management by hand and just completely ignore the fact that no human being has ever managed to consistently write bullet-proof code in it. Using software which automates memory management, engineered by the brightest minds on this topic, is for hipsters, right? I guess you also roll your own crypto and implement stuff in assembler “for performance”? |
|
Sometimes you need performance or there are other constraints, in which case your choice of language is very limited.
Automated memory management works, but not all the time. And how about other resources? How you make sure your mutex gets released? Add a comment "please don't forget to release this one"? How about file handle, temporary file, serial port, DMA, GPU, network port and other limited resources?
BTW, I think most of the brightest minds you mention use C or C++ on daily basis. :)