News for hackers. Stuff that matters.
Re:Shift to Memory-Safe Languages Gains Momentum by mark_l_watson on Wednesday December 07, 2022 @10:37AM (#33895556)
They mention several languages besides Rust that are also much safer than C/C++. 59% of C/C++ programs have vulnerabilities while only 10% of Python do. I wonder: are the Python vulnerabilities mostly from external C libraires? I was trying think of how pure Python can be memory corrupted.

A few weeks ago I read a tutorial on writing Rust Python libraries, and it looked cool. I have just started publishing some of my libraries to PyPi.org but so far what I am writing is pure Python.

Re:Shift to Memory-Safe Languages Gains Momentum by repastat3hmasta on Wednesday December 07, 2022 @10:28AM (#33895435)
Kinda makes you wonder if the OpenAI team is rapidly dealing with memory leaks caused by maliciously formed prompts to ChatGPT right now. Or maybe they wrote it in a memory-safe language?
Re:Shift to Memory-Safe Languages Gains Momentum by jjgreen on Wednesday December 07, 2022 @10:30AM (#33895461)
I doubt it, the GCs would give it a stutter.
Re:Shift to Memory-Safe Languages Gains Momentum by foxyv on Wednesday December 07, 2022 @10:37AM (#33895562)
If you are doing it right, on multi-threaded computers, modern GCs will usually not result in freezes or stutter. Usually, even on older GCs, only a Full Mark and Sweep GC will cause a pause in operation. If you are seeing a lot of Full GCs usually that means that you aren't managing memory properly or have un-closed resources building up.
Re:Shift to Memory-Safe Languages Gains Momentum by jjgreen on Wednesday December 07, 2022 @10:47AM (#33895684)
That was (mostly) a joke :-)
Re:Shift to Memory-Safe Languages Gains Momentum by foxyv on Wednesday December 07, 2022 @02:08PM (#33898711)
Ah! Got me!