![]() |
|
![]() |
| Even if it makes just you happy, it's impactful. You are the person others have to put up with. Making yourself happy improves the world for those around you. |
![]() |
| Aw, that's not what I hoped it would be. An actual file-based calendar UI is a neat idea, where you can (for instance) echo into a file to create a calendar event on the command line. |
![]() |
| I don't see where it's remotely useful, the idea sounds fun but it's not praticle.
Explain how it is better vs having a simple cli that parse args and store that into SQLite. |
![]() |
| I appreciate that they made the calender system pluggable. Don't want to get locked into a single calendar vendor with something as important as your file system! |
![]() |
| Yeah, I’ll update the README to be more specific about this. This is also why I didn’t provide instructions on how to use the tool :) |
![]() |
| I seriously doubt this kind of stuff has ever messed with their bottom line. I think they just really resent users trying to do more with their service than they intended. |
![]() |
| This is unhinged and I love every part of it! Apart from the repo having an attitude I often miss from the modern internet I also learnt something reading the code on how FUSE works! |
> I used this project as an opportunity to learn about Rust and FUSE file systems. I also think it's hilarious.
> Visitors interested in the code should note that this is an irredeemably messy codebase—it's full of hacks, unidiomatic code, and wildly poor design decisions.
> However, visitors should also note that that's okay. The best way to learn something new is to try it out for yourself—and creating a mess is a vital part of that process.
I absolutely love this sentiment. Why do this? Because it’s fun. And messy. And sometimes, that’s okay. Not everything needs to be a product… sometimes it’s enough to do something because you can… or want to… or because $RANDOM reason. I’m very grateful to the author and whoever decided to submit it today.