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

It's actually a great resource. The glossary covers all these issues, except for Rust, which the site content predates. It tends to use more academic terminology instead of the current industry terminology, but the academic terminology is often more precise anyway. Yes, it's opinionated in favor of GC, but that's a perfectly defensible position (which may sound odd coming from me as a Rust developer, but I actually like GC in many—just not all—circumstances).

RAII is covered under "smart pointer": https://www.memorymanagement.org/glossary/s.html#term-smart-...

Stack allocation is here: https://www.memorymanagement.org/glossary/s.html#term-stack-...

Object pooling is covered under "segregated free list": https://www.memorymanagement.org/glossary/s.html#term-segreg...

Multithreaded GC is covered under "parallel garbage collection": https://www.memorymanagement.org/glossary/p.html#term-parall...



I disagree. A few short more or less related entries in the glossary is not really "covering". A paragraph on smart pointers that conflates the concept with reference counting is certainly not covering RAII. None of these adequately address the deficiencies I mentioned.


That paragraph on smart pointers doesn’t have anything to do with RAII - it’s not even accurate concerning C++ smart pointers, where the standard ‘has a single owner’ smart pointer doesn’t use ref counting, it uses RAII.


Probably the resource is older than 2018, and is taking aim shared_ptr (or maybe even auto_ptr?) rather than unique_ptr.


Both unique_ptr and shared_ptr have been standard since C++11 which is also when auto_ptr was deprecated (auto_ptr is/was also not reference counted).




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

Search: