soloApr 3

tbh the fact that nextcloud is completely unwilling to take after owncloud and implement a high performance golang backend for some of the more core things is really dumb

like. nextcloud performance is absolutely abysmal. it really needs to be better, yet they won't consider moving off of php

and tbh the bad performance is also likely due to architecture reasons rather than just because it uses php, but rewriting portions of it in go also gives you the chance to improve the architecture

Show threadThin LineApr 3
@solonovamax I think the HUGE amount of JS shipped to the browser does not help, PHP or not.
Show threadsoloApr 3
@thin_line the biggest issue I have with nextcloud is the multi-second page load times, which would be fixed if the backend were faster
Show threadThin Line

@solonovamax I don't know, maybe the backend could be improved. But have you seen the amount of data and requests after one reload on the main page/ file browser view ?

This was without cache, so a bit unfair.

Apr 3 at 6:21pmWeb
Show threadThin LineApr 3
@solonovamax For comparison, #Readeck, go backend with JS client side ish
Show threadThin LineApr 3

@solonovamax And Miniflux, with (probably) even less JS:

19 requests
203.44 kB / 73.85 kB transferred
Finish: 1.90 s

Show threadThin LineApr 3
@solonovamax also go backend
Show threadsoloApr 3

@thin_line yes frontend could definitely be improved, but 5-10s page load is abysmal

and yes I have seen the amount of data transfered

Show threadThin LineApr 3
@solonovamax I agree, it's a major issue for me too :D