|
|
|
|
|
by josephg
19 days ago
|
|
If my goal was to make something that fits in with the existing ecosystem and has the most users possible, I could do that. Try to make some changes which could possibly be upstreamed. Spend my time going back and forth on minutia in github pull requests. Learn Dart. Figure out how to wrap a typescript & dart app in a macOS native window. Or turn to electron. (Yuck.) But I’m optimising for the feeling of joy and agency over my tools. I also want to experiment with p2p / local first data structures in a real app. I could fork immich and rewrite the data model. But that all seems much less fun. At the end of the day, I’m not doing this for other people. I’m doing this for me. Learning dart so I can hack on someone else’s code sounds like a pain in the butt. Not like something I’d want to do for fun on the weekend. Working on someone else’s code seems like a strange default. You and others have jumped on me for wanting to make my own thing instead of using - or forking - someone else’s software. Can you help me understand why? Why would that be the default for a fun hobby project? I’m confused. |
|