Deleting files extremely slow since OSX High sierra

[Vojtěch Meluzín]

Hi,

I have a custom installer, which places various audio plugins (bundles)
onto the target system and as an uninstaller it removes them. It manages
them the same way as any other folder (containing folders and files). Since
OSX High sierra deleting these files became extremely slow, almost like the
OSX is checking the bundles after every change. On some computers it also
blocks write access to the files inside these bundles (e.g. if the
installer is used again). It almost seems like some pseudosecurity measure
gone wrong, not the first time on OSX after all...

Any ideas what is going on? For the record I'm using FSDeleteObject to
delete files/folders, I know deprecated, but I don't see a reason for
messing up with new API if the old one works.

Thanks in advance.
Vojtech
_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.net

[Richard Charles]

Since OSX High sierra deleting these files became extremely slow, almost like the OSX is checking the bundles after every change.

I have a test machine running High Sierra 10.13.4. Just on Friday I was doing some network testing for a friend, connecting a Windows 10 machine to a macOS High Sierra shared folder. The Mac became extremely sluggish. Every operation that touched the file system became extremely slow even after turning file sharing off. I have never experienced anything like this before. I ended up reinstalling High Sierra to get rid of the problem.

--Richard Charles

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.ne

[Steve Mills]

There’s definitely something rotten in 10.13. After a few days of using Safari, closing windows or doing new searches will take around 30 seconds. Quicklooking jpgs in Finder will become sluggish. Only a robot seems to fix it for a few days, then everything starts slowing down again, getting worse and worse as the days go on.

My thought is the new file system format on my SSD is still full of problems. After all, everything about the format is slower in general.

Steve via iPad
_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent t

[Alex Zavatone]

Playgrounds in Xcode 9.3 are screwed, people can’t delete files, window closes take 40 seconds. VTDecodedXPCservice takes 147% of the processor cores on one of my boxes. How the hell does crap like this ship?

Seriously. Why aren’t people fired for shipping garbage like this?

Post by Steve Mills
There’s definitely something rotten in 10.13. After a few days of using Safari, closing windows or doing new searches will take around 30 seconds. Quicklooking jpgs in Finder will become sluggish. Only a robot seems to fix it for a few days, then everything starts slowing down again, getting worse and worse as the days go on.
My thought is the new file system format on my SSD is still full of problems. After all, everything about the format is slower in general.
Steve via iPad
_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive

[Andreas Falkenhahn]

Post by Alex Zavatone
Seriously. Why aren’t people fired for shipping garbage like this?

Probably because the terms "shipping" and "production build" have lost
much of their significance because fixes can be "shipped" all the time
at absolutely no cost. It's just a push of a button.

Back in the day when new OS versions were shipped on physical media
and put into store shelves, you had to test things *very* carefully
to make sure it was alright. Otherwise heads would surely have rolled
if a company were forced to withdraw millions of media from the shelves.

But today you can just slap out update after update after update and
see what happens. Let's face it, in 2018 we've all become beta testers,
like it or not. It's just so much cheaper than having to do all the testing
inside the company that everybody does it.
--
Best regards,
Andreas Falkenhahn mailto:***@falkenhahn.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This e

[Richard Charles]

Post by Steve Mills
There’s definitely something rotten in 10.13. After a few days of using Safari, closing windows or doing new searches will take around 30 seconds. Quicklooking jpgs in Finder will become sluggish. Only a robot seems to fix it for a few days, then everything starts slowing down again, getting worse and worse as the days go on.

It looks like others are also experiencing slow issues with High Sierra.

https://discussions.apple.com/thread/8155686

Post by Steve Mills
imac unusably slow after high sierra upgrade
i have a 2014 27" i7 retina imac. it has slowed to the point of being unusable after upgrading to high sierra. simply opening finder takes more than 5 minutes before the files are done displaying and the beachball stops.

This sounds exactly like what happened to my High Sierra machine on Friday (2 days ago). This was a clean machine. Very little had been done on the machine since a clean install of High Sierra about one month ago. It happened all of a sudden when I was messing around with file sharing. It was so bad that the only thing I could think of doing was another clean install.

--Richard Charles

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent t

[Rob Petrovec]

Post by Alex Zavatone
VTDecodedXPCservice takes 147% of the processor cores on one of my boxes.

That is to be expected if you are playing any video or audio, and is not new to High Sierra. There are tons of reports online about it taking alot of CPU.


