certainly speaks to a profound lack of understanding of basics. imagine the ux choices an organization like that would make, if they can't think to highlight a screenshot in an accessible manner of something that's intrinsically a visual product
Meta: This is also a testament to how learning is often incidental. Like I read the comments on this thread and go to another thread for far manager and bam screenshots link on the top right corner.
you get what you pay for? the gripe with the ux is more a wxWidgets issue than a CodeLite issue. IMHO. It does what it claims it does. It doesn't waste cycles on making things pretty, but rather making things functional. Granted, I do wish devs would take some extra time on ux and colors, in this case though - it's out of scope.
However, I do see they support some VSCode themes so maybe in the future the UI could get some love. If you're used to vim and/or unix c/c++ development, you probably don't care - target audience of CodeLite.
Even if it would be running natively, the statement'd be still highly debatable.
But it's Electron based and using TypeScript, which means it uses a lot more electricity than a native solution would (about 20 times [1]), wasting precious resources.
Now consider the fact that this is a product of a company that states "to ensure that technology is inclusive, trusted, and increases sustainability."
The only amazing thing here is the level of hypocrisy, IMHO.
There's a lesser known optimization trick I haven't seen in a while, which is especially effective when a large portion of the Mandelbrot set is visible: there are no holes in it, i.e. it's a compact set.
From an optimization point of view, it means that if a rectangular area's edges contains only values reached the iteration limit without growing larger than the escape value, the entire area belongs to the Mandelbrot set.
The term you're looking for is "simply-connected set."
Simply-connected sets and compact sets are both sometimes informally described as "sets with no holes," but the definition of "holes" is different in both cases.
A compact set contains all of its limiting points (i.e. limits of convergent sequences of points within the set). Therefore it may not have any point-shaped holes. But it may still have a hole shaped like, e.g. an open disc.
To rule out such large holes, you want a simply-connected set, which is a connected set in which any closed path can be continuously shrunk to a point.
Not sure I'd say "no holes", but yes there are no islands, the entire mandelbrot set is connected. However that does not mean that parts of the display that's interesting doesn't cover part of the set, that's not visible in any individual pixel.
For those that want to fly around in the mandelbrot set, even a 2015 desktop can easily keep up, I suggest Xaos which I believe includes all the common mandelbrot optimizations at https://xaos-project.github.io/
There's even a web version at the above URL. It's in most linux repos I tried apt or yum. I couldn't find any docs for what optimizations Xaos uses, but it seems plenty fast for real time zooming, even on old hardware.
I used a recursive way: split the image area, calculate the edges for all, checking edges, and then either fill it, or call the function with the sub-areas's region.
Or you can set up a grid and calculate the chunks.
When I was learning a new language in my collage days, my helloworld used to be implementing a Mandelbrot/Julia set on the given language. A few months ago I decided to look into Rust and started to work on my helloworld in Rust, using RayLib :-)
There was a Mandelbrot/Julia set renderer on the Atari ST that did the exact same thing. Instead of waiting rather long for a pixel-perfect image you could see output immediately and it got more refined with each recursive stage. On a box with a 68000 CPU @ ~8 MHz and no FPU it made for a really nice effect.
A lot of junk mail landed in my mailbox when I moved to a new place, until I put a red dot sticker on it. Within a week or two, they disappeared.
We should implement this "red dot sticker" feature in browsers (with optional exceptions), and pages, services and whatnot should respect it, or they will be facing fines. Fines that really hurt.
I'd never heard of that before. I wish it were a thing where I live. But at least in my apartment complex, the recycling bin is right next to the mailboxes, so I can conveniently just move the junk mail straight from my mailbox to the bin.
The interesting thing is that there was a sticker inside the mailbox already, but it didn't work, my mailbox was filled with junk mail, and I put them in the bins too.
I guess the others don't mind the flyers and stuff, because the bins are still pretty full, every time I check my mailbox.
See?
It's really not that hard, you just need to switch the perspective for a minute: what would I prefer if I were a user?
Hiding the complexity from the user is one step forward to a better UI.
