Check out raddebugger's implementation as well -
ui_signal_from_box:
https://t.co/e6QgzE7WQz
I compiled all my refs or notes on Imgui here:
https://t.co/qoJSk75zBW
My stuff was very wip, I didn't get a lot of core features done (like clipping children for scroll boxes). Very much was me learning imgui like Primeagen but in 2024..
I was trying to make a min viable high-perf ui for code viewing in both a traditional "screen" and zoomable canvas space. The canvas zooming was a nice rabbithole on text rendering. I'll probably get back to that prototype next year. Not sure if in Odin though.
I've been loosely following your UI journey. I think you have a better setup than some exploration I did a few years back. Implementation was heavily influenced by RAD Debugger's UI layer. Had went into trying a hybrid auto-layout with some ability to just allow doing layout passes immediately.
Edit: (twitter not allowing edits on replies..)
Layout defs: https://t.co/LpSM4BuwjJ https://t.co/ezazmSHoAb
Builder's end pass: https://t.co/V98Gr8qAYu
@rushicrypto it's intentional. This isn't an accident, and it's not people "ignoring". There has been more than plenty of reputable sources, conferences, workshops, books on what's going on. These people are intentionally doing this. And they want the predictable outcomes of it.
I managed to get RetroPad, my full-feature-parity version of Notepad from XP, down to 2686 bytes of tight x86 assembly.
I checked in the exe to make life simpler, so you don't need masm on hand!
Episode coming shortly... follow so you don't miss it!
Code: https://t.co/Kl736oVuvC
We can get a bunch of the UX from node based structural editors, but in a more text, block based form. Where your not constrained to a text grid or file slice that's bound per-file to a filesystem as a reference to the data. That can just be a cold serialization source of truth. Unfortunately because everything is either text based or jank binary blobs for serializing this info (Unreal) and then processing it for execution or symbol navigation; we don't have many good examples of this in modern toolchains.
I think some old toolchains ideated on some of this (80s-90s) but they always catered toward unskilled developers or crufted runtime environments that tried to "simplify" the scripting experience instead of just doing a systems level sandbox first.
Nothing public does proper memory mapped I/O to service a toolchain for a "language" that a "structured" frontend would communicate with. It's just slow VSCode styled JSON lsp jank. People think we're living some crazy futuristic and robust toolchain but we're really in some dystopian slopfest.
Glyphosate is a chemical that inhibits the shikimic pathway in bacteria, which produces the aromatic amino acids phenylalanine, tyrosine, and tryptophan. Glyphosate is sprayed on basically every grain in the US, and grains are used to make bread.
Glyphosate should not directly affect human cells since we lack the enzymes for the shikimic pathway, but our gut harbors bacteria that require it to produce aromatic amino acids.
Different bacteria vary in susceptibility to glyphosate. Generally, beneficial bacteria are wrecked while harmful ones are not. The degree to which glyphosate affects gut bacteria is disputed, but the mechanism exists and can lead to dysbiosis.
Glyphosate is likely a major reason why guts in the US are trashed, with bacterial endotoxins weakening intestinal tight junctions. This allows undigested food particles into the bloodstream, triggering immune reactions to normal foods.
Pathogenic serotonin and histamine loads from the dysbiosis then wreck mental health: depression/anhedonia, anxiety, ADHD, and OCD are all consequences of dysfunctional serotonin and histamine signaling.
You would think with all this ai cruft, Epic Games and other vendors would have eliminated the technical writing bottleneck for engine docs but instead its still terrible.
PSA: @TencentGlobal is aggressively scraping the Internet to build yet another AI slop chatbot, DDoSing many websites in the process.
We've found that, as of last week, their scraping bots can now solve Cloudflare challenges and behave like real users while ignoring robots.txt. In the last 24 hours alone, our website received more than 3 million successful requests from Tencent bot IP addresses, plus another 1 million that were blocked by Cloudflare challenges.
These recurring DDoS attacks from Tencent have been going on for over a year, and we have been constantly adjusting our firewall rules to filter them while trying not to impact Tencent's real users. Because that is no longer possible, we're now fully blocking Tencent IP addresses, starting with ASN 132203. We recommend other sysadmins do the same.
Other ASNs displaying similar abusive behaviour will also be fully blocked from our services.
We'd also like to thank @Cloudflare for sponsoring us with Project Alexandria as of 2025, giving our sysadmin the tools to keep RPCS3's online services running without service disruptions.
It's unfortunate there isn't an easy way to map the page file so that writes don't automagically post to storage, meaning map then turn off flush until a time desired by the programmer.
FragCoord is now the best place online to share:
-Complex graphics demos (fluid simulation, Radiance Cascades, audio visualizers, multi-pass post-processing)
-Shader functions and code snippets
-HLSL, MSL, live demos
-Code golfing
-Advanced shader debugging
I just think that we could achieve everything we do today with computers, with a simplified "technical stack" consisting of 98% less stuff ... fewer complexities to deal with when making things on top, thus easier to create the things and the higher-quality they will be (and cheaper, and more robust, etc). But not that many people seem to care about this issue.