I am not hitting these issues and I use APFS on all my partitions. I don’t have any third party system mods installed on my machine. Maybe its not the file system, but some app you have installed that is effecting the OS? Wouldn’t be the first time that has happened.

Have any of you filed bug reports about the issues you are seeing, including but not limited to a sysdiagnose, spindump, Instruments System Trace taken _while_ the slowness was occurring. If your issue is related to being connected to an SMB share, you should include info about the server you are connecting to (e.g. OS on the Server, WiFi or Ethernet, large or small network etc etc)? If your issue is I/O bound, then an lsof run taken during the slow I/O session is also useful. Without that kind of info there isn’t any way they can possibly fix it. Just sayin’… Maybe reply to this thread with the bug numbers you’ve filed in case an Apple Engineer sees this thread.

—Rob

Post by Alex Zavatone

Post by Steve Mills
There’s definitely something rotten in 10.13. After a few days of using Safari, closing windows or doing new searches will take around 30 seconds. Quicklooking jpgs in Finder will become sluggish. Only a robot seems to fix it for a few days, then everything starts slowing down again, getting worse and worse as the days go on.

It looks like others are also experiencing slow issues with High Sierra.
https://discussions.apple.com/thread/8155686

Post by Steve Mills
imac unusably slow after high sierra upgrade
i have a 2014 27" i7 retina imac. it has slowed to the point of being unusable after upgrading to high sierra. simply opening finder takes more than 5 minutes before the files are done displaying and the beachball stops.

This sounds exactly like what happened to my High Sierra machine on Friday (2 days ago). This was a clean machine. Very little had been done on the machine since a clean install of High Sierra about one month ago. It happened all of a sudden when I was messing around with file sharing. It was so bad that the only thing I could think of doing was another clean install.
--Richard Charles
_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This ema

[Alex Zavatone]

Post by Rob Petrovec

Post by Alex Zavatone
VTDecodedXPCservice takes 147% of the processor cores on one of my boxes.

That is to be expected if you are playing any video or audio, and is not new to High Sierra. There are tons of reports online about it taking alot of CPU.
I am not hitting these issues and I use APFS on all my partitions. I don’t have any third party system mods installed on my machine. Maybe its not the file system, but some app you have installed that is effecting the OS? Wouldn’t be the first time that has happened.

I’ve got 5 Macs. These errors are common across many of them.

Post by Rob Petrovec
Have any of you filed bug reports about the issues you are seeing, including but not limited to a sysdiagnose,

No, because historically, all the time I have spent on reporting issues has been an utter waste of my time.

Recently I reported a text failure in Mail, added instructions and a sample to reproduce it. They reported it fixed. I spent my time to check on the latest Mac OS and it’s not fixed. I marked the bug as Still Open As Written. Nothing’s been done about it since. My time has been triply wasted as a result.

I don’t have time to professionally do Apple’s job for them and they aren’t paying me to. The time I have spent to report bugs over the past 6 years has been an utter waste of my time and effort.

Maybe one issue has been fixed, but the point is that our time is wasted when something fails. We have to spend more of our time to find a workaround. I don’t have time to do that, report their bugs with no guarantee that it may get addressed.

Post by Rob Petrovec
spindump, Instruments System Trace taken _while_ the slowness was occurring. If your issue is related to being connected to an SMB share, you should include info about the server you are connecting to (e.g. OS on the Server, WiFi or Ethernet, large or small network etc etc)? If your issue is I/O bound, then an lsof run taken during the slow I/O session is also useful. Without that kind of info there isn’t any way they can possibly fix it. Just sayin’… Maybe reply to this thread with the bug numbers you’ve filed in case an Apple Engineer sees this thread.
—Rob

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to

[Rob Petrovec]

Post by Alex Zavatone

Post by Rob Petrovec

Post by Alex Zavatone
VTDecodedXPCservice takes 147% of the processor cores on one of my boxes.

That is to be expected if you are playing any video or audio, and is not new to High Sierra. There are tons of reports online about it taking alot of CPU.
I am not hitting these issues and I use APFS on all my partitions. I don’t have any third party system mods installed on my machine. Maybe its not the file system, but some app you have installed that is effecting the OS? Wouldn’t be the first time that has happened.

I’ve got 5 Macs. These errors are common across many of them.

Post by Rob Petrovec
Have any of you filed bug reports about the issues you are seeing, including but not limited to a sysdiagnose,

No, because historically, all the time I have spent on reporting issues has been an utter waste of my time.

