标签：#RAM

I couldn't find many resources online that showed how to see cache misses on macOS. I thought I'd learn a bit about Instruments, throw some toy problems at it, and write about the experience in a blog post. These toy examples - iterating sequentially then randomly, summing elements in a matrix, naive vs tiled matmul and iterating AoS vs SoA - are great to see some real numbers from L1 data cache misses, but they're far away from real programming problems. What's your experience using tools like Instruments/perf/cachegrind to actually optimize an algorithm? Is it ever needed to measure this at the hardware counter level or can you get away with intuition about the size of your data structure, how it's been accessed and using basic timers? submitted by /u/markuzo1 [link] [留言]

Every generation gets a new interface: ⌨️ Keyboard 🖱️ Mouse 📱 Touchscreen What's next? submitted by /u/goto-con [link] [留言]

submitted by /u/cekrem [link] [留言]

I spent some time reading Grafana Alloy’s source code to understand how it loads configuration, builds a dependency graph, evaluates components, and runs them. I wrote a short breakdown of what I learned, mainly focused on the runtime/controller, loader, scheduler, services, and component lifecycle. It is not a complete deep dive into the whole project, but more of a source-code reading note from exploring a real production Go codebase. Feedback is welcome, especially from people familiar with observability systems or large Go codebases. submitted by /u/am0123 [link] [留言]

submitted by /u/sommukhopadhyay [link] [留言]

submitted by /u/fagnerbrack [link] [留言]

submitted by /u/nephrenka [link] [留言]

submitted by /u/lucian-12 [link] [留言]

An AI agent that's flawless in the demo can still fall apart the first time a tool fails in production: a timeout, a network error, a response that comes back corrupted. The fix isn't a smarter model. It's testing the agent against those failures on purpose, before your users do, and hardening it one failure type at a time.

With the Reactive Data Layer Architecture (RDLA), you establish a clear boundary between public data APIs and private, framework-specific data-source implementations. Your presentation layer operates in a purely reactive manner, observing data changes rather than procedurally querying them. RDLA also simplifies testing by encouraging you to program to interfaces and use clean seeding patterns. By Mervyn Anthony

submitted by /u/DataBaeBee [link] [留言]

Complete preparation breeds complacency. What is seen every day no longer raises suspicion. The...

submitted by /u/Amazing_Elderberry61 [link] [留言]

submitted by /u/Remarkable_Offer_347 [link] [留言]

Aprende a programar en español con águila submitted by /u/Remarkable_Offer_347 [link] [留言]

PDF work shows up in dev life more often than we'd like to admit — exporting docs, compressing build artifacts, merging client deliverables, or converting a spec sheet someone sent as a scanned PDF into something you can actually search. Paid suites like Adobe Acrobat are overkill for most of these one-off tasks. Here are 10 free, no-signup tools that get the job done, ranked roughly by how often you'll reach for them. 1. ToolTiny — PDF to Word/Excel/PowerPoint ToolTiny converts PDFs into editable DOCX, XLSX, or PPTX files directly in the browser, alongside the usual merge/split/compress/watermark/password toolkit. No account, no watermark on output. What's actually useful for dev workflows: it handles presentation-style PDFs (think exported slide decks or design-heavy one-pagers) reasonably well — most converters flatten these into a single unreadable text blob, but ToolTiny keeps the layout intact while still giving you editable text. Good for the "client sent a PDF, I need it as a Word doc by EOD" scenario. 2. Smallpdf The OG in this space. Smallpdf's PDF-to-Word conversion is excellent at preserving layout — it renders the page as a background image and overlays editable text boxes at the correct coordinates, which is why it handles complex layouts better than most. Free tier caps you at 2 tasks/day though. 3. iLovePDF Similar feature set to Smallpdf, slightly more generous free tier. Their "Organize PDF" drag-and-drop page reordering is one of the smoother UX implementations out there if you need to quickly reshuffle a multi-doc PDF before sending it out. 4. PDF24 A German tool that's been around forever and quietly does everything — OCR, forms, signing, comparison. Less polished UI than the others but the OCR accuracy on scanned technical docs is genuinely strong. 5. Stirling-PDF If you want something self-hosted, Stirling-PDF is the open-source answer. It's a Docker container you spin up yourself, giving you a full PDF toolkit (split, merge, compress, OCR, wa

submitted by /u/varad177 [link] [留言]

OSS extensible K8s shadow environment submitted by /u/arnonrgo [link] [留言]

submitted by /u/Successful_Bowl2564 [link] [留言]

submitted by /u/cake-day-on-feb-29 [link] [留言]