If you're just going to sit there doing nothing, at least do nothing correctly - The Old New Thing
devblogs.microsoft.com
How to be inert.
  • Kuinox@lemmy.world
    191·
    9 months ago

    This is exactly what the browsers have been doing for decades and why the developer experience with html/css is infuriating.

    • abbadon420@lemm.ee
      9·
      9 months ago

      It seems like a decent approach when you’re working with an existing tech stack and not some shiny new technology that has every sorted appropriately. At first I was like “just return an empty list of printers and let the user think there might be printers? Are you mad?” But than I was like “Well, that’s what I would do in an API as well”

    • epyon22@programming.dev
      32·
      9 months ago

      Html/css/JavaScript is one of the most highly compatible and prolific stacks to ever exist. I like to say that JavaScript has succeeded where Java was trying to be.

      • Kuinox@lemmy.world
        5·
        9 months ago

        They didn’t succeeded because they were good, but because they were popular.
        Browser devtools are very inferior to java/.net devtools, except the network tab from the browser, only thing the language I gave as example lack.

      • Lmaydev@programming.dev
        4·
        9 months ago

        JavaScript, until recently, was literally the only option. It’s a nightmare of a language littered with bear traps and pitfalls.

  • brisk
    111·
    9 months ago

    I’ve seen far too manny error messages claiming I did something I most certainly didn’t do. This seems like a good way to make those far more prolific.

    • Fontasia@feddit.nl
      1·
      9 months ago

      Isn’t this better to understand about what the program is trying to do, which a user really only has a passing influence on

  • zartcosgrove@beehaw.org
    31·
    9 months ago

    This seems wrong to me. Existing paradigms like try catch or returning result codes enable handling these situations gracefully and in an informed manner. Making an inert api as is suggested here means that now you have an api that doesn’t behave as expected but without an explanation why.

    “The app was probably only tested against a PC so an exception would be unhandled” means that they did not implement it well against a PC. There are a bunch of possible reasons you’d get an exception while adding a printer on a PC, and I can’t imagine that the correct behavior would be to crash whatever it is you’re doing.