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

91–100 of 359 posts

Re: Why Nextcloud feels slow to use

#91

Post by Yie1cho »

MrDresden wrote: post #43
Yie1cho wrote: post #31

nextcloud just feels abandoned, even if it isn't of course. maybe paying customers are getting a different/updated/tuned version of it. maybe not. but the only thing that keeps me using it is there isn't any real selfhosted alternatives. why is it slow? if you just blink or take a breath, it touches the database. years ago i've tried to optimise it a bit and noticed that there are horrible amount of DB transactions t…

I'm not sure why you feel like it is abandoned. There is a steady release cadence and the changelog[0] clearly shows that much is being worked on. [0]: https://nextcloud.com/changelog/#latest32

yes of course there's progress and new features and it's not really abandoned per se.

but the feeling is that the outdated or simply bad decisions aren't fixed or redesigned.

it could be made 100 times better.

Re: Why Nextcloud feels slow to use

#92

Post by moi2388 »

rahkiin wrote: post #83
tripplyons wrote: post #37

I once discovered and reported a vulnerability in Nextcloud's web client that was due to them including an outdated version of a JavaScript-based PDF viewer. I always wondered why they couldn't just use the browser's PDF viewer. I made $100, which was a large amount to me as a 16 year old at the time. Here is a blog post I wrote at the time about the vulnerability (CVE-2020-8155): https://tripplyons.com/blog/nextclou…

I recently needed to show a pdf file inside a div in my app. All i wanted was to show it and make it scrollable. The file comes from a fetch() with authorzation headers. I could not find a way to do this without pdf.js.

The html object tag can just show a pdf file by default. Just fetch it and pass the source there.

What is the problem with that exactly in your case?

Re: Why Nextcloud feels slow to use

#93

Post by Yie1cho »

8cvor6j844qw_d6 wrote: post #51

Is Nextcloud reliable enough for "production" use? Last time I heard a certain privacy community recommended against Nextcloud due to some issues with Nextcloud E2EE.

the question is, what's your use case?

for me it's a family photo backup with calendars (private and shared ones) running in a VM on the net.

its webui is rarely used by anyone (except me), everyone is using their phones (calendars, files).

does it work? yes. does anyone other than me care about the bugs? no. but noone really _uses_ it as if it was deployed for a small office of 10-20-30 people. on the other hand, there are companies paying for it.

for this,

Re: Why Nextcloud feels slow to use

#94

Post by benhurmarcel »

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

I stopped using Nextcloud when the iOS app lost data.

For some reason the app disconnected from my account in the background from time to time (annoying but didn't think it was critical). Once I pasted data on Nextcloud through the Files app integration, it didn't sync because it was disconnected and didn't say anything, and it lost the data.

Re: Why Nextcloud feels slow to use

#95

Post by glenstein »

bfkwlfkjf wrote: post #58

I've never used nextcloud, but I always imagined that the point is you can run services but then plug in any calendar app etc. You don't have to be running nextclouds calendar, I thought. Did I misundestand how it works?

If dav works best for you, you're using it right.

I would assume that the people for whom a slow web based calendar is a problem (among other slow things on the web interface) are people who want to be using it if it performed well.

They wouldn't just make a bad slow web interface on purpose to enlighten people as to how bad web interfaces are, as a complicated way of pushing them toward integrated apps.

Re: Why Nextcloud feels slow to use

#96

Post by Yie1cho »

zdragnar wrote: post #46
robin_reala wrote: post #24

Earlier quoted context omitted.

The complete Doom 2, including all graphics, maps, music and sound effects, shipped on 4 floppies, totalling 5.76MB.

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.

yes, but why isn't it optimised? not as extreme as doom had to be, but to be a bit better? especially the low hanging fruits.

this is why i think there's another version for customers who are paying for it, with tuning, optimization, whatever.

Re: Why Nextcloud feels slow to use

#97

Post by mynameisvlad »

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…

There is no way it’s going to be completely rewritten from scratch in Go, and none of whatever Germany is or isn’t doing affects that in any way shape or form.

Re: Why Nextcloud feels slow to use

#98

Post by hamburglar »

madeofpalk wrote: post #82

I don't think this article actually does a great job of explaining why Nextcloud feels slow. It shows lots of big numbers for MBs of Javascript being downloading, but how does that actually impact the user experience? Is the "slow" Nextcloud just sitting around waiting for these JS assets to load and parse? From my experience, this doesn't meaningfully impact performance. Performance problems come from "accidentally…

It downloads a lot of JavaScript, it decompresses a lot of JavaScript, it parses a lot of JavaScript, it runs a lot of JavaScript, it creates a gazillion onFoundMyNavel event callbacks which all run JavaScript, it does all manner of uncontrolled DOM-touching while its millions of script fragments do their thing, it xhr’s in response to xhrs in response to DOM content ready events, it throws and swallows untold exceptions, has several dozen slightly unoptimized (but not too terrible) page traversals, … the list goes on and on. The point is this all adds up, and having 15MB of code gives a LOT of opportunity for all this to happen. I used to work on a large site where we would break out the stopwatch and paring knife if the homepage got to more than 200KB of code, because it meant we were getting sloppy.

Re: Why Nextcloud feels slow to use

#99

Post by glenstein »

branon wrote: post #11

I have been considering https://bewcloud.com/ + Immich as an alternative Nextcloud's client support is very good though and it has some great apps, I use PhoneTrack on road trips a lot

Fantastic recommendation, it's like exactly what the doctor ordered given the premise of this thread. Does Bewcloud play nice with DAV or other open protocols or (dare I hope) nextcloud apps? I wouldn't mind using nextcloud apps paired with a better web front end.

Re: Why Nextcloud feels slow to use

#100

Post by selectodude »

rkagerer wrote: post #57
selectodude wrote: post #7

Earlier quoted context omitted.

Seafile works pretty well. The iOS app is ass though. Everything else is rock solid.

Where does it store metadata like the additional file properties you can add? Does it use Alternate Data Streams for anything? Does the AI run locally? For anyone who might find it useful, here's a Reddit thread from 3 years ago on a few concerns about SeaFile I'd love to see revisited with some updated discussion: https://www.reddit.com/r/selfhosted/comments/wzdp2p/are_ther...

Seems like the AI runs wherever you want it - you enter an API endpoint.

https://manual.seafile.com/13.0/extension/seafile-ai/

Post reply on HN