Explore >> Select a destination
|
You are here 
|
patshaughnessy.net | ||
| | | | |
www.brandons.me
|
|
| | | | | Lately I've been seeing lots of anecdotes from people trying to get into Rust who get really hung up on strings (&str, String, and their relationship). Beyond Rust's usual challenges around ownership, there can be an added layer of frustration because strings are so easy in the great majority of languages. You just add them together, split them, whatever! They're primitives that you can do whatever you want with. For someone who's only ever known this mental model (which is to say, never worked much with... | |
| | | | |
craftinginterpreters.com
|
|
| | | | | [AI summary] The text provides an in-depth exploration of string handling and memory management in a programming language, focusing on dynamic allocation, performance considerations, and Unicode encoding challenges. It discusses the trade-offs between different string encodings (ASCII, UTF-8, UTF-16, UTF-32) and their implications for memory usage and performance. The text also touches on the complexities of representing and manipulating strings in modern programming languages, highlighting the need for flexible and efficient data structures to support Unicode and internationalization. | |
| | | | |
mtlynch.io
|
|
| | | | | Updates about my life and what I learn about creating software | |
| | | | |
www.da.vidbuchanan.co.uk
|
|
| | | [AI summary] The CTF writeup details the process of solving a cryptographic challenge involving AES key recovery through side-channel attacks. The key was recovered by analyzing timing leaks from the AES decryption process, specifically the doSboxInv function's execution time. The recovered round 10 key was then used to invert the AES key schedule to obtain the original encryption key, which was the flag. The writeup also discusses the challenges of directly recovering the original key due to timing noise and the importance of using statistical correlation to identify the correct key. | ||
