Mandelbrot Set Explorer(mandelbrot.site) |
Mandelbrot Set Explorer(mandelbrot.site) |
I was surprised that this appears to be calculated entirely on the CPU via Rust code rather than with a GPU shader. The multithreaded JavaScript is indeed interesting though.
[0]: https://github.com/austinksmith/Hamsters.js/tree/master
Anyway, I first generated Mandlebrot sets in 1981 on an Ohio Scientific Challenger 1, printed out on an ASR33 via a homebrew current loop interface. <kerchunk>
I just came across your db48x comments, and since I couldn't reply there (old post), thought I'd catch you here :)
I saw that you're a fan of the hp48, and enjoy loading the different libraries. I recently got into the world of HP calculators, and have been really enjoying the learning experience on HP48GX (via Emu48 on my android).
I've been tinkering with some of the libraries, and would love some opinions on a couple of questions.
- I currently have on my list the following libraries: speedui, erable, alg48, qpi, solvesys, stat48pro. Do you suggest any other libraries to dabble with? Anything that'd improve tthe calculator capabilities in math statistics or finance, or general useful utilities (like SpeedUI). I also came across mathtools but not sure if it adds value. When trying to answer this question I also came across https://mrityunjay.tripod.com/OS/HPUX/hp48/part4/faq.html , but not sure if all said apps (mainly Application and Math ones) are decent and compatible or not.
- Is EQSTAK necessary if SpeedUI is installed, or not really? I ask because Erable suggests installing it, but I think speedui does the same thing?
Thanks :)
https://github.com/no-gravity/WorldWideMandelbrot
Every solution has its pros and cons. I still have not seen one that allows deep zooms (The parent only allows up to 48x zoom for example), is written in JS (parent is written in Rust and then compiled to JS), is fast, has a UI that nicely works on mobile and allows to save arbitrarely high resolutions. If there is none, I'm planning to write one myself.
Thinking about it, this could also be an interesting test on how far AI has come. When will I be able to hand the above text to an LLM and get out an HTML page with all the code that satisfies the above criteria?
I guess it depends how many humans have done the hard way, so the LLM can rip off their code?
Until seeing this website, I'd never even considered what different exponents might do to the image, and was pleased to find a nice logical pattern from changing it, even if the higher exponents don't necessarily have as much interesting stuff going on as you zoom in.
> Multibrot Sets: Beyond the traditional Mandelbrot set, users can explore multibrot sets by adjusting the exponent in the generating formula.
> Customizable Color Schemes: Users can personalize their visual experience by choosing different color schemes.
But I don’t see that option anywhere; did anyone find it? I’m on mobile if that matters.
EDIT: The number of iterations can be changed
E.g.: https://mandelbrot.site/?re=-0.7375916562086786&im=-0.189982...
Fractals are one of those things that just feel "right". You know?
Under the effects of hallucinogens, I found fractals far more noticeable in nature, especially when looking at trees. The branching from the base, off to smaller branches, out to the leaves. I feel like the geometric patterns that appear are somewhat of a fractal-design as well, even though they tend to shift and "breathe". I still enjoy fractals for the way they can be created through math processes, while also showing up in places within nature where there's not a computer anywhere in sight.
If the info is intended to be read by humans, keep it in a human-readable format. That way your project is more likely to _have_ a future.
2. Embrace your tooling.
You are keeping it on Github. GH will render Markdown to HTML for you. Use that. Don't keep it in some format it won't render.
3. Choose the right tools.
YAML is for config files. This isn't a config file.
4. Think about what tools you chose and why.
It may be easy to parse YAML with code, but is that significantly different from how easy it is to parse Markdown with code?
Anyway. You do you. I am not telling you what to do or how to do it. I am merely trying to point out flaws with the current approach.
For example it lets you easily make your own project based on mine which renders the Yaml file in a way that is suitable for reading. Even if I add more attributes to each entry, your version will always stay user friendly by rendering only the attributes that you deem right for your interface.