[nathanstitt]

hah, so I've been fighting AI all the time as it tries to write all this on it's own vs re-using libraries. To me that's a much safer option, because the libraries all pre-date AI so I assume the authors know what they're doing.

Not to bag on Nextcloud but I do think that this is _much_ easier to understand and maintain, it's standard Go/React/Sqlite, nothing esoteric so if you did need to maintain it I'm sure anyone could pick it up. Of course I don't really know Php so that def flavors my opinions here.

I have an example of a one-shot TODO app: https://github.com/tinycld/todo just to demonstrate what's possible.

[edoceo]

The claims you make about Go/React are similar to the claims made by PHP and Python and JS users. Basically: the thing I'm familiar with is easy - then imply that it would be the same level of easy for others.

This does look easier than Nextcloud however I'm not sure thats the tech-stack. Generally the new project is easier/simpler because it doesn't have so many years of scope-creep, work-arounds, half-imolemented-then-abandond features.

[nathanstitt]

yep very true, everyone has their preferred stack, and greenfield is _always_ easier than maintaining years worth of past code.

I did look really closely at Nextcloud when it came time to leave Google apps. I really wanted it to work but also wanted:

* Realtime updates - Pockebase gives us this for free.

* A native app - React Native <- this one worked out but does cause pain with the web version, some things don't work _quite_ as well as a standard React ap would.

* Lightweight docs that work on mobile. Collabora is very full-featured but is also pretty slow. It remains to be seen if I've successfully here because we're only starting to use our docs "for real"

And also: I'm absolutely sure this has many bugs that I've yet to uncover. All I can say is that I am planning on using it for real-world business stuff so I'm sure we'll be uncovering and fixing them throughout the next year.