• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle





  • tweeks@feddit.nltoProgrammer Humor@lemmy.mlWhoops
    link
    fedilink
    arrow-up
    4
    ·
    8 months ago

    If for example a client application is (accidentally) firing doubled requests to your API, you might get deadlocks in this case. Which is not bad per se, as you don’t want to conform to that behaviour. But it might also happen if you have two client applications with updates to the same resource (patching different fields for example), in that case you’re blocking one party so a retry mechanism in the client or server side might be a solution.

    Just something we noticed a while ago when using transactions.


  • Interesting, I work with both at my job and my main take is:

    • CLI of Mac is superior to me and least confusing, plus has it’s whole CLI experience working correctly for a long time, but Windows did a bit of a catch-up (still not on par IMO and too many ways of working)

    • The GUI settings are more advanced on Windows, but the new/old interface are a cluster fuck; I don’t trust the interaction between them

    • Windows has more compatibility options with hardware/software, if you dig deep enough you can make things work most of the times

    • The general MacOS experience (from starting your computer, opening apps, using the CLI) performs better, Windows feels a bit more sluggish/bloated to me

    I do like the steps that Microsoft takes with things like Visual Studio Code and .NET of aiming cross-platform. I have in no way any hatred for Microsoft and I think both operating systems have their pros and cons. They are both fine to work with.