Hacker News new | ask | show | jobs
by stimpson_j_cat 1480 days ago
Calendar apps are so complicated and tightly integrated with other productivity apps now I'm not sure the benefit of simplicity here outweighs the cost of losing that.

My Google cal emails me notifications, works with desktop calendar apps, integrates with Maps, etc. It autofills addresses, adjusts for time zones, syncs across my 4000 devices, allows me to edits dates via text input or GUI/drag 'n drop, etc. (Not shilling, Apple cal is probably similar.)

Even my todo list went from org mode to Google Tasks because of the integrations with Android, Google Calendar, etc.

6 comments

I think you have it slightly backwards (or should).

There's an open standard, icalendar (https://icalendar.org/) which represents calendar entries. Invitations you get in the mail come this format too. The easiest way for your map, address book, reminders etc to integrate is just to talk to your calendar server. The apps need not know about each other at all.

Google and microsoft of course may do some non-standard futzing around within their proprietary stacks: you can often see these problems when you try to connect to something outside their silos, though in my experience the standards integration in google calendaring is pretty good (especially when compared to their mail system). It's been a few years since I had to interface with Exchange calendaring but back then it...wasn't good.

So in any case there's no reason you couldn't write a small service that spoke ical over the network and this plain text calendar's format locally. Then it would appear normally in your partner's iphone, handle your kids' schools' calendars etc.

Whether it would be worth doing that is literally an exercise for the reader...but you'd get the same level of integration as you would with, say, Apple's icloud calendar services.

That's fine in theory but honestly I have bigger fish to fry than rolling my own networked calendar. Much as I'm a big advocate for open source and open specs (even being an author and contributor to a few open source projects too), I have to use these proprietory systems for authentication and email at work anyway. So the convenience of using them for my calendar too far outweighs the cost of rolling my own solution.

This is one of those situations were worse is better.

> There's an open standard, icalendar (https://icalendar.org/) which represents calendar entries. Invitations you get in the mail come this format too. The easiest way for your map, address book, reminders etc to integrate is just to talk to your calendar server. The apps need not know about each other at all.

> Google and microsoft of course may do some non-standard futzing around within their proprietary stacks: you can often see these problems when you try to connect to something outside their silos, though in my experience the standards integration in google calendaring is pretty good (especially when compared to their mail system).

Yes, crossing the two is often still a hot mess.

The first paragraph sounds great in theory. The second paragraph sounds more like what happens in practice...

Well, the real problem is letting big companies get away with shitty implementations.
In any case... here we are, in a world where 95%+ of the people I share / use calendars with are via orgs owned by one of two big tech companies.
>Google and microsoft of course may do some non-standard futzing around

Sadly, in this particular case, I can forgive them. The fact that iCalendar is the best we have is sad. There is a lot of room for improvement.

[link redacted]

> Calendar apps are so complicated and tightly integrated with other productivity apps now I'm not sure the benefit of simplicity here outweighs the cost of losing that.

I've been looking for something like this that will let me edit in plaintext but also sync both ways with gCal for the benefits of plaintext but also the caveats that you mentioned.

I actually built something exactly like this, using the google calendar API and FUSE. It wasn't very difficult at all, I think it took half a day. I'll try to find the code, it's been about a year since I used it since it was just a toy and I didn't want to maintain it.
If you work alone, your calendar and todo lists are what you put there with you as the only editor. So whether, you use pen & paper, a spreadsheet, a text file in Google Drive, or whatever, does not matter to anyone except you. So, whatever works for you. I'm a pen & paper guy. But as soon as you are not working alone, you need different tools. Mostly, my pen & paper work eventually ends up in a proper tool.

Any time slot that matters to me goes into a proper calendar so my time is marked as blocked and people know that I'm busy and don't dump meetings in it. I literally block time to code. Likewise, a lot of my work is coordinating work with others and we use Asana and Github issues for that sort of thing. Other tools are available. But the key feature usually is that you can use them with a team and assign stuff to each other, edit them concurrently, and have some non technical team members doing so as well.

Doing csv exports and imports is feasible for calendars and issue trackers but it doesn't solve a problem I have (except when migrating to different tools). As data input tool that seems not really great. It's actually why I like Asana; I can just type an issue, hit enter, type another one, etc. It feels like a spread sheet tool.

For personal use, it would be much easier using a Calendar service that syncs with our devices and works with our services.

That said, this kind of text format is useful if one needs to keep track of calendar information for a specific project (in a project folder).

The problem is that Google Calendar (and most other widely used calendars) has poor portability. I too use it, because my work uses it, so I have no choice, if I don't want to end up with multiple calendar apps. I hate it for this reason.
> My Google cal emails me notifications

Until you get locked out/banned by Google.