@Stuart, I was that guy who reported the super zoom issue. I definitely felt angry when it slipped through into the release. It’s especially enraging that many other problems that get reported on this stage get fixed just fine — and in the end nobody just never gets to know about them — and there are a lot of them, those never happened. It’s like preventing problems by going back in time.
Illustrator is hard to develop and maintain. It’s not about new code gets written slowly, it’s about dealing with the legacy code and making all of it working cohesively. A tiniest oversight — and we get guides that don’t hide with their layers, we get missing buttons, blank dialogs, you name it. And all of these are caused by good intentions, by the effort to optimize it, to streamline it, to pay off the UX and tech debt that one inevitably gains in ~30 years of doing anything. Like if none of us here don’t have a shelf they must nail to a wall, or a door to paint... I am not defending the team here. We pay, we use, we report, we expect the attention and care! It’s us getting exhausted, tired, rude... as if the team does not — although I can’t say the team shows anything of this on public.
I’m the first in line to be angry. And this thread, I must say, became a Swamp of Wining :D 'Multithreading' here is believed to be a shiny Shambala that awaits all of those who preaches enough. No, it’s a thing that can crumble the codebase into the chaos. If even a smallest change leads to painful experience, how can anyone here believe the gargantuan effort to make Ai multithreaded all of sudden is going to be anything different? :)
But I should not be angry, as anyone here. And I must rely on facts, right? What I know is that the effort to make Ai multithreaded is something that is happening — right now — and it’s have been in the making for a long time. All new modules that get added, like the Smart Export (which works fast, doesn’t it?), the 3D engine (of course it is), the Image Trace (which becomes less useful, to my taste, but still incredibly fast), — they all use multiple threads. The team looks into those areas that can benefit from multithreading and cautiously, carefully, slowly, to avoid this Jenga tower fall, replace them brick by brick — until it all gets that boost we dream about. We are driving this car, remember? 24/7, and it gets upgraded just below are bottoms.
But it’s not a panacea, not a magical bean, not a finite goal, it's a mundane everyday task. And honestly — some much smaller things make me much more happier that this abstract idea. Have you tried the filtering in Layers, which is available in Beta? Do you try Beta at all? Do you help ourselves to get it the way we, users, want?
In the light of this new info, that now we know is the current state of things — do you think the status of this should be 'Started'?

Adobe,,,what if I told you,.,.,.......multithreading will make it easier to do all the stupid social media sharing stuff that nobody wants...

I now hate gambling with updating illustrator. If it's currently working in a relatively stable fashion and I know how to work around all the myriad stupid things that don't work properly (like editing gradients from the gradients window or unreliable copying of text - 2 of the most annoying at the moment) then I don't bother. It's such a massive pain in the neck and loss of productivity to have to reset keyboard shortcuts, profiles, workspace layout and settings when you roll back a version. It's like admitting defeat if they make it easy to do. A recognition that updates don't necessarily improve user experience, or heaven forbid introduce a new problem like the recent super zoom in and out effect that made it utterly unusable.

I feel for the volunteer testers who flag these things as the guy who reported that issue during beta didn't get his feedback responded to and we get a know about broken 'update'.

Shame as it's juts another slow drip of annoyance for the faithful monthly funders. Grr!

+1 for this. Please. Illustrator is an outrageously poor performer on my computer. Constant freezes. Constant crashes. All kinds of glitches. It's feeling less stable with each release.

actually since 2017 if they wrote 100 lines of code a day for 365 Days for 7 Years, I don't know with 220,000 lines of code maybe they would have rewritten Illustrator from scratch and made it better, stable, fast, ready for the future. They created new software like XD from scratch And maybe now It will pass no to Figma. So wasted time behind XD when they could boost AI and use it for UX interfaces as well.

affinity designer is written from the ground up, they did had some joke of a program before, but they put up the work and made it right.

So adobe with all those millions can't make a program from scratch?

