Free, but now I'm having harder time convincing myself not getting RG35XXSP or a similar device.
08.03.2026 14:58
👍 1
🔁 0
💬 0
📌 0
Free, but now I'm having harder time convincing myself not getting RG35XXSP or a similar device.
This first big purchase I made after getting my first job and saving for quite some time was a stereo system with Denon PMA-710AE and Klipsch RB-61. The design is timeless.
www.denon.com/en/product/a...
Music making and Hi-Fi gear is my weakness. Look at this beauty.
www.arturia.com/products/har...
polyend.com/tracker-mini/
www.roland.com/global/produ...
korgusshop.com/products/kao...
The performance expectations from Go are not the same as from Rust/C/Zig. Generics in Go are not zero-cost in some cases. I also wouldn't mind if enums in Go were just syntactic sugar over interfaces and structs, even with some boxing involved.
It's baffling to me that Go got generics before enums. Enums is the biggest thing I miss when I have to jump from Rust to Go.
Manhattan ferry today
Relative cost-performance evolution of SPECint
If you are running CPU-bound workloads in the cloud and are not using the latest ARM instance types, you are losing money www.cs.cit.tum.de/fileadmin/w0...
I've posted my latest recap of the world of databases: www.cs.cmu.edu/~pavlo/blog/...
All the hot topics from the last year:
• More Postgres action!
• MCP for everyone!
• MongoDB gets litigious with FerretDB!
• File formats!
• Market movements!
• The richest person in the history of the world!
Back to skis after 15 years of snowboarding. Can't decide between High Anxiety Adios.
Is that Analogue 3D? How is the CRT emulation on a modern TV? I tried emulating N64 on a Steam Deck recently, most games didn't age well, upscaling doesn't help much.
"I simplified tx: Mutex<Option<mpsc::Sender<ScheduledTask>>> to tx: Arc<Mutex<Option<mpsc::Sender<ScheduledTask>>>>."
Claude, are you sure?
AI-assisted coding feels a lot like a mix of management and coaching junior engineers, except you are coaching the LLM instead of a person.
Rust database developer starter pack:
- Arc<Mutex>, RwLock, Ouroboros, ArcSwap
- "Is atomic::Ordering::Relaxed enough here?"
- Iterator borrowing from itself
- "Polonius is not really ready for widespread use"
- Tokio async disk IO is just blocking IO in a thread pool
- tokio-uring: "Dead or dying?"
I haven't looked into this myself, but I know other engineers at Datadog did. The performance issue is discussed here github.com/golang/go/is... There is a workaround go-review.googlesource.com/c/tools/+/68... but it breaks some repo-wide features like "Find all references".
The whole "Zed is fast" thing doesn't really hold up when the language server is the bottleneck.
There is one major issue with Zed I noticed in two months, which is not directly Zed's fault: a large Go monorepo at work makes gopls slow, occasionally pinning a single CPU core to 100% for a few minutes. IntelliJ doesn't use gopls and didn't have that problem.
It's happening "We've noticed that your IntelliJ license has been inactive for more than 60 days".
MMAP is incredibly fast when the dataset fits in memory, but it slows to a crawl when it doesn't, especially if the workload is mostly random point lookups. Speaking as someone who built an MMAP-based key-value store before :) Obligatory paper from @andypavlo.bsky.social db.cs.cmu.edu/mmap-cidr2022/
Just got cured ham I bought in duty-free in France confiscated at the US border 🤦♂️apparently you can't bring it www.help.cbp.gov/s/article/Ar...
These pictures unlocked some deep memories. I had a Tenchu 2 CD as a kid. The game was all right, far less time played compared to FFT, FF8, MGS2, CoolBoarders 4, and Tony Hawk's Pro Skater 2.
Using uv with inline dependency declarations is a gamechanger for Python scripts docs.astral.sh/uv/guides/sc...
Added a few Mikkeller prints - exactly what the kitchen was missing.
Zed being VC-backed concerns me a bit, but I don't use any of the AI and collab features in the IDE and there is now a privacy-focused fork.
I switched to Zed a few weeks ago and it has been a better experience for both Rust and Go compared to IntelliJ. It's very unlikely I'll renew my IntelliJ license.
JetBrains IDEs have gone downhill in recent years. IntelliJ went from working almost flawlessly for Rust and Go to often having issues to the point where the IDE becomes unusable. I'm not sure how they are going to survive with free alternatives getting pretty good.
Would it be ok to test every bit of a bitset in a loop like Claude Code suggested instead of calling Count (POPCNT under the hood) if it's not in the hot path? Yeah, but should I commit this code willingly when it's possible to do better in both performance and code complexity?
Out of curiosity I attempted a "100% AI generated PR" with Claude Code. It was very tedious. You either have to do a lot of handholding, which makes the whole process net negative, or you have to lower the quality bar, which can be fine in some cases.
$7 for an iced latte?! Specialty beans from B&W and Onyx Coffee suddenly don't sound expensive.
static const uint32_t kMaskDelta = 0xa282ead8ul; // Return a masked representation of crc. // // Motivation: it is problematic to compute the CRC of a string that // contains embedded CRCs. Therefore we recommend that CRCs stored // somewhere (e.g., in files) should be masked before being stored. inline uint32_t Mask(uint32_t crc) { // Rotate right by 15 bits and add a constant. return ((crc >> 15) | (crc << 17)) + kMaskDelta; }
This piece of code in RocksDB caught my eye. The exact same snippet exists in Snappy and many other projects if you search GitHub for the magic constant. I was curious what "problematic" means exactly. After some digging TIL CRC(A + CRC(A)) is always the same constant, regardless of A.
Might be a naive question, why did Go manage to avoid introducing colored functions, but Python didn't? Is there something fundamental in Python that doesn't allow what Go does?
