81–90 of 359 posts
syncthing otoh barely even has a web ui, so it's really fast :-P
From my experience, this doesn't meaningfully impact performance. Performance problems come from "accidentally quadratic" logic in the frontend, poorly optimised UI updates, and too many API calls.
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 could not find a way to do this without pdf.js.
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.
Look into syncthing for a dropbox replacement, have been using it for years, very satisfied.
I'm still setting up my own home server, adding one functionality at a time. I wanted to like Nextcloud but it's just too bloated. Radicale is a good calendar replacement. I'd rather have single-function apps at this point.
Any good file syncing/drive replacements? My Synology exists pretty much because Synology Drives works so well syncing Mac and iOS.
Earlier quoted context omitted.
Any good file syncing/drive replacements? My Synology exists pretty much because Synology Drives works so well syncing Mac and iOS.
Pretty happy with Resilio Sync. I use it on Mac, and linux in a docker container.
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…
Overeager warming/precomputation of resources on page load (rather than on use) can be a culprit as well.
Earlier quoted context omitted.
Not paying attention. 1. Indiscriminate use of packages when a few lines of code would do. 2. Loading everything on every page. 3. Poor bundling strategy, if any. 4. No minification step. 5. Polyfilling for long dead, obsolete browsers 6. Having multiple libraries that accomplish the same thing 7. Using tools and then not doing any optimization at all (like using React and not enabling React Runtime) Arguably things…
What is React runtime? I looked it up and the closest thing I came across is the newly announced React compiler. I have a vested interest in this because currently working on a micro-SaaS that uses React heavily and still suffering bundle bloat even after performing all the usual optimizations.