Win32 API

is peak comfy and nothing else comes close

Homeless People Are Sexy Shirt $21.68

DMT Has Friends For Me Shirt $21.68

Homeless People Are Sexy Shirt $21.68

  1. 1 month ago
    Anonymous

    it's comfier to be able to read and edit the source of your operating system

  2. 1 month ago
    Anonymous

    The win32 API is nice but it would be nicer if the documentation wasn't constantly wrong.

    • 1 month ago
      Anonymous

      Give me examples.

      • 1 month ago
        Anonymous

        I haven't used it tons, so I may have just been unlucky so far to say "half the time", but off the top of my head DWMWA_USE_IMMERSIVE_DARK_MODE is supposed to make the window follow the user's preferred color scheme, but in fact as the name suggests actually just forces dark. You have to check the preference separately. There's some drawing macro for the callback that's supposed to paint asynchronously but actually paints synchronously so the window will literally yield not reponding if you make it pathologically large. And BCryptGenRandom() always gives the same result the first two times it's called on a new thread. There are many more examples, I've seen clips of Jon Blow b***hing about how Microsoft doesn't add fixed versions of anything anymore but still leaves the buggy ones in for compatibility.

  3. 1 month ago
    Anonymous

    MSVC is bloat

  4. 1 month ago
    Anonymous

    WTF-16 here, just came to say hi to you

    • 1 month ago
      Anonymous

      UTF-16 is such a confusing decision.

      • 1 month ago
        Anonymous

        not really, UTF-16 actually predates UTF-8
        UTF-16 is an extended version of the original "unicode" (now known as UCS-2), microsoft adopted unicode (UCS-2), and since UTF-16 is a compatible upgrade, moved to UTF-16
        UTF-8 is not compatible with UTF-16, so they are now stuck with UTF-16

        • 1 month ago
          Anonymous

          Wrong, UTF-16 and UTF-8 are compatibile. WTF-16 isnt compatible with UTF-16/UTF-8, there exists WTF-8 which is WTF-16 naively converted to UTF-8 like. This microsoft mistake is what also poisoned tons of programming languages like pyhton, js and java, and still keeps poisoning standard libraries to this date, rust's osstring, zig actually adopting WTF-16/WTF-8 semantics because supporting NT fully any other way is impossible. TL;DR yet another ms's turd gift tothe world

          • 1 month ago
            Anonymous

            Excuse the typos, have to phone post because jannies have range banned my IP for years now

          • 1 month ago
            Anonymous

            read that article
            windows adopted unicode before even C did, so they had to make up their own implementation
            when C did finally get unicode support, it was different, but microsoft wasn't about to break shit to change that

          • 1 month ago
            Anonymous

            Does not change the fact their UTF-16 isnt UTF-16, they can lie or spin it in their article however they may like but its WTF-16 aka UCS-2 (where wtf-x become popular when people encoded UCS-2 bytes to garbage unicode)

          • 1 month ago
            Anonymous

            at the end of the day, they did their own thing because they had to, now it's different to what everything else uses because everyone else waited to see what "won"
            it's annoying, but people make it out like microsoft was being different to be different, which is not really true in this case, though i can understand why people would assume that since that is something microsoft does do on purpose often (EEE)

          • 1 month ago
            Anonymous

            They had time to fix their shit, but nope

        • 1 month ago
          Anonymous

          even if it were true, choosing "to be stuck with" UTF-8 when the rest of the world isn't is in itself a decision.

      • 1 month ago
        Anonymous

        not really, UTF-16 actually predates UTF-8
        UTF-16 is an extended version of the original "unicode" (now known as UCS-2), microsoft adopted unicode (UCS-2), and since UTF-16 is a compatible upgrade, moved to UTF-16
        UTF-8 is not compatible with UTF-16, so they are now stuck with UTF-16

        https://devblogs.microsoft.com/oldnewthing/20190830-00/?p=102823

  5. 1 month ago
    Anonymous

    >incomplete
    >has errors
    >proprietary, cannot truly know what happens if stuff breaks
    no thanks

  6. 1 month ago
    Anonymous

    typedef int homosexual;
    typedef int *lphomosexual;

    Even the peak competent Microsoft develpoment team, their Windows C-programmers, were too dumb for pointers.

    There are just too few who can. The idea is not to make it more accessible, but to utilize the few that can as best as you can.
    TRD

    • 1 month ago
      Anonymous

      This shit bothered me the most when I dabbled with the winapi.

      https://learn.microsoft.com/en-us/windows/win32/winprog/windows-data-types

      typedefs for typedefs

    • 1 month ago
      Anonymous

      Typedefing pointers is a great idea because it fixes the moronic pointer syntax in C. You can even declare multiple pointer variables on the same line this way (but you still shouldn't do that).

      • 1 month ago
        Anonymous

        No, it doesn't, it is both moronic and a waste of time.

  7. 1 month ago
    Anonymous

    >WindowProc moronation that affects how you structure and pass things
    >no sane way to just pass a pointer around
    >have to go through an entire ritual of GetWindowLongPtr and LPCREATESTRUCT moronation
    >things not updating without a pointless SetWindowPos call
    I honestly prefer XCB, despite the """"""""""""""documentation""""""""""""" being random window manager repos on githutb

Your email address will not be published. Required fields are marked *