P: Saving copy not saving over jpg file

Adobe bought and KILLED Macromedia Freehand... was a much superior product to Illustrator.

Actually Illustrator appeared superior in many regards* for a long time, but definitely not in all.

Those aspects of Freehand that were superior are surely missed. 

And some of them seem so very basic – like the existence of  Connector Points or the Path-closing behaviour. 

I wouldn’t call Illustrator 

abandonware

though, but it does seem like the Illustrator team might not have been getting the resources it needed at all times. 

*) One example would be Illustrator’s Pattern Brush – I am not sure it was called that back then and I don’t remember what Freehand’s corresponding feature was called. But I do remember that Freehand produced a lot more artefacts/errors in the necessary transformations of the »bent« artwork. 

I find it full of issues that would not exist had Adobe actually developed it thoroughly and used real people to provide feedback. 

I like to think you are exaggerating, there is testing and beta-testing.

But when I consider the way the Feature Request for additional grid-lines in Warp-transformations was implemented it seems hard to disagree with you – it looks like the people implementing it did actually flat-out not understand what the Feature Request was about. 

Over a year now with no resolution to the JPG copy issue - that is beyond comprehension. There is no workaround to this

The workaround is to use a Script. 

But this is Adobe's "official" bug-reporting mechanism.

What an offensive joke.

Adobe bought and KILLED Macromedia Freehand... was a much superior product to Illustrator.
So sad!

 This is so well put... please go post this on the Adobe Twitter page every hour until someone gets tired of seeing it?

I'm going to say it again...
Organized, Hourly, Twitter Spamming until this is addressed.
I don't understand why Adobe feels the need to turn Photoshop into 
Snapchat filter heaven... Nice Parlor tricks, but how about a stripped down version minus the BS

for us in the trenches?

Really user hell. When basic functions are either removed or altered without the User in mind, convoluted processes arise without any sense of whether it's a bug or a change in function. Speaking to 1st level Adobe support is simply a waste of time: 1) they are prone to give the wrong information; 2) they don't seem to understand the nature of a problem. I'm not sure if Adobe monitors board activity here. If they don't, then these types of threads are meaningless. If they do, then a rep ought to be posting here about what needs to happen to fix the problem. This is not rocket science, just a logical way to keep everyone in the loop. 🙄                    

Illustrator is abandonware. Adobe should open-source it and be done with it.

I've long since moved on to Affinity Designer and Sketch, both of which have some pretty profound flaws but at least they're being maintained.... and you don't have to rent them.

@oscargoldman - absolutely!

Adobe Illustrator is doing the same.

This is a programmer-prone hell they are creating - gone are the days of real world user development strategies.

I have a list of bugs a mile long for InDesign, Illustrator *and* PhotoShop. But why should I teach Adobe to fix their messes - I'm not being paid. In fact, I am paying a premium to use their products and still not getting the quality that is required. Every time I got back to a feature I haven't used in a while - recently the Perspective grid in Illustrator and Indexing in InDesign - I find it full of issues that would not exist had Adobe actually developed it thoroughly and used real people to provide feedback. They are simply using developers to patch it and throw updates at us every few weeks thinking they're doing something to improve their apps when clearly they are not.

Over a year now with no resolution to the JPG copy issue - that is beyond comprehension. There is no workaround to this - it requires a concerted effort on Adobe's part - but they are not willing to acknowledge nor fix it. And their support staff continue to call it "normal action" and "a feature."?!?!

 Anyone know a good lawyer who would be interested in starting a class action suit? Not for the feint of heart tho - Adobe is likely really lawyered up.

What I find interesting is that THIS issue has garnered so much outrage while other longstanding defects do not.

For example, the one where if you select a different layer, do something, and then press Undo... it undoes your action AND re-selects the previous layer. For example, if you switched from a text layer to a bitmap layer and made a brushstroke, undoing it will not only remove the brushstroke but re-select the text layer... so now you can't make a new brushstroke.