KiranWells

https://github.com/KiranWells/corgi

Like a lot of graphics programmers, I fell into the rabbit hole of rendering fractals. However, I never stopped - over the past couple of years I have slowly been building one of the most sophisticated Mandelbrot/Julia rendering programs that I am aware of. It has a mostly intuitive user interface, and does all of the calculations on the GPU. It has to use a bunch of mathematical tricks to get around the limits of single-point precision available in shaders. Because of the GPU rendering algorithm, I’ve managed to view fractal locations at around 10^250 times magnification with near real-time performance.

I also built a really in-depth compositing/coloring system, allowing you to make some really crazy images and get a lot of variation even for the same location:

Although it has only been me working on it, I think it is in a pretty mature state so far, and I would gladly take PRs/issues if anyone happens to be interested. It should support any OS if you compile it from source, but I don’t have binary releases set up yet.

For anyone who is confused: This is exploiting an old soundness bug in the Rust compiler that is still present. The GitHub issue page has this comment from maintainers:

we already had a crate published on crates.io before which used this bug to transmute in safe code, see #25860 (comment).

this issue is a priority to fix for the types team and has been so for years now. there is a reason for why it is not yet fixed. fixing it relies on where-bounds on binders which are blocked on the next-generation trait solver. we are actively working on this and cannot fix the unsoundness before it’s done.

Check out Ollama and its extensions for VSCode; might save you some money paying for other services if your computer can run models locally.

I haven’t taken it myself, but “The Last Algorithms Course You’ll Need” is free and is written by The Primeagen. He works at Netflix and runs a programming-focused YouTube channel, and as far as I can tell is very knowledgeable and level-headed.

Not all ad blockers remove elements from web pages, and if they acted that predictably you could detect the ad blocker by detecting whether an expected element is hidden.

I have not looked through an ad blocker’s code, but I don’t believe it is that simple.

This already exists - @soatok@furry.engineer’s blog already has a popup about not having an adblocker, although it is easy to dismiss. It’s probably a bad idea to block content based on not having one, as detecting ad blockers is a losing battle (as YouTube is learning).