For the most part, I have had the opposite experience over the years. Typically, the bugs either gets duped to one they already have, or they ask for additional information which I provide. Sometimes the bug sits for a while, but they all have gotten resolved one way or another. From talking to some Apple Engineers at WWDC over the years, the bar to get a bug fixed in a software update is pretty high. They would rather allow a bug to continue to exist then possibly introduce a regression. Its the devil you know vs the devil you don’t kind of thing with a serious risk vs reward evaluation. It is much easier for them to get a fix into a major release (e.g. 10.13(.0)), so the wait to see a fix is typically over a year.
If you report it and they don’t fix it after a major release, then you have all the right in the world to complain. However, if you don’t report it, IMO, you don’t have any right to complain.

Post by Alex Zavatone
Recently I reported a text failure in Mail, added instructions and a sample to reproduce it. They reported it fixed. I spent my time to check on the latest Mac OS and it’s not fixed. I marked the bug as Still Open As Written. Nothing’s been done about it since. My time has been triply wasted as a result.

How long ago did you mark it SOAW? No offense but if there hasn't been a full OS release cycle since then I think you may be a little overly critical, cynical and impatient. As I said above, getting a bug into a software update is very difficult. The reward has to be significantly higher then the risk. So maybe it will get fixed in the next major release or they are having trouble reproducing or something benign like that?

Post by Alex Zavatone
I don’t have time to professionally do Apple’s job for them and they aren’t paying me to.

I agree. However, you also can’t expect Apple to be able to test all possible configurations or scenarios. That would be physically & statistically impossible. That is one reason they have the beta program, to get a wider audience before the public release. Without (well written) bug reports from devs, they may never know about issues like this. Especially since issues like this are highly configuration dependent.

Post by Alex Zavatone
Maybe one issue has been fixed, but the point is that our time is wasted when something fails. We have to spend more of our time to find a workaround. I don’t have time to do that, report their bugs with no guarantee that it may get addressed.

So by that logic, you are saying that in the products you work on, every single issue reported by users is addressed & fixed in a timely manor? If not, with your relatively small app compared to their huge OS, how could you expect Apple too? If you can’t guarantee that every single user issue is fixed in your products how could you possibly expect Apple? Seriously.

—Rob

Post by Alex Zavatone

Post by Rob Petrovec
spindump, Instruments System Trace taken _while_ the slowness was occurring. If your issue is related to being connected to an SMB share, you should include info about the server you are connecting to (e.g. OS on the Server, WiFi or Ethernet, large or small network etc etc)? If your issue is I/O bound, then an lsof run taken during the slow I/O session is also useful. Without that kind of info there isn’t any way they can possibly fix it. Just sayin’… Maybe reply to this thread with the bug numbers you’ve filed in case an Apple Engineer sees this thread.
—Rob

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email

[Dave]

Post by Rob Petrovec

Post by Alex Zavatone
Recently I reported a text failure in Mail, added instructions and a sample to reproduce it. They reported it fixed. I spent my time to check on the latest Mac OS and it’s not fixed. I marked the bug as Still Open As Written. Nothing’s been done about it since. My time has been triply wasted as a result.

How long ago did you mark it SOAW? No offense but if there hasn't been a full OS release cycle since then I think you may be a little overly critical, cynical and impatient. As I said above, getting a bug into a software update is very difficult. The reward has to be significantly higher then the risk. So maybe it will get fixed in the next major release or they are having trouble reproducing or something benign like that?

Post by Alex Zavatone
I don’t have time to professionally do Apple’s job for them and they aren’t paying me to.

I agree. However, you also can’t expect Apple to be able to test all possible configurations or scenarios. That would be physically & statistically impossible. That is one reason they have the beta program, to get a wider audience before the public release. Without (well written) bug reports from devs, they may never know about issues like this. Especially since issues like this are highly configuration dependent.

Why not? They used to do a *much* better job when they had much lesser resources, now they are rich they really couldn’t care less.

I agree with Alex, reporting bugs in a total waste of time these days.



_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@m

[Steve Mills]

Post by Rob Petrovec
I am not hitting these issues and I use APFS on all my partitions. I don’t have any third party system mods installed on my machine. Maybe its not the file system, but some app you have installed that is effecting the OS? Wouldn’t be the first time that has happened.

Oh, it's the file system.

Post by Rob Petrovec
Have any of you filed bug reports about the issues you are seeing, including but not limited to a sysdiagnose, spindump, Instruments System Trace taken _while_ the slowness was occurring.

Yes. It's still open.

--
Steve Mills
Drummer, Mac geek

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.nar

[Mike Throckmorton]

