Ballin
01 Aug 2011
Share on
Keep Reading 🚀
-
Disallow code usage with a custom `clippy.toml`
I recently discovered that adding a
clippy.tomlfile to the root of a Rust project gives the ability to disallow a method or a type when runningcargo clippy. This has been really useful. I want to share two quick ways that I’ve used it: Enhancingstd::fscalls viafs_errand protecting CWD threadsafety in tests. -
Upgrade to Puma 7 and Unlock the Power of Fair Scheduled Keep-alive
Puma 7 is here, and that means your Ruby app is now keep-alive ready. This bug, which existed in Puma for years, caused one out of every 10 requests to take 10x longer by unfairly “cutting in line.” In this post, I’ll cover how web servers work, what caused this bad behavior in Puma, and how it was fixed in Puma 7; specifically an architectural change recommended by MSP-Greg that was needed to address the issue.
-
Learn How to Lower Heroku Dyno Latency through Persistent Connections (Keep-alive)
Before the latest improvements to the Heroku Router, every connection between the router and your application dyno risked incurring the latency penalty of a TCP slow start. To understand why this is a performance bottleneck for modern web applications, we must look at the fundamentals of the Transmission Control Protocol (TCP) and its history with HTTP.
-
'Our app supports Markdown' and other lies apps tell
I’ll make this plain and simple: If your app does not let me read back, the character-for-character raw text I put into the editor, it does NOT support markdown.
-
Don't McBlock me
“That cannot be done.” Is rarely true, but it’s a phrase I’ve heard more and more from technical people without offering any rationale or further explanation. This tendency to use absolute language when making blocking statements reminded me of a useful “McDonald’s rule” that I was introduced to many years ago when deciding where to eat with friends. It goes something like this: