Show HN: Hubfs – File System for GitHub(github.com) |
Show HN: Hubfs – File System for GitHub(github.com) |
> I have a few qualms with this app...
Different paths towards the same outcome should multiply, so we can increase the surface area of the bandages on the different pain points along the way.
Maybe to use existing file-based indexing and search tools? I must be missing prime use-cases here.
This could be especially nice with some debugger integration, if you could just step into a library function, and have the corresponding file opened via hubfs...
Any plans to add support for gists to Hubfs?
Or, we could just have the computer do it all for us.
- Less efficient use of bandwidth, as the git protocol is optimised for bulk transfers
- Not resilient against unreliable connectivity
- No support for repositories not hosted on GitHub
Yes, I can think of some.
GmailFS and pyfilesystem (userspace FUSE) and rclone are neat as well.
https://stackoverflow.com/questions/1960799/how-to-use-git-a... explains about the `git push` step that git-remote-dropbox enables: https://github.com/anishathalye/git-remote-dropbox
Locality_of_reference#Matrix_multiplication explains how the cache miss penalty applies to optimizing e.g. matrix multiplication: https://en.wikipedia.org/wiki/Locality_of_reference#Matrix_m...