Live data from Hacker News

Viewing profile — farkin88

farkin88

HN member
Joined
Tue, Mar 07, 2023, 9:31 AM UTC
HN karma
141
Public activity
24 items

About farkin88

No profile information was provided.

Recent public activity

  1. comment
    Comment #44820136

    Thanks for sharing. That's really cool.

  2. comment
    Comment #44803616

    X11's SECURITY extension was its long-forgotten stab at sandboxing: flip a bit and every client is either trusted or untrusted. It does kill trivial key-logging, but it also breaks…

  3. comment
    Comment #44782451

    Anthropic still relies on quotas (5-hour rolling + weekly coming at the end of the month) so the next step is dynamic per-token pricing. But, even with transparent off-peak rates o…

  4. comment
    Comment #44782371

    Fair point about process bloat. Just to clarify: I'm not an ADR expert nor do I personally know Harmel-Law. Just deriving insights from his blog post that I linked to earlier becau…

  5. comment
    Comment #44781729

    The prod-readiness concerns are fair, but mcp-use fills a real gap in the MCP stack: orchestration across many servers with far less boilerplate than the official SDK. Even if the …

  6. comment
    Comment #44781083

    That robustness-vs-throughput trade-off is such a staple of PDF parsing. My guess is that the new path is slower because the recovery scan now always walks the whole byte range and…

  7. comment
    Comment #44780993

    There are so many external links, it's easy to get lost in this article. Look under content for the section titled "1. A Thinking and Recording Tool: Decision Records." It's under …

  8. comment
    Comment #44780855

    Great rundown. One thing you didn't mention that I thought was interesting to note is incremental-save chains: the first startxref offset is fine, but the /Prev links that Acrobat …

  9. comment
    Comment #44780755

    Solid advice on clarity and editing. The only gap is what happens after the doc is approved? Without upkeep it decays into "design archaeology." A few years ago, Andrew Harmel-Law …

  10. comment
    Comment #44780528

    For sure. Feel free to copy/paste it. Great blog by the way. Will keep any eye out more of your posts.

  11. comment
    Comment #44780384

    Type safety for API calls is huge. I haven't used ts-rest but the compile-time validation approach sounds solid. Way better than runtime surprises. How's the experience in practice…

  12. comment
    Comment #44780346

    What a dual-publishing nightmare. Someone had to break the stalemate first. 90% size reduction is solid even if Node bundle size isn't as critical. The streams thing sounds messy, …

  13. comment
    Comment #44780304

    Ky is definitely one of the libraries moving in that direction. Good adoption based on those download numbers, but I think the ecosystem is still a bit fragmented. You've got ky, o…

  14. comment
    Comment #44780275

    Yeah, that's the classic bundle size vs DX trade-off. Fetch definitely requires more boilerplate. The manual response.ok check and double await is annoying. For Lambda where I'm op…

  15. comment
    Comment #44780039

    Undici is solid. Being the engine behind Node's fetch is huge. The performance gains are real and having it baked into core means no more dependency debates. Plus, it's got some gr…

  16. comment
    Comment #44779872

    I think that's the sweet spot. Native fetch performance with axios-style conveniences. Some libraries are moving in that direction, but nothing's really nailed it yet. The challeng…

  17. comment
    Comment #44779832

    Interesting to get a library author's perspective. To be fair, you guys had to deal with the whole ecosystem shift: dual package hazards, CJS/ESM compatibility hell, tooling change…

  18. comment
    Comment #44779759

    Totally get that! I think it depends on your context. For Lambda where every KB and millisecond counts, native fetch wins, but for a full app where you need robust HTTP handling, t…

  19. comment
    Comment #44779715

    Right?! I think a lot of devs got stuck in the axios habit from before Node 18 when fetch wasn't built-in. Plus axios has that batteries included feel with interceptors, auto-JSON …

  20. comment
    Comment #44779650

    Big takeaway for me: the win isn’t better prompts, it’s semantic guarantees. By proving at the bytecode level that the pixel loop is side-effect-free, you can safely split it into …

  21. comment
    Comment #44779555

    I've been burnt by performance gates on GitHub Actions. One random timing spike and the whole PR turns red. The coefficient of variation math here nails why: GitHub Actions shows a…

  22. comment
    Comment #44779431

    Even though tokens are getting cheaper, I think the real killer of "unlimited" LLM plans isn't token costs themselves, it's the shape of the usage curve that's unsustainable. These…

  23. comment
    Comment #44779342

    The killer upgrade here isn’t ESM. It’s Node baking fetch + AbortController into core. Dropping axios/node-fetch trimmed my Lambda bundle and shaved about 100 ms off cold-start lat…

  24. comment
    Comment #44779063

    I really like the tiny-lib approach. One thing that would make it even more useful in larger systems: OpenTelemetry hooks is if each call to formatMCPError() could optionally: star…