Very sad to see this wonderful podcast go, thanks a lot for all these fun and interesting episodes <3
The dichotomy between live and dead views is my main criticism of the framework.
I really wish there was unified APIs for assigns, html templating, sessions, etc...
Bresenham approximates a segment so it skips some cells, Amanatides & Woo gives the exhaustive list of cells touched by it, which is what you want when accelerating raytracing with a grid. No idea if that's relevant here, the screenshots just made me think about a problem I had long time ago :)
Reminds me of Amanatides & Woo traversal
http://www.cse.yorku.ca/~amana/research/grid.pdf?hl=fr-FR
I think the only way to find out is to actually try
What are the safer & saner ways? 🙂
The manual parts of this workflow:
- on Github: choose the base branch when you open a PR
- locally: delete the merged branches and restack
These are handled automatically when you use the GitHub integration.
I use Graphite (CLI only) to manage my stacked branches. One PR per commit, and reviewers review them in the order they want (I would like to use the GH integration, which shows the stack as PR comments).
Each time the PR closest to main is approved I merge it and restack.
Great workflow đź‘Ť
pypi.org/project/ruam...
My mission at PhotoRoom is coming to an end, I had a blast making their editor collaborative in realtime using Rust + Elixir.
I'm looking for remote full time positions, either as an employee or as a freelancer, starting January 2025!
www.linkedin.com/in/luper-rou...
