So yes not perfect, bloated js but it works and is maintained.
So I'd rather thanks all developers involved in nextcloud than whine about bloated js.
Good news! You can do both.
Do I need them for my home server? No. Do I need them for my company? Yes, but costs compared to MS 365 are negligible.
The http upload is miserable, it's slow, it fails with no message, it fails to start, it hangs. When uploading duplicate files the popup is confusing. The UI is slow, the addons break on every update. The gallery is very bad, now we use immich.
I feel like > 2kb of Javascript is heavy. Literally not needed.
IMO, the worst offenders are when you bring in charting/graphing libraries into things when either you don't really need them, or otherwise not lazy loading where/when needed. If you're using something like React, then a little reading on SVG can do wonders without bloating an application. I've ripped multi-mb graphing libraries out to replace them with a couple components dynamically generating SVG for simple charting or overlays.
https://dev.to/dehemi_fabio/why-php-is-still-worth-learning-...
On the other hand, in 99.99% of web applications you do not need self baked concurrency. Instead use a queue system which handles this. I've used this with 20 million background jobs per day without hassles, it scales very well horizontally und vertically.
I literally explained why this is not the case.
And Nextcloud being slow in general is not a new complaint from users.
Radicale is a good calendar replacement. I'd rather have single-function apps at this point.
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...
You can try it out easily here: https://peergos-demo.net
Our iOS app is still in the works still though.
Owncloud infinite scale might be the best option for a full featured file sync setup, as thats all it does.