Try replacing FSDeleteObject with [[NSFileManager defaultManager] removeItemAtPath: pth error: &erro];

Worked for me.

Delete of folder containing 7500 files went from realllly slow down to nice and quick.

I also found that other older FSRef based api's got slow.

Sandboxing? Discouraging use of elderly API's?

Time to ditch the old stuff anyway.

Vojtûch Meluzín Sunday, April 22, 2018 9:55 PM

Post by Vojtěch Meluzín
Hi,
I have a custom installer, which places various audio plugins (bundles)
onto the target system and as an uninstaller it removes them. It manages
them the same way as any other folder (containing folders and files). Since
OSX High sierra deleting these files became extremely slow, almost like the
OSX is checking the bundles after every change. On some computers it also
blocks write access to the files inside these bundles (e.g. if the
installer is used again). It almost seems like some pseudosecurity measure
gone wrong, not the first time on OSX after all...
Any ideas what is going on? For the record I'm using FSDeleteObject to
delete files/folders, I know deprecated, but I don't see a reason for
messing up with new API if the old one works.
Thanks in advance.
Vojtech
_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
https://lists.apple.com/mailman/options/cocoa-dev/mike1throckmorton%40gmail.com

-----------------------------------------------
Mike Throckmorton ***@gmail.com
Software Engineer
My Mac running Mac OS X has been up 4 days,

running Mac OS X and it's starting to drift.

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive

[Vojtěch Meluzín]

Thanks Mike, i'll probably try. I am reluctant to do that, because api is
api and apple forcing devs to change stuff all the time (wasting our time)
is just sad. Plus i just cannot imagine how it could cause things to be
that bad. And finally people here seem to report general problems... Well
apple... Anyways i'll try.

Cheers!
Vojtech
www.meldaproduction.com

Dne po 23. 4. 2018 13:36 uživatel Mike Throckmorton <

Post by Mike Throckmorton
Try replacing FSDeleteObject with [[NSFileManager defaultManager]
removeItemAtPath: pth error: &erro];
Worked for me.
Delete of folder containing 7500 files went from realllly slow down to nice and quick.
I also found that other older FSRef based api's got slow.
Sandboxing? Discouraging use of elderly API's?
Time to ditch the old stuff anyway.
Vojtûch Meluzín Sunday, April 22, 2018 9:55 PM

Post by Vojtěch Meluzín
Hi,
I have a custom installer, which places various audio plugins (bundles)
onto the target system and as an uninstaller it removes them. It manages
them the same way as any other folder (containing folders and files).

Since

Post by Vojtěch Meluzín
OSX High sierra deleting these files became extremely slow, almost like

the

Post by Vojtěch Meluzín
OSX is checking the bundles after every change. On some computers it also
blocks write access to the files inside these bundles (e.g. if the
installer is used again). It almost seems like some pseudosecurity

measure

Post by Vojtěch Meluzín
gone wrong, not the first time on OSX after all...
Any ideas what is going on? For the record I'm using FSDeleteObject to
delete files/folders, I know deprecated, but I don't see a reason for
messing up with new API if the old one works.
Thanks in advance.
Vojtech
_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

https://lists.apple.com/mailman/options/cocoa-dev/mike1throckmorton%40gmail.com
-----------------------------------------------
Software Engineer
My Mac running Mac OS X has been up 4 days,
running Mac OS X and it's starting to drift.

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email

[Steve Mills]

Post by Vojtěch Meluzín
Thanks Mike, i'll probably try. I am reluctant to do that, because api is
api and apple forcing devs to change stuff all the time (wasting our time)
is just sad. Plus i just cannot imagine how it could cause things to be
that bad. And finally people here seem to report general problems... Well
apple... Anyways i'll try.

That's called progress - replacing antiquated APIs and data structures with new and better ones. By all means, keep driving a coal-powered steam car and see how easy it is to buy fuel when every station sells gasoline.

--
Steve Mills
Drummer, Mac geek

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

[Dave]

Post by Steve Mills

Post by Vojtěch Meluzín
Thanks Mike, i'll probably try. I am reluctant to do that, because api is
api and apple forcing devs to change stuff all the time (wasting our time)
is just sad. Plus i just cannot imagine how it could cause things to be
that bad. And finally people here seem to report general problems... Well
apple... Anyways i'll try.

That's called progress - replacing antiquated APIs and data structures with new and better ones. By all means, keep driving a coal-powered steam car and see how easy it is to buy fuel when every station sells gasoline.

