Live data from Hacker News

Why Nextcloud feels slow to use

ounapuu.ee

211–220 of 359 posts

Re: Why Nextcloud feels slow to use

#212

Earlier quoted context omitted.

The original Doom 2 ran 64,000 pixels (320x200). 4k UHD monitors now show 8.3 million pixels. YMMV. Of course, Doom 2 is full of Carmack shenanigans to squeeze every possible ounce of performance out of every byte, written in hand optimized C and assembly. Nextcloud is delivered in UTF-8 text, in a high level scripting language, entirely unoptimized with lots of low hanging fruit for improvement.

You know apps don't store pixels, right? So why are you counting pixels?

A single picture that looks decent on a modern screen, taken from a modern camera, can easily be larger than the original Doom 2 binary.

Re: Why Nextcloud feels slow to use

#213
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.…

This also happened to me with my nextcloud, thankfully I did not lose any photos. I transitioned to Immich for my photos and have not looked back.

Re: Why Nextcloud feels slow to use

#214

Earlier quoted context omitted.

This made me try it once more and I got something to work with some Blobs, resource URLs, sanitazion and iframes. So I guess it is possible

Yeah, blobs seem like the right way to do it.

There does not seem to be a way to configure anything though. It looks quite bad with the default zoom level and the toolbar…

Re: Why Nextcloud feels slow to use

#215
I know that this is supposed to be targeted at NextCloud in particular, but I think it's a good standalone "you should care about how much JavaScript you ship" post as well.

What frustrates me about modern web development is that everyone is focused on making it work much more than they are making it sure it works fast. Then when you go to push back, the response is always something like "we need to not spend time over-optimizing."

Sent this straight to the team slack haha.

Re: Why Nextcloud feels slow to use

#216

Earlier quoted context omitted.

You know apps don't store pixels, right? So why are you counting pixels?

A single picture that looks decent on a modern screen, taken from a modern camera, can easily be larger than the original Doom 2 binary.

You don't need pictures for a CRUD app. Should all be vectorial in any case.

Re: Why Nextcloud feels slow to use

#217

The major shortcoming of NextCloud, in my opinion, is that that it's not able to do sync over LAN. Imagine wanting to synchronize 1TB+ of data and not being able to do so over a 1 Gbps+ local connection, when another local device has all the necessary data. There is some workaround involving "split DNS", but I haven't gotten around to it. Other than that, I thought NC was absolutely fantastic.

> The major shortcoming of NextCloud, in my opinion, is that that it's not able to do sync over LAN.

That’s an interesting way to describe a lack of configuration on your part.

Imagine me saying: "The major shortcoming of Google drive, in my opinion, is that that it's not able to sync files from my phone. There is some workaround involving an app called 'Google drive' that I have to install on my phone, but I haven't gotten around to it. Other than that, Google drive is absolutely fantastic.

Re: Why Nextcloud feels slow to use

#218

Earlier quoted context omitted.

I was going to say... The size of the JS only matters the first time you download it unless there's a lot of tiny files instead of a bundle or two. What the article is complaining about doesn't seem like it's root cause of the slowness. When it comes to JS optimization in the browser there's usually a few great big smoking guns: 1. Tons of tiny files: Bundle them! Big bundle > zillions of lazy-loaded files. 2. Lots o…

>Do I understand why they're so much lower latency than REST calls on mobile networks? Not really: In theory, it's still a round-trip but for some reason an open connection can pass data through an order of magnitude (or more) lower latency on something like a 5G connection. It's because a TLS handshake takes more than one roundtrip to complete. Keeping the connection open means the handshake needs to be done only on…

doesn’t HTTP keep connections open?

Re: Why Nextcloud feels slow to use

#219

Earlier quoted context omitted.

For your specific use case of photos, Immich is the front runner and a much better experience. Sadly for the general Dropbox replacement I haven't found anything either.

There is also "memories for nextcloud" which basically matches immich in feature set (was ahead until last month), nextcloud+memories make a very strong replacement for gdrive or dropbox

Yeah I guess my issue is that if I can't trust the mobile app not to lose my photos (or stop syncing, or not sync everything), then I just can't use it at all. There is no point in having Nextcloud AND iCloud just because I don't trust Nextcloud :D.

Re: Why Nextcloud feels slow to use

#220

Earlier quoted context omitted.

For your specific use case of photos, Immich is the front runner and a much better experience. Sadly for the general Dropbox replacement I haven't found anything either.

I love immich, too, but I have also ran into a lot of issues with syncing large libraries. The iPhone app will just hang sometimes.

Does it recover though, or do you end up in situations where your setup is essentially broken?

Like if I backup photos from iOS, then remove a subset of those from iOS to make space on the phone (but obviously I want to keep them on the cloud), and later the mobile app gets out of sync, I don't want to end up in a situation where some photos are on iOS, some on the cloud, but none of the devices has everything, and I have no easy way to resync them.

Post reply on HN