Personal sharing
This article explores multiple in‑memory strategies—using a simple map with timers, per‑driver goroutine management, and especially a Go‑implemented timing wheel—to identify Uber drivers who haven’t reported for ten minutes, comparing their complexities, memory usage, and suitability for large‑scale systems.
The proposal introduces a ‘?’ operator to automatically handle errors in Go, aiming to reduce boilerplate while preserving explicitness, but it raises concerns about code readability, variable shadowing, and the effort required to update existing codebases.
An in‑depth look at Go’s origins, design goals, and the trade‑offs that provoke both admiration for its simplicity in large‑scale server development and criticism over its limited generics, file‑system API, error handling, and FFI capabilities.
Using a local Go server and Wireshark, the author measured that a basic HTTPS request transmits 2,164 bytes—about ten times more than an equivalent HTTP request—revealing the bandwidth impact of TLS handshakes and suggesting when HTTP may be preferable for internal, non‑sensitive traffic.
This article explains how Go 1.24 rewrote its built‑in map with a SwissTable‑based hash table, compares it to Dolt’s SwissMap implementation, and details the underlying data structures, algorithms, and performance benefits.
This article examines typical Go memory‑leak scenarios—including unclosed files, forgotten HTTP response bodies, slice sharing, goroutine and channel misuse, improper finalizers, and outdated ticker handling—provides concrete code examples, and offers practical techniques such as using strings.Clone, buffered channels, and proper defer usage to avoid leaks.
This article explains how Go's testing/synctest experiment speeds up cache expiration tests by using a virtual clock and bubble isolation, providing code examples that reduce a five‑second wait to milliseconds while ensuring reliable concurrent test execution.
This article explains the limitations of Go's runtime.SetFinalizer, introduces the new runtime.AddCleanup function in Go 1.24, demonstrates proper usage with code examples, and highlights important pitfalls and best‑practice tips for reliable resource management.
The article critiques hollow security‑first slogans, explores the endless nature of security, the tension between security and user experience, and offers practical risk‑scoring frameworks and phrasing advice for organizations seeking a realistic balance between protection and usability.
This article explains Go 1.24's new std‑lib weak package, compares it with weak reference implementations in other languages, demonstrates its API with practical code examples, and shows how to build canonicalization maps and fixed‑size caches using weak pointers.
