[lblume]

> Unix philosophy. It's one day, one line.

The Unix philosophy is often recited as "do one thing, and do it well". This does one thing, but doesn't do it well at all.

[oneeyedpigeon]

Without any explanation, this comment isn't particularly productive. Can you explain how it doesn't do it well?

[jbreckmckye]

I am also sceptical.

It's conflating a format for recording calendars with a syntax the user needs to write.

That syntax looks quite brittle and not very intuitive. One day = one line would get unwieldy fast. It doesn't localise well and there's no obvious way to implement recurring events beyond daily actions. (From what I can see at least?)

You could build a client on top of that but then, you lose the benefit.

It's a neat idea and it's good to see someone share a simple concept that works for them. But I don't see it working for most people.

[woodrowbarlow]

> You could build a client on top of that but then, you lose the benefit.

disagree. having the data in a simple format makes it syncable, trackable, and guarantees that even if you don't have access to the software you're used to, you can always edit it by hand as long as you can access the file.

you can build some software on top of it; or better yet, build sync plugins for existing software, and benefit from nicer UX without giving up the benefits.

[kapep]

I would say it doesn't do anything. It may has well defined what should be done - but doing it well and correctly is burdened upon the user.

[JohnKemeny]

It even says:

> Unix philosophy. It's one day, one line. You can grep (only show lines).

Surprisingly, grep is able to output several lines, so even if you were to use a (say) more sensible format of one line per event, grep could still output all lines, and display them.