Watch how your code behaves as you write it. Faster iterations. Better understanding. Fewer errors. By @azmreece & friends Discord https://xitter.cf/t.co/Oky8t1Ao7O

Joined September 2019
WhiteBox retweeted
I'm feeling the pull to write some of the articles I listed at azmr.uk/bsc25 First up is going to be "Bits are high level", focused on human-meaningful interpretations of bitwise ops. I have my list, but I'd welcome any additional favourites from you fine people 😄
1
3
22
485
Very excited to use @Blick_Editor for upcoming videos! There also *may* be the odd timeline feature/affordance that we shamelessly steal...
1
1
42
2,880
.@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. youtu.be/i-h95QIGchY
3
56
5
364
44,232
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: chat.whitebox.systems
1
1,057
Casey's talk is now available on YouTube. Enjoy! youtu.be/wo84LFzx5nI
11
71
15
535
34,505
Replying to @whitebox_sys
Can confirm, I've seen the bits, they are indeed the finest, highest quality bits money can buy. Primo bits.
1
3
1,086
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: twitch.tv/azmreece
2
2
1
7
4,341
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.
1
3
1,135
(The infrastructure for this was needed regardless of speedup, so I'd only used summary profiling before doing this, and overestimated its individual impact.)
2
651
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: twitch.tv/azmreece
2
13
1,792
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.
2
1
6
2,281
If you'd like to be able to use/inspect constants in your debugger...
2
14
1,283
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.
1
3
22
1,172
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.
1
8
1,139
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 handmadecities.com/seattle/
1
2
8
961
See if you can spot the clip of WhiteBox debugging WhiteBox...
1
342
"Thanks to WhiteBox, I have a very good idea in which part of the function everything is being turned into a mess. This tool is so useful! 😄" -- New WhiteBox user and 3rd year Computer Engineering student
3
8
735