After working with Uplift for several months, the package update, which is a vital part of using a package manager on a daily basis, is a bad experience with a lot of issues.
On larger projects with a lot of direct dependencies and transitive dependencies, the Uplift update window is slow, and reacts poorly, making the package update process for singular packages troublesome.
The update window relies on the current state of dependencies being stable (no resolution conflicts, all packages including installed ones available online...) to be displayed, which means that it cannot be used to actually solve any issue.
There is no GUI for conservative updates, while the functionnality (or at least some form of it) is present in the form of the UpliftManager.InstallStrategy.INCOMPLETE_LOCKFILE strategy.
This results in updating dependencies from the Upfile.xml not being an option, as would be possible on other package managers.
The Update packages option in Uplift menu update all packages as much as possible. This feature, barely ever needed, is incentivised way too much resulting on a lot of users clicking it either by mistake or by confusion. This in turns leads to broken states that need to be cleaned up.
There are still some reliability issues with the existing installing procedure under very specific situations resulting in packages poorly uninstalled, wrong package version being installed...
The issues are hard to replicate, and the context under which they appear even harder to define.
Git LFS has reportedly been slowed down quite a lot by large .gitignore files Issue #2221, Issue #3668 which Uplift tends to create by relying on it to make sure that packages are not added to git.
It is supposed to be addressed by latest versions of Git LFS.