Well if you consider the use of “gasoline” as an “update” on steam power, I’d say the same is true. Gasoline which seemed like “progress” at the time has caused more damage to the environment then almost any other man made “device”. Which if you turn this back into operating system speak would also be true, I mean look how much damage the software version of “gasoline” has caused!


_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

[MeldaProduction]

I don't think this is applicable here. If you have a function to "delete a
file", it will still be a function to delete a file, there's no
improvement! Apple is simply covering badly designed APIs, which do work,
they are far from ideal, but they work. If they replace an API, they need
to provide full backwards compatibility. Look at Windows, it's backwards
compatible without problems for like 20 years now (yes I made some hardcore
projects 20 years ago and they still work). So apparently it is possible.
Whenever MS designs something new, the old version still works, may not be
ideal, but let's face it, several times slower file delete because of
backwards compatibility? That's a joke...

Cheers!
Vojtech
www.meldaproduction.com
Facebook <https://www.facebook.com/MeldaProduction>, Twitter
<http://twitter.com/meldaproduction>, Youtube
<http://www.youtube.com/user/meldaproduction>

Post by Steve Mills

Post by Steve Mills

Post by Vojtěch Meluzín
Thanks Mike, i'll probably try. I am reluctant to do that, because api

is

Post by Steve Mills

Post by Vojtěch Meluzín
api and apple forcing devs to change stuff all the time (wasting our

time)

Post by Steve Mills

Post by Vojtěch Meluzín
is just sad. Plus i just cannot imagine how it could cause things to be
that bad. And finally people here seem to report general problems...

Well

Post by Steve Mills

Post by Vojtěch Meluzín
apple... Anyways i'll try.

That's called progress - replacing antiquated APIs and data structures

with new and better ones. By all means, keep driving a coal-powered steam
car and see how easy it is to buy fuel when every station sells gasoline.
Well if you consider the use of “gasoline” as an “update” on steam power,
I’d say the same is true. Gasoline which seemed like “progress” at the time
has caused more damage to the environment then almost any other man made
“device”. Which if you turn this back into operating system speak would
also be true, I mean look how much damage the software version of
“gasoline” has caused!
_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
https://lists.apple.com/mailman/options/cocoa-dev/
meldaproduction%40gmail.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This

[Steve Mills]

Post by MeldaProduction
Apple is simply covering badly designed APIs

So you want to keep using "badly designed APIs"? Why?!

Post by MeldaProduction
Look at Windows, it's backwards
compatible without problems for like 20 years now

"Without problems". That's hilarious.

Post by MeldaProduction
That's a joke...

Says the guy still typing return at the end of every line because that newfangled automatic wrapping is like some kind of voodoo that you don't trust because it's not the way you used to do it all for decades, not to mention typing period period period instead of option-;.

--
Steve Mills
Drummer, Mac geek

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.net

[Matthew Kozak]

LOL, "better" and "badly" are subjective. To belabor your original metaphor, if Apple is indeed selling gasoline cars, we're still looking for hybrid/electric ones. if only we could have skipped the gasoline and had thoughtful development right to solar/electric/etc. (instead of climate change). I don't think backward compatibility is necessarily the solution (and Windows is no beacon of hope for good dev), but removing useful capability for no good reason is just plain stupid.

A lot of recent changes at Apple are not "better", just because they're changes/new/different (disbanding the router team  <https://9to5mac.com/2018/01/10/apple-mesh-wifi-system-airport/>instead of keeping-up with new WiFi developments and saturating the home with a full/robust Apple ecosystem; removing "disablelocal" in High Sierra <https://forums.developer.apple.com/thread/79297>; all of the mess that was/is High Sierra <https://duckduckgo.com/?q=high+sierra+exploit+macos&atb=v109-7_y&ia=web> until 10.13.4 finally(?), releasing iOS11 knowing it did not work with Office 365 <https://forums.developer.apple.com/thread/82279> and so on). It goes well beyond APIs and software devs.

Anyone who'd disagree with even just the few things I listed, you simply reaffirm my actual point. It's not "better", just "different", which too often just plain sucks (or is fan-freaking-tastic, depending on your bent)...

If it ain't broke*,
-Matt

*P.S. To carry your metaphor even further, if you're gonna spruce-up the engine, make sure the thing still has wheels (and round ones, no less) when you're done!

Post by Steve Mills

Post by MeldaProduction
Apple is simply covering badly designed APIs

So you want to keep using "badly designed APIs"? Why?!

Post by MeldaProduction
Look at Windows, it's backwards
compatible without problems for like 20 years now

