All I ever demanded from my calendaring protocol was to safely and quickly synchronize my calendars between the server and the client. CalDAV has utterly failed

All I ever demanded from my calendaring protocol was to safely and quickly synchronize my calendars between the server and the client. CalDAV has utterly failed at this because it is a complex protocol, and I have no idea how this new protocol improves upon that situation. I don't give a shit about my CalDAV servers talking to each other and "doing scheduling". I use WhatsApp and email for my scheduling. We don't need more features, we need less of them. CalDAV, iTip and iSchedule seem to be designed around the needs of the corporate bureaucratic world, with little to no regard to the average users' needs, and frankly, I'm horrified that for a protocol drafted in the last three years, XML is still used. Simplicity is not just some arbitrary property I'm striving for. It's what all protocols out of the DAV series lack to be actually sensibly implementable. Have you read this thread? People are struggling to mount a simple WebDAV collection, because either the clients or the servers are so bad. And you're talking about scheduling. This isn't even in defense of JMAP. While it at least doesn't try to add crap on top of the crappile, it's just too complex for my usecase either. I guess I'll just stick to remoteStorage and some ics files in it.