Running atlas-cli yields warnings:
I respectfully submit that QuickReload is not a sufficient replacement at this time, as it does not support uploads via HTTP/HTTPS.
Specifically, with atlas-cli I can deploy a plugin to staging or even production via HTTPS with:
ATLAS_OPTS="-Dusername=$USERNAME -Dpassword=$PASSWORD" atlas-cli --server https://devserver -p 443 --context-path / --cli-port 4330
and then 'pi' on the prompt to upload successive versions.
I use atlas-cli to deploy in preference to atlas-debug because my plugin needs real data to work on, backed by a real database, not the empty hsql-backed system atlas-debug gives me. It's also super handy for repeated deploys to staging.
Operating over HTTP/HTTPS is a non-goal with Quick Reload, as that would eliminate the "quick". One is inherently file-based, the other inherently URL-based. Quick Reload will never cover some perfectly legitimate use-cases of atlas-cli, and therefore should not be deprecated.
I am also heavily using atlas-cli and for my Plugin development I can say that every other "hot reload" mechanism is not working as reliable as "atlas-cli" plus "pi" command.
So please let it stay
So, atlas-cli is still mandatory until this has been properly fixed.
There is also the case that QR doesn't work with FishEye/Crucible yet either (I submitted a fix but it's not been released yet).
And QR is useless if you have a project that targets multiple connected apps, QR attempts to load all plugins into all instances regardless of whether the plugin was intended for that instance.
QR isn't fully baked yet, its too early for it to replace atlas-cli entirely.
Removing atlas-cli will make add-on development up to 100x slower.....no kidding. It allows me to (in most situations) compile and redeploy changes in 1 to 2 seconds. Quickreload can take minutes.