• 0 Posts
  • 40 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • Unfortunately, at least in my country, it’s getting harder and harder to do banking through a plain old webbrowser. Apps are being pushed hard and afaik all of them use the Google Lock-In API in their Android app. Alternatively I could switch to iPhone, but having had the displeasure of experiencing their crappy hardware and even worse service I’d rather cut my balls off than ever dealing with Apple again.





  • Founded by Nazis, but abandoned during the war and revived by British army officer Ivan Hirst whom both saw the potential for turning it into a workshop and building new vehicles for the British occupation forces.

    After the war it was used by REME (Corps of Royal Electrical and Mechanical Engineers) to repair British army vehicles, and it was used to build new vehicles. It was handed over to West Germany in september 1949.

    The company as we know it today therefore effectively has more British roots than Nazi ones.




  • It moves the value of register (a CPU memory cell) rbx to register rax. It’s not that important though.

    Basically the comic shows that the CPU is happily chugging along, executing instructions when suddenly the keyboard sends an interrupt telling the CPU it must stop all work and listen to whatever it has to say.

    That was how keyboards worked before USB (back when they used PS/2 or DIN connectors). With USB it’s the other way around: the device gets polled X times per second to check if it has any data to send.



  • Aganim@lemmy.worldtoProgrammer Humor@programming.devProgress
    link
    fedilink
    arrow-up
    8
    arrow-down
    5
    ·
    edit-2
    5 months ago

    So is comparing a Microsoft bug to the highlight of the Apollo project and conveniently ignoring all the setbacks that both led up to and followed it.

    I don’t mind bashing Microsoft where warranted, but this just feels like cherry picking from a long list of technical and procedural failures.











  • Aganim@lemmy.worldtolinuxmemes@lemmy.worldPreference
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    7 months ago

    KDE on Wayland has only very recently started to become workable for me, before that it was utter crap as I switch between home and office with my laptop, with varying display setups. In that case you got stuff like screen positions not being remembered and applications consistently starting off screen, requiring gymnastics to coax them onto a display.

    And regularly it would crap out and not show output to one of the displays, if you opened up display manager you’d see the displays not touching and a big red error telling you that gaps betweens displays aren’t supported. Well here’s a brilliant idea, how about not automatically putting a gap between them in that case?

    As I said, last few months it works better (although I still encounter some issues from time to time that I never had on X11). But the whole Wayland protocol had such a rough start, with issues encountered often being downplayed by parts of the community because “it’s better and we don’t want to hear otherwise”, that I simply cannot feel any love for it anymore. There was too much basic stuff that took too long to support, while people were shouting “but HDR!”, “better code!”. I don’t fucking care, I just want to be able to work and for too long that required X11.

    Edit: some typo’s and improved readability.