• 0 Posts
  • 53 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle













  • Imagine a website where EVERYONE sees the exact same content. You could just calculate that content once, save the result, and give everyone that pre-calculated result. This is called caching (roughly speaking).

    Now imagine the other extreme: NOONE sees the same content. That means you have to do your (comparatively) expensive calculations every single time. That requires a lot more compute power, esp. if you want to maintain a decent speed.

    Most websites aren’t entirely one or the other, but in general anything customizable will make things just a little less cache-able, and therefore everything a little more compute-intensive. Blocking is one of those customizations.



  • r1veRRR@feddit.detoProgrammer Humor@programming.devGolang be like
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    11 months ago

    It’s better than “invisible” exceptions, but it’s still the worst “better” version. The best solution is some version of the good old Result monad. Rust has the BEST error handling (at least in the languages i know). You must handle Errors, BUT they are just values, AND there’s a easy, non-verbose way of passing on the error (the ? operator).


  • It’s absolutely true in practice. CEOs have gotten sued for not acting in the shareholders best interests.

    And in relation to the original comment I replied to, are you truly saying that companies, esp. public companies, are not, FOR ALL INTENTS AND PURPOSES, beholden to making money for the shareholders? Any “nice” company will make less money, will not compete well, will then fail or be bought out by the less nice, more profitable company.