make handles bold.

This commit is contained in:
ed committed 2026-08-25 16:26:52 -04:00
1 parent f577242432
commit 69b87777e5
728 files changed
+3291 -3087

No files matched your search

@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @Alecazam123
**1/** **@Alecazam123** ^2010391151208251442
@Dispatch_Graph
**@Dispatch_Graph**
Hard to believe I’m still writing games in Win32 25 years later. But it runs on SteamOS, so can never be replaced now.
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @BowTiedTails
**1/** **@BowTiedTails** ^2010494359062327682
@Dispatch_Graph
**@Dispatch_Graph**
Yep. Win32 is heaven when you see what else is out there.
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @VPCOMPRESSB
**1/** **@VPCOMPRESSB** ^2010378880209871041
@Dispatch_Graph
**@Dispatch_Graph**
coincidentally, i made a Vulkan Wayland compute engine yesterday in ~600 LoC.
@@ -26,42 +26,42 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @VPCOMPRESSB
**1/** **@VPCOMPRESSB** ^2010385913541546282
yeah. i actually prefer Wayland because if you implement something super simple, you get something super simple back (e.g., if i create a window, i get the bare minimum window - no decorations, no resizing, no keyboard or mouse input). with Win32, i'd have fight it and move through its weeds to force it to make something simple.
another problem with Win32 is that it modularizes too much, and make everything seem irrelevant from each other. in Wayland, it's all unified, where if just learn 1 pattern from 1 thing, you can apply that pattern to everything else, from windows to input (e.g., all interfaces are just a simple server-client messaging model). basically, you can take a step back and look at everything as a whole, and clearly see a pattern.
**2/** @NOTimothyLottes
**2/** **@NOTimothyLottes** ^2010396312651649276
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
You didn't get the true Wayland experience until you try interfacing to Wayland without the Wayland user-space library. Meaning do it with just the kernel calls required. Then you will have taken the gold off the poop, and understood how bad it actually is.
**3/** @NOTimothyLottes
**3/** **@NOTimothyLottes** ^2010398147617640535
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
WIN32 base system DLLs are a substantially cleaner interface. I only do non-decorated full-screen (foreground or background) window. Majority of WIN32 code fits on screen grab with mostly comments. I'm not a fan of their "WndProc" but at least it is simple.
![](https://pbs.twimg.com/media/G-Zd9wLWUAE9kZj?format=png&name=orig)
**4/** @NOTimothyLottes
**4/** **@NOTimothyLottes** ^2010398743422709770
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
Some like to hate on X11, but for what it was designed to do (support both local and remote displays), it is at least very well documented and actually quite easy to roll an interface for with just Linux kernel calls (no external libraries). Docs here: https://x.org/releases/X11R7.7/doc/xproto/x11protocol.html
**5/** @NOTimothyLottes
**5/** **@NOTimothyLottes** ^2010404729633829180
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
Duckduckgo Wayland protocol and you get this garbage as documentation (below). Nothing there actually explains how it works, it's just high-level OOP obfustication speak. My vomit translator cannot even process this stuff.
![](https://pbs.twimg.com/media/G-Zjy3uXgAETWbE?format=jpg&name=orig)
**6/** @NOTimothyLottes
**6/** **@NOTimothyLottes** ^2010407422272160202
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
Lets continue. It's built over unix domain sockets and doesn't support remote rendering. Haha, WFT. Just because they want to transfer file descriptors between processes for "bulk data". Wayland looses network displays and is SLOWER (fail): https://www.dedoimedo.com/computers/plasma-6-4-performance-wayland-x11-power-cpu-kernel.html
@@ -69,47 +69,47 @@ Lets continue. It's built over unix domain sockets and doesn't support remote re
![](https://pbs.twimg.com/media/G-Zla8PXYAAdRoE?format=png&name=orig)
![](https://pbs.twimg.com/media/G-ZmyPCWQAAKtYR?format=png&name=orig)
**7/** @NOTimothyLottes
**7/** **@NOTimothyLottes** ^2010411498729046449
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
Don't understand why Linux people had to take what was working, X11, and instead of just improving it, they had to make something that {removed the remote desktop, made it slower, and forces an OOP garbage design}. There is nothing good here.
**8/** @NOTimothyLottes
**8/** **@NOTimothyLottes** ^2010412846845473278
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
Another great thing about X11, is that it was trivial to both write and use your own window manager, using the same stable system for DECADES. I had a 350 line minwm.c window manager. Dead easy.
![](https://pbs.twimg.com/media/G-ZrxUJXwAAINS7?format=png&name=orig)
**9/** @NOTimothyLottes
**9/** **@NOTimothyLottes** ^2010418524376981598
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
Unix was about KISS (keep it simple stupid) then Linux user-space people transformed that into MISC {make it stupid complex}. Seen this trend with Audio, from OSS to ALSA, and so on.
**10/** @NOTimothyLottes
**10/** **@NOTimothyLottes** ^2010420107630330273
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
I worked in the {SunOS,Solaris,HPUX,SGI,AXI,etc} workstation era and started on Linux before ELF and before pthreads. Meaning I build things based on fork() [instead of pthreads] and SHM (shared page mappings) when doing local-only interfaces (no high kernel call granularity).
**11/** @NOTimothyLottes
**11/** **@NOTimothyLottes** ^2010421431105093819
@VPCOMPRESSB @Dispatch_Graph
**@VPCOMPRESSB** **@Dispatch_Graph**
If Linux people wanted to replace X11 with a local only interface, at a minimum it should have been simple SHM for the majority, and then only go outside SHM when needing to say kick a doorbell (make wake another process), etc.
**12/** @o__boga
**12/** **@o__boga** ^2010504713867870403
@NOTimothyLottes @VPCOMPRESSB @Dispatch_Graph
**@NOTimothyLottes** **@VPCOMPRESSB** **@Dispatch_Graph**
Obfuscation is the secret for its "security!"!
**13/** @VPCOMPRESSB
**13/** **@VPCOMPRESSB** ^2010498624157782265
@NOTimothyLottes @Dispatch_Graph
**@NOTimothyLottes** **@Dispatch_Graph**
i've never actually used X11. this is much easier.
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @hadal101dev
**1/** **@hadal101dev** ^2010378989022622068
@Dispatch_Graph
**@Dispatch_Graph**
Yea windows makes some interesting choices lol. Calling CreateFile when you want to OPEN a file? very weird lol.
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @smolus
**1/** **@smolus** ^2010450157222154626
@Dispatch_Graph
**@Dispatch_Graph**
one thing I appreciate about wayland is that it's just a simple protocol spec so you are not married to any particular API/library but yeah it can be a lot of work to get basic things working
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @Chris_Linux
**1/** **@Chris_Linux** ^2010676815128301753
@Dispatch_Graph
**@Dispatch_Graph**
Apples and oranges comparison here
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @FoundryOfLies
**1/** **@FoundryOfLies** ^2010725798114979912
@Dispatch_Graph
**@Dispatch_Graph**
It's KWin
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @JoaoBapt
**1/** **@JoaoBapt** ^2010753110805979471
@Dispatch_Graph
**@Dispatch_Graph**
I suggest you to stick with GLFW if you’re only doing Vulkan.
@@ -26,15 +26,15 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @Oka7071
**1/** **@Oka7071** ^2010799896866255168
@Dispatch_Graph
**@Dispatch_Graph**
![](https://pbs.twimg.com/media/G-fL2X9WAAARbpz?format=jpg&name=orig)
**2/** @Dispatch_Graph
**2/** **@Dispatch_Graph** ^2010808986619298248
@Oka4902
**@Oka4902**
if you give me 3 trillion dollars I can elaborate
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @PervWizz
**1/** **@PervWizz** ^2010750206237651067
@Dispatch_Graph
**@Dispatch_Graph**
Well. Win32 began as a bad API and then organically got reshaped into a worse one. Same goes for X11
@@ -26,15 +26,15 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @Rami36217810
**1/** **@Rami36217810** ^2010799138712273238
@Dispatch_Graph
**@Dispatch_Graph**
What about x11
**2/** @Dispatch_Graph
**2/** **@Dispatch_Graph** ^2010808862623027217
@Rami36217810
**@Rami36217810**
its aight
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @SyntaxError2505
**1/** **@SyntaxError2505** ^2010700042080862455
@Dispatch_Graph
**@Dispatch_Graph**
Why? Sdl works great
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @f82james
**1/** **@f82james** ^2010735384750334453
@Dispatch_Graph
**@Dispatch_Graph**
fuck x11
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @linux_version
**1/** **@linux_version** ^2010740512769404946
@Dispatch_Graph
**@Dispatch_Graph**
Oddly enough, with how old the wine project is, Win32 might be the most stable API on Linux.
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @mizanyx
**1/** **@mizanyx** ^2010686383954800643
@Dispatch_Graph
**@Dispatch_Graph**
Elaborate please, I'm still an X11 user
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @platonvin
**1/** **@platonvin** ^2010728789396050001
@Dispatch_Graph
**@Dispatch_Graph**
windows.h is like a nightmare but real. It is so bad, that many people manually paste parts of it to avoid including entire thing
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @ruminaik
**1/** **@ruminaik** ^2010733158996865131
@Dispatch_Graph
**@Dispatch_Graph**
And let us say Amen
@@ -26,9 +26,9 @@ parent_post_id: "2010303501851877740"
## Branch
**1/** @thedarkhog
**1/** **@thedarkhog** ^2010669573427884393
@Dispatch_Graph
**@Dispatch_Graph**
Get Xlibre instead. If you're using arch, btw., it's in the AUR.
@@ -25,20 +25,20 @@ in_reply_to: ""
## Thread
**1/** @Dispatch_Graph
**1/** **@Dispatch_Graph** ^2010303501851877740
Ok, the Win32 API sure is something, but WOW wayland is awful
Branches: [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-11-VPCOMPRESSB-coincidentally-i-made-a-vulkan-wayland-compute]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-11-hadal101dev-yea-windows-makes-some-interesting-choices-lol]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-11-VPCOMPRESSB-yeah-i-actually-prefer-wayland-because-if-you]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-11-Alecazam123-hard-to-believe-im-still-writing-games-in-win32]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-11-smolus-one-thing-i-appreciate-about-wayland-is-that-its]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-11-BowTiedTails-yep-win32-is-heaven-when-you-see-what-else-is-out]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-thedarkhog-get-xlibre-instead-if-youre-using-arch-btw-its-in]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-Chris_Linux-apples-and-oranges-comparison-here]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-mizanyx-elaborate-please-im-still-an-x11-user]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-SyntaxError2505-why-sdl-works-great]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-FoundryOfLies-its-kwin]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-platonvin-windows-h-is-like-a-nightmare-but-real-it-is-so]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-ruminaik-and-let-us-say-amen]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-f82james-fuck-x11]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-linux_version-oddly-enough-with-how-old-the-wine-project-is]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-PervWizz-well-win32-began-as-a-bad-api-and-then]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-JoaoBapt-i-suggest-you-to-stick-with-glfw-if-youre-only]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-Rami36217810-what-about-x11]], [[archive/threads/Dispatch_Graph/2026-01-11-ok-the-win32-api-sure-is-something-but-wow/2026-01-12-Oka7071-thread]]
**2/** @ocarina588
**2/** **@ocarina588** ^2010305588580974622
@Dispatch_Graph
**@Dispatch_Graph**
😂😂😂, what are you using? Hyprland ?
**3/** @Dispatch_Graph
**3/** **@Dispatch_Graph** ^2010319408045183333
@ocarina588
**@ocarina588**
KDE Plasma