I have now used Redux pretty extensively in multiple projects by now, especially the Firefox Developer Tools. While I think it breaks down in a few specific scenarios, generally I think it holds up well in complex apps. Certainly nothing is perfect, and the good news is when you want to do something outside of the normal workflow, it’s not hard.
It’s been 6 months since my last blog rewrite, so it’s time for another one. This time, let’s subtract.
In most debuggers, a breakpoint will "slide" if the clicked line doesn't have any code. This is supposed to be a helpful feature, but it becomes **infuriating** if it behaves wrongly. In Firefox 46, we made our breakpoint sliding algorithm much more robust.
In this post, I explain why it has taken so long to get the Firefox console sourcemapped. It requires an unobtrusive debug mode which is really hard to do, but we got it working. The console now has access to sourcemaps, so we are only one small step away from getting it working.
"It’s late Friday night, my wife is already asleep, and I finally found time to go through those pull requests on that old project I put up on github last year. My daughter is getting up at 7:30 though, so I better not stay up too late. ..."
- LLJS fork of LLJS that compiles to asm.js
- dcpu-lisp static Lisp that compiles to DCPU-16 assembly code
- shade terrible WebGL graphics engine
- octoshot multiplayer WebGL 3d first person shooter
- dom3d 3d objects with purely 2d CSS transforms