freeing memory for running programs is terrible idea, theres a myriad of reasons why everyone avoids it unless its some super optimized game engine thing
Rust
Noah Cruz
Thomas Ramirez
...
Ryder Sanders
C is garbage collected. Try allocating more memory than your machine has. Does it crash? No. C is garbage collected.
Grayson Hughes
Memory is allocated in a lazy fashion. Allocate more memory than your machine has and then write 1 byte to each page and it will crash.
Blake Sanchez
the function free is too hard :,(
Anthony Baker
that is literally the lowest paying career path in software development
that used to be one of the highest paying career paths last I checked
you can actually use both retard
Jason Ortiz
Still better than you trivial c faggots.
Only if you are the 0.001% of contractor
Yeah you can shit and piss at the same time
Carson Collins
You can tell the kernel not to overcommit tho. If you do that malloc will return 0 when you're out of memory.
Tyler Murphy
What I love about Rust is the core language’s notion of guaranteeing memory safety (akin to what you’d get from a garbage collector) without an actual garbage collector, and all the performance benefits that entails for any sort of real time application where random pauses and stutters are not okay.
I also like that there are no nullable pointers (sum types are used instead). Seriously, nullable pointers need to die already (except for limited contexts like “unsafe” blocks).
What I don’t like about Rust is a language that is perhaps too complicated in ways that are unnecessary (C++ is way more complicated, but for “legacy” reasons — Rust is a fresh start and has no such excuse), poorly designed “ergonomics” around their borrow checker stuff, vague and unhelpful error messages, and last but not least: that awful SJW CoC.
It’s been getting better in some ways, but worse in others — particularly, nasty compiler bugs that will segfault your completely correctly written program, bugs where the borrow checker fails, etc. And to top it off, their management seems kind of lackadaisicle/dispassionate about even prioritizing fixes for these.
They’re more interested in their future-looking rewrite and research projects than actually fixing bugs. And of course, if you tell them that’s a really stupid way to manage a programming language, they’ll ban you for intolerance and “toxic meritocracy” via their CoC.
Josiah Phillips
Please tell me that's not an actual quote.