The sentiment is solid, but this is a major software company dropping an update that fails to do BASIC checks (like "is the target directory named what I expect?") before permanently deleting data. Blasting is entirely appropriate.
Software development is hard, managing projects and making stupid decisions is easy.
TL/DR, using Lightroom's import function creates huge amounts of crap video cache files in at least two buried directories regardless if those video files are imported into LR or not. I had a 5-6 GB photo library and 262GB of cache files for video I had not imported. The application has a cache limit, and blew by mine by a factor of 87. Cache purging does not delete the data either.
Anyway, not releated to this particular bug, but I'm not feeling much love for Adobe today.
Kill me now...
/Users/username/Library/Application Support/Adobe/Common/Media Cache Files
/Users/username/Library/Caches/Adobe/Lightroom/Video/Media Cache Files
Windows, you'll have to trawl this thread for probable locations:
That's a joke, right? Software development is hard, but this kind of mistake is indefensible.
Really the problem is just there wasn't a user story saying:
As a user having a directory .AAAAA
When I run an Adobe application
The directory should still be there
If your Agile developers follow user stories to the exclusion of common sense, you should probably fire them now.
It reminds me of this quote:
"There are two ways to develop software: Make it so simple that there are obviously no bugs, or so complex that there are no obvious bugs." - Tony Hoare
I can kill it and it keeps coming back, Freaking annoying, I'm almost to the point of just uninstalling CC from my laptop and leaving it only for my desktop.
No clue what it's doing there but it'll happily spin away for hours at 100% utilization.
kill -SIGSTOP or kill -SIGTSTP
Oh great! I'm glad it just deleted the files but leaves an empty folder intact. Really dodged a bullet there.
People make mistakes during development... but there's no way this should have gotten past even basic QA testing. :(
It sounds like you want those to be steps that come after each other, like some sort of waterfall.
If you want to get with the times, you, the developer, should write a unit test for each file you think shouldn't be deleted on running the application.
That's one way of looking at it. ;)
Another way of looking at it is there shouldn't be a product update/release getting pushed out to hundreds of thousands of users (a guess), without passing an extensive validation suite. Developer unit tests are for a different purpose.
Unless I missed your sarcasm? :)
Nowadays I work in medical devices. It's nice because you're actually legally required to spend 5 minutes making sure your product does what you say it will before you're allowed to sell it, in contrast with what's happened to the rest of the industry.
# chmod +ai "group:everyone deny delete" folder