Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Nextcloud feels slow to use

ounapuu.ee

Post reply on HN
Print view View original

331–340 of 359 posts

Re: Why Nextcloud feels slow to use

#331

Post by port11 »

riskable wrote: post #190
Joeri wrote: post #173

Earlier quoted context omitted.

That 15mb still needs to be parsed on every page load, even if it runs in interpreted mode. And on low end devices there’s very little cache, so the working set is likely to be far bigger than available cache, which causes performance to crater.

Ah, that's the thing: "on page load". A one-time expense! If you're using modern page routing, "loading a new URL" isn't actually loading a new page... The client is just simulating it via your router/framework by updating the page URL and adding an entry to the history. Also, 15MB of JS is nothing on modern "low end devices". Even an old, $5 Raspberry Pi 2 won't flinch at that and anything slower than that... isn't…

This really is a very wrong take. My iPhone 11 isn't that old but it struggles to render some websites that are Chrome-optimised. Heck, even my M1 Air has a hard time sometimes. It's almost 2026, we can certainly stop blaming the client for our shitty webdevelopment practices.

Re: Why Nextcloud feels slow to use

#332

Post by caspar »

cbondurant wrote: post #72

I've used nextcloud for close to I think 8 years now as a replacement for google drive. However my need for something like google drive has reduced massively, and nextcloud continues to be a massive maintenance pain due to its frustratingly fast release cadence. I don't want to have to log into my admin account and baby it through a new release and migration every four months! Why aren't there any LTS branches? The a…

Been using syncthing with keepass(X/XC) for probably half a decade now and it works great, especially since KeepassXC has a great built-in merge feature for the rare cases that you get conflicts from modifying your vault on different clients before they sync.

The only major point of friction with syncthing is that you should designate one almost-always-on device as "introducer" for every single one of your devices, so that it will tell all your devices whenever it learns about a new device. Otherwise whenever you gain a device (or reinstall etc) then you have to go to N devices to add your new device there.

Oh, and you can't use syncthing to replicate things between two dirs on the same computer - which isn't a big deal for the keepass usecase and arguably is more of a rsync+cron task anyway but good to be aware of.

Re: Why Nextcloud feels slow to use

#333

Post by selfmodruntime »

johnsea wrote: post #80
lompad wrote: post #38

Earlier quoted context omitted.

Recently people built a super-lightweigt alternative, named copyparty[0]. To me that looks like it does everything people tend to need without all the bloat. [0]: https://github.com/9001/copyparty

This is not an alternative as it only covers files. Mind what is in the article: "I like what Nextcloud offers with its feature set and how easily it replaces a bunch of services under one roof (files, calendar, contacts, notes, to-do lists, photos etc.), but ". For us Nextcloud AIO is the best thing under the sun. It works reasonably well for our small company (about 10 ppl) and saves us from Microsoft. I'm very gra…

Germany does fund and work on a couple of serious OSS projects. Look for Opencode. They are also actively working on the matrix spec.

Re: Why Nextcloud feels slow to use

#334

Post by DrammBA »

immibis wrote: post #319
DrammBA wrote: post #289

Earlier quoted context omitted.

Not sure why you took it so personally, I was simply pointing out that if you don't configure a feature then that feature would obviously not work, for example phone sync for google drive won't work if you don't download the google drive app, and lan access for nextcloud won't work if you don't set up lan access.

Except your phone comes with Google Drive and syncs things you don't want it to, so Google can scan your life better.

Last time I checked my iPhone didn't come with Google drive

Re: Why Nextcloud feels slow to use

#335

Post by cess11 »

palata wrote: post #27

I would love to like Nextcloud, it's pretty great that it does exist. Just that makes it better than... well everything else I haven't found. What frustrates me is that it looks like it works, but once in a while it breaks in a way that is pretty much irreparable (or at least not in a practical way). I want to run an iOS/Android app that backs up images on my server. I tried the iOS app and when it works, it's cool.…

