Explore >> Select a destination
|
You are here 
|
without.boats | ||
| | | | |
boats.gitlab.io
|
|
| | | | | In the previous post I said that in the second post in the series we'd talk about how rooting works. However, as I sat down to write that post, I realized that it would be a good idea to back up and give an initial overview of how a tracing garbage collector works - and in particular, how the underlying garbage collector in shifgrethor is implemented. In the abstract, we can think of the memory of a Rust program with garbage collection as being divided into three sections: the stack, the "unmanaged" heap... | |
| | | | |
v8.dev
|
|
| | | | | Orinoco, V8's garbage collector, evolved from a sequential stop-the-world implementation into a mostly parallel and concurrent collector with incremental fallback. | |
| | | | |
aykevl.nl
|
|
| | | | | An explanation of how garbage collectors work including some pseudocode how a real GC could be implemented. | |
| | | | |
paragonie.com
|
|
| | | [AI summary] CMS Airship is a secure, free software content management system (CMS) designed to provide a secure-by-default solution for online publishers. It addresses the shortcomings of existing CMS platforms by incorporating advanced security measures, such as prepared statements for SQL injection prevention, layered XSS defenses, CSRF mitigation, automatic secure updates, and cryptographic libraries like Halite. The system emphasizes user privacy, secure account recovery, and flexible access controls, making it a robust choice for developers seeking a secure CMS. | ||
