arjonagelhout

I didn't know that was a thing, but that makes sense. Thanks!

Brilliant, this website is blocked at my work: "This content is blocked by your organization".

I personally avoid Visual Studio Code as much as possible due to the scroll latency, so I think it is noticeable as long as you know what to look for.

I personally use Skia, in combination with a very thin platform layer. I do use C++ so that might still be a bit too low level, but after having set up everything, the Skia API is really nice for just drawing some text / other primitives onto the screen.

React Native uses Skia under the hood as far as I recall.

That wasn't my intention. The intention was to share the joy of working on a single project for a long time, and holding myself accountable to keep working on this project instead of abandoning it.

Merry Christmas!

Here’s a quad tree:

11

11

—

0110

0110

1111

0110

—

00000000

00011000

00011000

00111100

01111110

11111111

00011000

00011000

Hi HN, I’m working on a 3D modeling app, and landed on a simple approach to implementing undo for a mesh graph data structure.

I’d also love to be pointed to other techniques or approaches that might be better.

Let me know if the part about recording the diff is of interest.

I think it’s a bug in getting a useful outcome, but it’s a feature in creating engagement with the post.

I have the same issue. For many of the questions my answer is "all of the above, but A in context A, B in context B, etc.". Many are also not mutually exclusive.

Take this example: "When debugging I typically:"

> Write tests to isolate the problem

In the case of math functions, or more primitive building blocks, writing tests can help ensure correctness of the underlying functions, to exclude them from the problem search.

> Reason about the code logically first

This is always useful.

> Use a debugger to step through code systematically

Useful when dealing with a larger codebase and the control flow is hard to follow. The call stack can give quick guidance over trying to manually decipher the control flow.

> Add print statements to understand data flow:

Useful when debugging continuous data streams or events, e.g. mouse input, where you don't want to interrupt the user interaction that needs to be debugged.

I get “A problem repeatedly occurred on <url>” on iOS Safari.

I didn't know about Feather 3D, but it looks super aesthetically pleasing. I'll have to try it out.

I tried uMake a while back, but found the 3D viewport navigation a bit hard to use, and would often find out I had been drawing on the wrong plane after orbiting the camera.

After using something like Tilt Brush in VR, it's hard to go back to a 2D screen that doesn't instantly communicate the 3D location of the brush strokes you're placing.