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

help-circle



  • I imagine it started with some sub-installations actually giving approximations that were acceptable and summed up, but then some finalizing was not taken into account or something needed to be added after the other processes are finished, and the deadline was close. That last part builds up over time with other quick additions and some annoying stuff that is actually quite performance heavy and not easy to incorporate through the whole installation. “Let’s do it at the end as well.”

    No time / budget to change the 100% to 99% as they have to adjust calculations based on the processes that actually do a good job. Although a display change could fake it, priorities are elsewhere.









  • While I agree with your sentiments, for a modern country I see it as a tool to be able to more easily handle international relationships with some countries who still see the importance (like an old handy swiss army knife you have laying around). As long as the monarchy is purely ceremonial and does not affect your own country’s politics.

    It should disappear sooner or later though. If it did not have that sneaky, seemingly effective benefit (as I’ve been dumbfounded by in the Netherlands) I’d be all for removing it right away.



  • It depends on if you trust Meta. Generally speaking there is end-to-end encryption in WhatsApp, which means only you and the person you chat with can decrypt your messages / media (source). I believe there are some weak spots in group chats, mostly caused by users themselves. Not sure about the new Community function but I’d be careful with what I share there.

    Some parties like Apple have decided to scan photos from your device for illegal material (edit: after backlash they dropped this for now, my bad). If using an app like WhatsApp I’d personally be aware that something like that might happen in the future as well. I’d not be surprised if some employees might (temporarily) be able to access more data than widely assumed, for debugging reasons in case of bugs.

    Personally I take the risk for pragmatic reasons, but it doesn’t hurt to be a bit cautious / aware.





  • A bunch of cells in rapid development with the potential to become a human being. Murder is a strong term, but in a broad sense I don’t think your insinuation is wrong per se.

    This might be getting a bit controversial, but for the sake of discussion:

    The important thing here is, do you mind if that potential for life is taken away. In this case we place priority on the human being that eventually has to dedicate her life to that potential. Or is that new potential more important than that already existing, conscious human being (especially when there are physical / mental problems involved)?

    It comes down to why we live, and why must we live? Personally I believe trying to avoid (potential of) suffering is a more reasonable concept.

    If one gives life to a baby, you give it a potential for suffering which it otherwise does not. I’d say the ways one can suffer is of a greater weight than the ways one can be happy. So if you go the route of creating life, you better be damn confident that you are in a good position to do that.

    In that philosophy ‘murdering’ a potential with a large chance of creating more suffering for the collective is not that bad. One might view this differently when the being is conscious and might actively not want to die, as we bring the complexity of individual human choice to the table and what worth that has; but I think we can agree that is not applicable on the unborn potential human being discussed in this topic.


  • tweeks@feddit.nltoProgrammer Humor@lemmy.mlWhoops
    link
    fedilink
    arrow-up
    4
    ·
    11 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.