I realized I'd only previously posted a teaser to WhiteBox's Handmade Seattle 2021 demo.
Here's the best compressed overview of what WhiteBox is and how you might use it:
https://t.co/jUYfoPYE6Z
.@azmreece's talk it out! A deep, technical look into concrete methods for reducing layers of indirection, memory accesses, and showing his Xar data-structure: A simple, pointer-stable, CPU-friendly, growable array.
https://t.co/5BOU3ZAhhs
Someone kindly pointed out that our friendly discord URL was broken.
I think I screwed it up while changing DNS details for our email provider...
Anyway, if you haven't yet joined, the link should be live again: https://t.co/oVVGIDeTqW
@luc_dyoro@grok Hey, sorry for the delayed response.
It's something I'd like to do but it's not a high priority at the moment unless someone wants to fund its development
For #DOOM30 let's WhiteBox some of its gameplay
Here I'm sampling every time the cursor is hit (in the frame loop).
- each bar in the timeline shows a change in value for the track's expression
- ints are graphed, scaled by min/max values seen
- vectors can be viewed as arrows
@luc_dyoro@grok I just tested it - it sort of works with C-like D code, but I can't recommend it for D in general currently.
This is only really because I'd never used D until 5 minutes ago!
(dmd produces PDBs, so grok is wrong here - there's no *major* incompatibility)
@kenpex@Kknewkles We've been quiet recently, but WhiteBox is by no means abandoned 😀
We've put out ~50 releases in the last 10 months.
As for "prototype": it's definitely not finalized (there's a reason it's not v1.0), but I AFAICT all of the major uncertainties have been resolved...
I'm going to finish painting a door frame, maybe have a bite to eat, then stream some cozy WhiteBox dev: fixing bugs, edge-cases & jank UI.
aka "I push my TIMELINE DEBUGGER to its LIMITS! Can I stop it from BREAKING?! 💥🔨"
Join either way in ~40 mins: https://t.co/9XUzDBfir2
(The infrastructure for this was needed regardless of speedup, so I'd only used summary profiling before doing this, and overestimated its individual impact.)
This worked in that it removed a fixed cost, although it's not a huge proportion (~3-10%).
Going through the process brought out some more low-hanging fruit for optimizations.
(And once other costs are reduced, the fixed cost here will represent a larger percentage 😂)
I've got an idea that I think should majorly speed up breakpoint recovery that I'll be trying out this week.
All going well, this should mean dense inspections cause less slowdown. The effect should be particularly noticeable for multithreaded user code.
I'm streaming some WhiteBox dev now! (@whitebox_sys)
I'm going to add some new debugger features by JIT compiling into the user process.
Jump in: https://t.co/9XUzDBeKBu
I've got an idea that I think should majorly speed up breakpoint recovery that I'll be trying out this week.
All going well, this should mean dense inspections cause less slowdown. The effect should be particularly noticeable for multithreaded user code.
AI-generated code is not used to build WhiteBox.
You can rest easy, knowing that all our software is handcrafted by artisans using organic, grass-fed, free range bits.
Know when the thing you're interested happens?
Sample every time it does.
Know where but not when it happens?
Over-sample, then highlight whenever an expression is true.
Found what you're looking for and don't need context?
Filter what's visible to just what's relevant.
One hour until the WhiteBox demo is presented at the Handmade Seattle conference.
We're showing off how we use it to solve real-world bugs, making use of some new features that haven't been shown until now!
You can watch it as it's livestreamed at https://t.co/ohjENGC015