"Without problems". That's hilarious.

Post by MeldaProduction
That's a joke...

Says the guy still typing return at the end of every line because that newfangled automatic wrapping is like some kind of voodoo that you don't trust because it's not the way you used to do it all for decades, not to mention typing period period period instead of option-;.
--
Steve Mills
Drummer, Mac geek
_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apple.com%2Fmailman%2Foptions%2Fcocoa-dev%2Fmkozak%2540oit.rutgers.edu&data=02%7C01%7Cmkozak%40oit.rutgers.edu%7C642bede014e740f3650708d5aac215ad%7Cb92d2b234d35447093ff69aca6632ffe%7C1%7C0%7C636602672925582681&sdata=kwNs%2BVPF9FBGVllYCgYSvNzY404XwV%2BnNNmk9W0CBTc%3D&reserved=0

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-i

[David Young]

Post by Steve Mills
Says the guy still typing return at the end of every line because that newfangled automatic wrapping is like some kind of voodoo that you don't trust because it's not the way you used to do it all for decades, not to mention typing period period period instead of option-;.

This hateful stuff doesn't really belong on this list, does it?

Maybe this conversation has run its course?

Dave
--
David Young
***@pobox.com Urbana, IL [phone]
_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.net

[Steve Mills]

Post by David Young
This hateful stuff doesn't really belong on this list, does it?

It wasn't hateful, just a further illustration of how he doesn't like change or want to use modern conveniences.

--
Steve Mills
Drummer, Mac geek

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.net

[Rob Petrovec]

apple forcing devs to change stuff all the time (wasting our time) is just sad

FSDeleteObject was deprecated in 10.8. That was 5 releases & 5 years ago. So I don’t know what you mean by “forcing devs to change stuff all the time”. You’ve had 5 years to update your code. They also haven’t killed the API yet. It still works, just slower then you would like. You can’t expect them to keep a deprecated API running perfectly in perpetuity. That would be silly and a waste of Apple’s engineering resources. Its time for you to poop or get off the pot, so to speak.

If you have a function to "delete a
file", it will still be a function to delete a file, there's no
improvement! Apple is simply covering badly designed APIs, which do work,
they are far from ideal, but they work

Its not a design issue here. FSDeleteObject uses FSRef’s. FSRefs were a big improvement over FSSpecs from back in the day, but FSRefs have been deprecated in favor of URLs for years. URLs are leaps and bounds better then FSRef’s. So that is what Apple improved by introducing new API that uses URLs and deprecating the older FSRef equivalents.

Well if you consider the use of “gasoline” as an “update” on steam power,

Fine, then use solar power vs coal, Calculators vs an Abacus, or a MacBook Pro vs a IBM 026 <https://en.wikipedia.org/wiki/IBM_026> Keypunch (google it) as an analogy. They all apply just as well.

This hateful stuff doesn't really belong on this list, does it?

Agreed.

—Rob

Thanks Mike, i'll probably try. I am reluctant to do that, because api is
api and apple forcing devs to change stuff all the time (wasting our time)
is just sad. Plus i just cannot imagine how it could cause things to be
that bad. And finally people here seem to report general problems... Well
apple... Anyways i'll try.
Cheers!
Vojtech
www.meldaproduction.com
Dne po 23. 4. 2018 13:36 uživatel Mike Throckmorton <

Post by Mike Throckmorton
Try replacing FSDeleteObject with [[NSFileManager defaultManager]
removeItemAtPath: pth error: &erro];
Worked for me.
Delete of folder containing 7500 files went from realllly slow down to nice and quick.
I also found that other older FSRef based api's got slow.
Sandboxing? Discouraging use of elderly API's?
Time to ditch the old stuff anyway.
Vojtûch Meluzín Sunday, April 22, 2018 9:55 PM

Post by Vojtěch Meluzín
Hi,
I have a custom installer, which places various audio plugins (bundles)
onto the target system and as an uninstaller it removes them. It manages
them the same way as any other folder (containing folders and files).

Since

Post by Vojtěch Meluzín
OSX High sierra deleting these files became extremely slow, almost like

the

Post by Vojtěch Meluzín
OSX is checking the bundles after every change. On some computers it also
blocks write access to the files inside these bundles (e.g. if the
installer is used again). It almost seems like some pseudosecurity

measure

Post by Vojtěch Meluzín
gone wrong, not the first time on OSX after all...
Any ideas what is going on? For the record I'm using FSDeleteObject to
delete files/folders, I know deprecated, but I don't see a reason for
messing up with new API if the old one works.
Thanks in advance.
Vojtech
_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