What a joke, they just don't care.

Im guessing Illustrator is a complete mess and any performance improvement will require a rewrite. Yes, it's a massive task but it's been 7+ years and the performance was never acceptable. Are other long unresolved issues related to the core engine?

The team cant seem to fix simple 4+ year outstanding QOL issues like hyphenation or adding HSB.

The team doesnt seem to understand the userbase. The team fails to act or communicate on high priority issues. They release fixes that are broken on release requiring months / years to correct such as Asset Export or Remove Canvas Size. Its very disappointing.

They could secretly pay some mole in Affinity to have him explain how they made the software multicore, have 1000000000% zoom, speed and rapidity, precision in hooking paths (nodes and curves), etc.
it's absurd, affinity should learn from Adobe's mother and not the other way around.

Adobe team, ooh boring, they're talking in that multi-core thread again.
Let's try and get that update on sharing japanese 3D objects on a tablet out this week.

Oh Yeah I totally agree with you it's annoying seeing all these updates with new features when the core program is still slow.

Yeah, I know there have been thoughts here of what's keeping them from fixing it but it would have been a nice gesture of the team if they could at least try to explain why this isn't happening.

Or perhaps it actually is happening but it takes time? Who knows?

I would be in so much better mood if they could go out and say something like "we are working on it but it's difficult but we believe that we might have it all done in two years".

Now it's just frustrating.

@Oskar People here have given thoughts on why they haven't done it, as I'm sure they would have to re-write large portions of the program but there has been silence from Adobe since switching it to Under Review. With the amount they bring in every month they need to bite the bullet and stop kicking the can down the road

@Oskar holy truth, it could be at least 4x faster if it exploited all cores/threads.
Out there it seems that there are processors that also use 24 cores / 32 threads... what are they for if illustrator uses only 1 core?

The thing that makes me angry is that I see illustrators wasting time (wheel spinning to think) even for simple operations and non-demanding files (zero effects).

Oskar they don't even pretend to be working on it. They don't care, end of story for us. They grab the money and call it a day.

Does anyone know if Illustrator team has provided any feedback on this one? I mean have they presented some thoughts on why they haven't managed to fix this?

It's incredible to see the Activity Monitor showing activity in 1 out of 12 cores in my new Mac Mini when I work in Illustrator. The frustration of knowing this could be almost 12 times faster...

Under review since 2017 .... joke

@Adobe, if your bean bag coders don't know how to do it, they can ask ChatGPT

25 seconds to open a document on a 13900k with RTX 4090, 64GB DDR5 RAM and nvme 4.0 with 7600 MB/s... hylarious...

Not to mention when the file is finally loaded, GPU changes tu CPU preview..... OH MY GOD.... Change this please......

Multithread please.... "force GPU" to not change to CPU please.... we need to work faster... i can learn a new language while waiting Ilustrator .... for sure....

We are at about 6 years since this was requested. It is the 5th most requested upgrade to Adobe's software. I have a $5,000 custom built PC that runs circles around anything I throw at it. That is anything with the exception of Adobe Illustrator. When I open customer PDF files exported from AutoCAD and try and extract the vectors to separate layers it's just impossible. I click on something and wait forever for it to register. Utilizing only 1 thread for the bulk of the work is absolutely ridiculous. This is what most everyone feared about the subscription based model that they strong armed everyone in to by not offering upgrades to new versions as software used to be. Adobe has collected years worth of subscriptions from countless users and can't be bothered to use that to actually upgrade the software to solve this issue. They have you on the hook and they have you perpetually paying for a product and have ignored your requests to make this software utilize a computers full capacity for 6 years. Thank you Adobe for confirming our fears were not unfounded...

No idea, why. But if 3D tasks can use full CPU, RAM and GPU, why can't other tasks?

Users should be able to decide how many resources some tasks can handle, like in Photoshop, you decide how much RAM to allocate and how much GPU RAM to allocate for 3D tasks.