This commit is contained in:
ed committed 2026-08-24 23:32:21 -04:00
1 parent 8741077173
commit 8b8f1a231c
2 files changed
+58

No files matched your search

@@ -0,0 +1,56 @@
---
title: "@NOTimothyLottes I just wish the win32 API was better designed."
type: archive
source: twitter
source_url: "https://x.com/philthistweet/status/1950918943834620235"
author: "phil bohun"
handle: philthistweet
post_id: "1950918943834620235"
date: 2025-07-31
archived: 2026-08-24
draft: false
tags:
- archive
- twitter
- NOTimothyLottes
description: "@NOTimothyLottes I just wish the win32 API was better designed."
in_reply_to: ""
parent_post_id: "1950866703342088407"
---
## Source
- URL: https://x.com/philthistweet/status/1950918943834620235
- Author: phil bohun (@philthistweet)
- Posted: 2025-07-31 13:58:17
## Branch
**1/**
@NOTimothyLottes I just wish the win32 API was better designed. It would essentially be perfect for cross dev then.
**2/**
@philthistweet Certainly it could be, but as is, it's easy to use and not strictly limiting. Id be curious what people don't like about it. Maybe the winproc interface?
**3/**
Just a few examples:
1) thread/process creation and management
2) file system interface (e.g. listing files in a directory)
3) interprocess communication
I know you can wrap these in your own library, but I'd end up wrapping almost the entire win32.
Whoever sat down to create it probably said: "How can I create the most annoying, unintuitive API possible?"
Honestly, I may start a wrapper project though, because it's the only stable API that works
**4/**
@philthistweet Clone is nicer and having ability to own cores should be great. But at least you get affinity and schedule priority. Yeah agree the file interface is poor, but I just memmap and manually page warm to bypass most of that.
## Related
- Spine: [[archive/threads/NOTimothyLottes/2025-07-31-people-claim-assembly-is-hard-a-good-counter-to]]
@@ -43,6 +43,8 @@ ASM provides a good opportunity to show how to convert typical function argument
Linux has been all down hill over the years. OSS was fantastic, easy portable Linux system call interface. Also it's easy to do direct X11 with just syscalls. Now with Wayland you are stuck with linking to a garbage library. So might as well do WIN32 for Linux and depend on Wine.
Branches: [[archive/threads/NOTimothyLottes/2025-07-31-people-claim-assembly-is-hard-a-good-counter-to/2025-07-31-philthistweet-i-just-wish-the-win32-api-was-better-designed-it]]
**5/**
So Valve standardizing on Proton saves a lot of trouble with porting across ABIs/etc, just do WIN32 as it's way easier to interface with than Wayland and whatever horrible userland audio interface Linux monkeys switch to this era.