• kamstrup@programming.dev
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    6 months ago

    The context package is such a big mistake. But at this point we just have to live with it and accept our fate because it’s used everywhere

    It adds boilerplate everywhere, is easily misused, can cause resource leaks, has highly ambiguous conotations for methods that take a ctx: Does the function do IO? Is it cancellable? What transactional semantics are there if you cancel the context during method execution.

    Almost all devs just blindly throw it around without thinking about these things

    And dont get me startet on all the ctx.Value() calls that traverse a linked list