• nik9000@programming.dev
    link
    fedilink
    arrow-up
    19
    ·
    2 days ago

    It’d be fun to talk shop with the fast code in slow languages folks. I do that for a living. I remember three ways, but I’m sure there’s more:

    • “Just use a better data structure”
    • “My language is a DSL for a faster language” (Polars, Numpy, etc)
    • “My compiler is surprisingly good if I’m careful” (Julia, JVM, etc)
    • themusicman@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      13 hours ago

      Arguably “we can just put it in docker, and create an auto scaling microservice with a load balancer, behind a CDN for avg request latency” fits this group too. The hoops I have to jump through to get a good user experience on top of our shitty PHP backend are unreal

      • nik9000@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        7 hours ago

        That’s not what I was thinking but I like it! Http caching is pretty magic. Stateless nodes and easy scaling too.

        For some kinds of problems you really can’t beat varnish and friends. It’s how we have Wikipedia, after all.