WebDAV is a nightmare, breaks when you least need it. Once I moved a few TB over it, it took a week with all the retries and troubleshooting.

As I understand it you can work around it with Nextcloud by running some other transfer service and have it watch and automatically import certain directories.

Re: Why Nextcloud feels slow to use

#336

Post by cess11 »

Imustaskforhelp wrote: post #267
tspng wrote: post #252

Earlier quoted context omitted.

Don't forget, "Lot of the code was written on a mobile phone using tmux and vim on a bus". That's crazy.

I have tried to run micro https://micro-editor.github.io/ on my phone but this is some other beast if someone is running tmux and vim on their phone I have found that typing normally is really preferably on android and usually I didn't like having to press columns or ctrl or anything so as such since micro is really just such a great thing overall, it fit so perfectly that when I had that device, I was coding more ba…

I do a lot of development and sysadmin stuff on phones and tablets, to a large degree due to PentiKeyboard. It helps a lot to see the entire screen and have all the usual keyboard sends that a regular, physical keyboard has.

https://software-lab.de/penti.html

Re: Why Nextcloud feels slow to use

#338

Post by troyvit »

cloudfudge wrote: post #269
hedora wrote: post #238

Earlier quoted context omitted.

If the developers can only get it to run in a pile of ubuntu containers, then it's extremely likely they haven't thought through basic things you need to operate a service, like supply chain security, deterministic builds, unit testing, upgrades, etc.

I see 6 officially supported linux distributions. I don't know where anyone got the idea that they can only get it to run on ubuntu. It's containerized. Who cares what the host os is, beyond "it can run containers"?

Here's where I got it from: https://doc.owncloud.com/ocis/next/depl-examples/ubuntu-comp...

And I wish it was "containerized" but really it's "dockerized" as this thread demonstrates: https://central.owncloud.org/t/owncloud-docker-image-with-ro...

So yeah like I said in my original comment, for personal use it's just not right for me (because I choose not to use docker in my personal projects), but I hope it's right for other people because it looks like a killer app.

I'd definitely like to see what other options are available on other distros so I'll dig through their documentation more.

Re: Why Nextcloud feels slow to use

#339

Post by troyvit »

preya2k wrote: post #262
troyvit wrote: post #121

Earlier quoted context omitted.

The thing I don't get is that based on the article the front-end is as bloated as the back-end. That said there's an Owncloud version called Infinite Scale which is written in Go.[1] Honestly I tried to go that route but it's requirements are pretty opinionated (Ubuntu LTS 22.04 or 24.04 and lots of docker containers littering your system) but it looks like it's getting a lot of development. [1] https://doc.owncloud.…

Most of the OCIS team left to start OpenCloud, which is a OCIS fork. And it's hardware requirements are pretty tame. It's a very nice replacement for Nextcloud, if you don't need the Groupware features/Apps and are only looking for File sharing.

Holy cow this looks awesome. I'm digging in now.

Re: Why Nextcloud feels slow to use

#340

Post by troyvit »

the_pwner224 wrote: post #206
troyvit wrote: post #84

Earlier quoted context omitted.

Syncthing is under my "want to like" list but I gave up on it. I'm a one person show who just wants to sync a few dozen markdown files across a few laptops and a phone. Every time I'd run it I'd invariably end up with conflict files. It got to the point where I was spending more time merging diffs than writing. How it could do that with just one person running it I have no idea.

My Syncthing experience matches Oxodao's. Over years with >10k files / 100 gb, I've only ever had conflicts when I actually made conflicting simultaneous changes. I use it on my phone (configured to only sync on WiFi), laptop (connected 99% of the time), and server (up 100% of the time). The always-up server/laptop as a "master node" are probably key.

That is good advice from both of you. I knew it has to be me because it's honestly one of the most successful and popular open source tools I've worked with. I think I should've made that more clear in my original comment.
Post reply on HN