51–60 of 78 posts
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.
Same here. I think that would be a terrific idea. $ cat /cal/2024/08/04/events
$ ls /cal/2024/08/04
$ cat /cal/2024/08/04/*
Earlier quoted context omitted.
Same here. I think that would be a terrific idea. $ cat /cal/2024/08/04/events
So the question begs: how hard would this be to write. Because I want it!
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.
Earlier quoted context omitted.
As a college student trying to figure out where I wanted to go next (industry vs academia) I had an epiphany that there was intrinsic value in doing things. Even things that were neither novel (academia), profitable (industry), nor impactful (nonprofits). While my career has found a balance between impact and financial sustainability, I have a special place in my heart for projects that are otherwise unnecessary but…
But there is no greater pleasure than to finish something, deliver it, get users in front of it, and get feedback you never expected from either grumpy or happy users. I think it's way more rewarding to try to work for profit, because while money is nice, profit also means it's so useful someone is ready to give you credit for future work (money) for what you did.
Profit doesn't inherently mean you've made the median experience of individual humans better, and is just as often to effect significant degradation. My biz was slightly on the positive, but I could have pegged an extra zero in profit if I had forgone scruples.
> Why Did You Do This? > 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—an…
As a college student trying to figure out where I wanted to go next (industry vs academia) I had an epiphany that there was intrinsic value in doing things. Even things that were neither novel (academia), profitable (industry), nor impactful (nonprofits). While my career has found a balance between impact and financial sustainability, I have a special place in my heart for projects that are otherwise unnecessary but…
I don't think it was mentioned in the repo readme, but this will most likely get your account banned. Be careful
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 :)
https://github.com/lvkv/whenfs/commit/618d6c343b2660567256fa...
Earlier quoted context omitted.
So the question begs: how hard would this be to write. Because I want it!
This is essentially just CalDAV[1], no? So a FUSE CalDAV client. Surely not that difficult in Go, Rust or something similar with ready libraries. [1]: https://en.wikipedia.org/wiki/CalDAV
I reckon, yeah.
From this article[1] writing a FUSE filesystem doesn't look that hard.
I might give it a go this weekend. Assuming I remember!
[1] https://blog.trieoflogs.com/2021-05-25-fuse-filesystem-go/