https://lists.apple.com/mailman/options/cocoa-dev/mike1throckmorton%40gmail.com
-----------------------------------------------
Software Engineer
My Mac running Mac OS X has been up 4 days,
running Mac OS X and it's starting to drift.

_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

[Sandor Szatmari]

Post by Rob Petrovec

apple forcing devs to change stuff all the time (wasting our time) is just sad

FSDeleteObject was deprecated in 10.8. That was 5 releases & 5 years ago. So I don’t know what you mean by “forcing devs to change stuff all the time”. You’ve had 5 years to update your code. They also haven’t killed the API yet. It still works, just slower then you would like.

We just recently replaced all the FS…Object code we had. We waited for the API/behavior to mature. There was a lot of churn with Unix permissions, ACLs, attributes… etc. We found that the change started on 10.8 but didn’t quite stabilize until 10.11.

On the 10.11 SDK we were able to get identical if not better attribute preservation and better performance as well.

Am I wrong in remembering that the FS…Object API is not 64bit compatible?

Sandor

Post by Rob Petrovec
You can’t expect them to keep a deprecated API running perfectly in perpetuity. That would be silly and a waste of Apple’s engineering resources. Its time for you to poop or get off the pot, so to speak.

If you have a function to "delete a
file", it will still be a function to delete a file, there's no
improvement! Apple is simply covering badly designed APIs, which do work,
they are far from ideal, but they work

Its not a design issue here. FSDeleteObject uses FSRef’s. FSRefs were a big improvement over FSSpecs from back in the day, but FSRefs have been deprecated in favor of URLs for years. URLs are leaps and bounds better then FSRef’s. So that is what Apple improved by introducing new API that uses URLs and deprecating the older FSRef equivalents.

Well if you consider the use of “gasoline” as an “update” on steam power,

Fine, then use solar power vs coal, Calculators vs an Abacus, or a MacBook Pro vs a IBM 026 <https://en.wikipedia.org/wiki/IBM_026> Keypunch (google it) as an analogy. They all apply just as well.

This hateful stuff doesn't really belong on this list, does it?

Agreed.
—Rob

Thanks Mike, i'll probably try. I am reluctant to do that, because api is
api and apple forcing devs to change stuff all the time (wasting our time)
is just sad. Plus i just cannot imagine how it could cause things to be
that bad. And finally people here seem to report general problems... Well
apple... Anyways i'll try.
Cheers!
Vojtech
www.meldaproduction.com
Dne po 23. 4. 2018 13:36 uživatel Mike Throckmorton <

Post by Mike Throckmorton
Try replacing FSDeleteObject with [[NSFileManager defaultManager]
removeItemAtPath: pth error: &erro];
Worked for me.
Delete of folder containing 7500 files went from realllly slow down to nice and quick.
I also found that other older FSRef based api's got slow.
Sandboxing? Discouraging use of elderly API's?
Time to ditch the old stuff anyway.
Vojtûch Meluzín Sunday, April 22, 2018 9:55 PM

Post by Vojtěch Meluzín
Hi,
I have a custom installer, which places various audio plugins (bundles)
onto the target system and as an uninstaller it removes them. It manages
them the same way as any other folder (containing folders and files).

Since

Post by Vojtěch Meluzín
OSX High sierra deleting these files became extremely slow, almost like

the

Post by Vojtěch Meluzín
OSX is checking the bundles after every change. On some computers it also
blocks write access to the files inside these bundles (e.g. if the
installer is used again). It almost seems like some pseudosecurity

measure

Post by Vojtěch Meluzín
gone wrong, not the first time on OSX after all...
Any ideas what is going on? For the record I'm using FSDeleteObject to
delete files/folders, I know deprecated, but I don't see a reason for
messing up with new API if the old one works.
Thanks in advance.
Vojtech
_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

https://lists.apple.com/mailman/options/cocoa-dev/mike1throckmorton%40gmail.com
-----------------------------------------------
Software Engineer
My Mac running Mac OS X has been up 4 days,
running Mac OS X and it's starting to drift.

_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com

_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
https://lists.apple.com/mailman/options/cocoa-dev/admin.szatmari.net%40gmail.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.

[Sean McBride]

Post by Mike Throckmorton
Try replacing FSDeleteObject with [[NSFileManager defaultManager]
removeItemAtPath: pth error: &erro];

Don't do that, it's sorta-deprecated too. :) You want removeItemAtURL:error:.

