docs(twitter): add 1951347512088088657 corpus (NOTimothyLottes 'engine' project announcement)

5-post thread. Announcement of next at-home project: build-from-assembly video series + public-domain 'engine' = live-edit toy for GPU-side PC game dev. Won't run on Intel iGPUs (binding limits). Memory model is CART-style (RAM CART buffer = snapshotted + dynamic GPU = not). GPU- side editing tools for shader source + bind tables, build-the-editors- in-it, load/store to CART. Sized for what a single person could pull off, not TBs of team-gen content.
2026-07-27 00:11:57 -04:00
parent ea9ca0e738
commit fcf70065e6
2 changed files with 121 additions and 0 deletions
@@ -0,0 +1,35 @@
+---
+title: "Also run-from GPU-side editing tools for shader source and bind everything table"
+author: "NOTimothyLottes"
+handle: "@NOTimothyLottes"
+post_url: "https://x.com/NOTimothyLottes/status/1951347512088088657"
+post_id: "1951347512088088657"
+timestamp: "2025-08-01 18:21:15"
+post_count: 5
+reply_count: 2
+repost_count: 0
+like_count: 17
+view_count: 963
+---
+
+# @NOTimothyLottes — Also run-from GPU-side editing tools for shader source and bind everything table
+
+## Post 1 (2025-08-01 18:15:07)
+
+At least for my next at home project, I think the right answer is a building it from assembly scratch series on video with a public domain release of the 'engine' which will be a live edit toy for hardcore GPU-side PC game dev in certain constraints [which keep it simple]
+
+## Post 2 (2025-08-01 18:18:39) — reply to Post 1
+
+It won't require RT, but it also won't run on Intel iGPUs [to low binding limits, etc]. Memory model will be 'CART' style where you get the a RAM CART [buffer] in memory which gets state snapshot, followed by dynamic GPU memory which is not snapshotted
+
+## Post 3 (2025-08-01 18:21:15) — reply to Post 2
+
+Also run-from GPU-side editing tools for shader source and bind everything tables. And build-the-editors-in-it style. Which load/store to the CART. So it won't be for people who want TBs of giant team gen content, but rather sized for what a single person could pull off
+
+## Post 4 (2025-08-01 20:06:53) — reply to Post 3
+
+@NOTimothyLottes Looking forward to it, what do I bookmark?
+
+## Post 5 (2025-08-01 20:25:38) — reply to Post 3
+
+@NOTimothyLottes Sounds super interesting!
@@ -0,0 +1,86 @@
+{
+  "root_post_id": "1951347512088088657",
+  "posts": [
+    {
+      "post_id": "1951345967795675161",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "At least for my next at home project, I think the right answer is a building it from assembly scratch series on video with a public domain release of the 'engine' which will be a live edit toy for hardcore GPU-side PC game dev in certain constraints [which keep it simple]",
+      "timestamp": "2025-08-01 18:15:07",
+      "media_urls": [],
+      "reply_to_id": null,
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 2,
+        "repost_count": 2,
+        "like_count": 56,
+        "view_count": 2406
+      }
+    },
+    {
+      "post_id": "1951346857017250014",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "It won't require RT, but it also won't run on Intel iGPUs [to low binding limits, etc]. Memory model will be 'CART' style where you get the a RAM CART [buffer] in memory which gets state snapshot, followed by dynamic GPU memory which is not snapshotted",
+      "timestamp": "2025-08-01 18:18:39",
+      "media_urls": [],
+      "reply_to_id": "1951345967795675161",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 2,
+        "repost_count": 0,
+        "like_count": 15,
+        "view_count": 1071
+      }
+    },
+    {
+      "post_id": "1951347512088088657",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "Also run-from GPU-side editing tools for shader source and bind everything tables. And build-the-editors-in-it style. Which load/store to the CART. So it won't be for people who want TBs of giant team gen content, but rather sized for what a single person could pull off",
+      "timestamp": "2025-08-01 18:21:15",
+      "media_urls": [],
+      "reply_to_id": "1951346857017250014",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 2,
+        "repost_count": 0,
+        "like_count": 17,
+        "view_count": 963
+      }
+    },
+    {
+      "post_id": "1951374094655516679",
+      "author": "Sankrant Chaubey",
+      "handle": "snk_xed",
+      "text": "@NOTimothyLottes Looking forward to it, what do I bookmark?",
+      "timestamp": "2025-08-01 20:06:53",
+      "media_urls": [],
+      "reply_to_id": "1951347512088088657",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 0,
+        "repost_count": 0,
+        "like_count": 0,
+        "view_count": 35
+      }
+    },
+    {
+      "post_id": "1951378813985890736",
+      "author": "Joey Az",
+      "handle": "joeyazf",
+      "text": "@NOTimothyLottes Sounds super interesting!",
+      "timestamp": "2025-08-01 20:25:38",
+      "media_urls": [],
+      "reply_to_id": "1951347512088088657",
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 0,
+        "repost_count": 0,
+        "like_count": 1,
+        "view_count": 59
+      }
+    }
+  ],
+  "source_url": "https://x.com/NOTimothyLottes/status/1951347512088088657"
+}