"M-set anatomy" remake
There are several reasons to remake old Java based pages
JS is easy-to-use because to make rather complex scripts you need not compiler but
just browser and text editor.
- The old version was optimized for 1024×800 screen resolution.
New pages are fitted to your browser window (reload page after resizing window).
It is not clear yet if this fitting suits well for HD displays but simple (non fractal)
boundary length depends on image size only linear.
Therefore it is not necessarily to support in mobile browsers two very similar technologies
(iOS and Android do not support Java applets).
- Multi-touch controls are added for mobile devices.
JS is more restricted than Java and therefore safer
(e.g. JS can not write files to your hard drive).
An Interactive Introduction to Splines remake.
CPU vs. GPU
Modern GPUs generate fractal pictures very quickly. See e.g. WebGL based
Julia sets animation,
animation with the Distance Estimator algorithm
or Makin's fractal animation.
But we can use double floats only in experimental WebCL yet.
Unfortunately direct calculation of all pixels is not power efficient.
The boundary tracing algorithm (see below) is 4-8 times more efficient for the standard
Mandelbrot and Julia sets. It is rather complicated and suits more for CPU.
4 JS workers are used for direct calculations.
The Boundary Tracing algorithm
The Boundary Tracing algorithm [1,2] makes use of the fact that there are not
areas of one color "inside" areas of a different color. This means, that if
you trace the boundary of a region of a single color, then all the pixels
inside that area will have that one color also. In the left image below only
13% of pixels are calculated and all the rest are simply flooded. But it is
evident, that you can get wrong picture (to the right) for very large scale.
Click this image to "repair" it.
 Michael R. Ganss
 John Bailey
Boundary Tracing algorithm
updated 8 Sep 2013