WetGeek I pity any new user who tries to install it on their hardware.
I suspect that it is very much luck of the draw. I did a fresh install of Solus Budgie on a replacement SSD last week Thursday, which update 400+ packages after install, using the Software Center, and the process went without a hitch. Similarly, I installed Solus Plasma and Solus Mate on Gnome Boxes VM's in early January, with no issues. No problems at all. On the other hand, I was vexed with numerous, repeating problems a year or two ago doing weekly updates, using both the terminal and the Software Center, and won't be surprised if I am vexed again in the future. In short, I've had my ups and downs.
Staudey Also, as WetGeek has mentioned, the root of the problem is an issue with the server(s) that host the Solus repository. But a new, improved package manager might fail more gracefully or manage to download everything, even if it slows to a crawl, instead of simply aborting the process like eopkg currently does.
I think that it is important to keep in mind that downloading updates is an end-to-end process, and a burp at any point in the infrastructure (server overloads, internet routing and path issues, ISP overloads, local router burps, wireless/ethernet adapter problems, wifi signal interference, and so on) could burp the download process. While the server is the most likely problem in the case of Solus updating, download burps can and do result from issues anywhere in the chain. The Solus team can't do much about most of it.
What the Solus team can do, however, is to work to make the package manager more fault tolerant, along the lines you are suggesting. That won't eliminate burps, but it will mean that a burp is only a burp, not a choking.