Sean


_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.net

[Vojtěch Meluzín]

Thanks Sean, will do!


A little comment for the fabulous Steve Mills:
*Says the guy still typing return at the end of every line because that
newfangled automatic wrapping is like some kind of voodoo that you don't
trust because it's not the way you used to do it all for decades, not to
mention typing period period period instead of option-;. *
Really? I think it would really be hard to find here someone, who would be
willing to go lower than this... But a nice representation of Apple :D

Cheers!
Vojtech
www.meldaproduction.com

Post by Sean McBride

Post by Mike Throckmorton
Try replacing FSDeleteObject with [[NSFileManager defaultManager]
removeItemAtPath: pth error: &erro];

Don't do that, it's sorta-deprecated too. :) You want
removeItemAtURL:error:.
Sean

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.net

[Andreas Falkenhahn]

Post by Sean McBride

Post by Mike Throckmorton
Try replacing FSDeleteObject with [[NSFileManager defaultManager]
removeItemAtPath: pth error: &erro];

Don't do that, it's sorta-deprecated too. :) You want removeItemAtURL:error:.

Good times. So what can we learn from that? Avoid Apple APIs at all costs
if there is a POSIX equivalent: remove() is your best friend :)
--
Best regards,
Andreas Falkenhahn mailto:***@falkenhahn.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.net

[MeldaProduction]

Unfortunately unicode could be quite a problem with that I think.

Cheers!
Vojtech
www.meldaproduction.com
Facebook <https://www.facebook.com/MeldaProduction>, Twitter
<http://twitter.com/meldaproduction>, Youtube
<http://www.youtube.com/user/meldaproduction>

Post by Sean McBride

Post by Sean McBride

Post by Mike Throckmorton
Try replacing FSDeleteObject with [[NSFileManager defaultManager]
removeItemAtPath: pth error: &erro];

Don't do that, it's sorta-deprecated too. :) You want

removeItemAtURL:error:.
Good times. So what can we learn from that? Avoid Apple APIs at all costs
if there is a POSIX equivalent: remove() is your best friend :)
--
Best regards,
_______________________________________________
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
https://lists.apple.com/mailman/options/cocoa-dev/
meldaproduction%40gmail.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.net

[Andreas Falkenhahn]

Post by MeldaProduction
Unfortunately unicode could be quite a problem with that I think.

No big deal... just have Cocoa convert your string to precomposed
or decomposed UTF-8. Both should work just fine with everything
POSIX. Just keep in mind that when you obtain file system information
from POSIX it will be in decomposed UTF-8 which is quite weird but
if it were just like on Linux where would that leave the fun ;)
--
Best regards,
Andreas Falkenhahn mailto:***@falkenhahn.com

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkive.net

[Jens Alfke]

Post by Andreas Falkenhahn
No big deal... just have Cocoa convert your string to precomposed
or decomposed UTF-8.

Just use NSString.fileSystemRepresentation, and -[NSString initWithFileSystemRepresentation:] to go the other way. They are guaranteed to do the proper encoding/decoding. (There are CF equivalents too.)

—Jens
_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

[MeldaProduction]

Interesting!

Cheers!
Vojtech
www.meldaproduction.com
Facebook <https://www.facebook.com/MeldaProduction>, Twitter
<http://twitter.com/meldaproduction>, Youtube
<http://www.youtube.com/user/meldaproduction>

Post by Andreas Falkenhahn
No big deal... just have Cocoa convert your string to precomposed
or decomposed UTF-8.
Just use NSString.fileSystemRepresentation, and -[NSString
initWithFileSystemRepresentation:] to go the other way. They are
guaranteed to do the proper encoding/decoding. (There are CF equivalents
too.)
—Jens

_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.

[Igor Mozolevsky]

On 22 April 2018 at 20:55, Vojtěch Meluzín <***@gmail.com>
wrote:

<snip>

Post by Vojtěch Meluzín
Since
OSX High sierra deleting these files became extremely slow, almost like the
OSX is checking the bundles after every change. On some computers it also
blocks write access to the files inside these bundles (e.g. if the
installer is used again). It almost seems like some pseudosecurity measure
gone wrong, not the first time on OSX after all...
Any ideas what is going on?

<snip>

Shooting in the dark here, what's the FS, I wonder if it's the new
filesystem that's propagating size changes all the way up to /
--
Igor M.
_______________________________________________

Cocoa-dev mailing list (Cocoa-***@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/gegs%40ml-in.narkive.net

This email sent to ***@ml-in.narkiv