![]() To disable auto update, you either have to add a registry value (eew), or create/modify the configuration file for each and every user on the computer (double eew). ![]() It can be silently installed, and you can change the installation directory, but nothing else can be specified with install arguments, unlike the plethora available with Owncloud. On the other hand, the Nextcloud client comes as an NSIS EXE installer. They are even nice enough to provide options for whether to add a desktop shortcut, to not add the shell extension, to disable auto update, to launch after installation, the installation directory, and whether to reboot if needed. The Owncloud client comes by default as an MSI installer file, which is IMO, about the same as an EXE installer for the average user, but miles better for a sysadmin or someone using something like Chocolatey. ![]() Now, onto the Windows versions specifically. The Nextcloud desktop Linux image is also about 100mb, but it not directly comparable since it is an appimage, which is much more compatible across Linux distros, but means that it has to bundle more things inside the image. On the other hand, the Nextcloud Windows installer weighs in at a chonky 100mb+, and the Mac edition is about 80mb. The Owncloud desktop app manages to fit in smaller than a reasonable 20mb for the Windows and Mac editions, and a tiny 1.5mb for the Debian package. On the other hand, the Nextcloud client cannot even download multiple files in parallel, see issue #976. Delta sync means that it can upload only the parts of the file that have changed, rather than transferring the entire file. The Owncloud client has delta sync capability, while the Nextcloud client does not. That area is their desktop sync client, especially when running on windows. There is one area that is not talked about much in regards to how Nextcloud and Ownclowd have diverged after they forked.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |