Why not? that's a _tiny_ amount of data for a modern computer.
I'd rather have a few gigabytes on my machine than have all the code I write automatically in the cloud.
1) kite is useless (or at least substantially less useful) if you explicitly disable files/directories.
Example: Customer says: This fridge I bought, poisons my good. Company: If you don't put your food into fridge its not poisoned. Yeah, but it also not frozen afterwards, which was the reason for the fridge! And no files/directories/lines/whatever policy does solve that problem. Partially because of 2)
2) Human errors will kill this. Just google for number of problems around security tokens, sshkeys and other thing commited to github by mistake.
The only solution is LOCAL index only.
One of the big things we've worked on over the past few months is giving users fine grained control of which files are indexed by kite:
- Kite only indexes directories that you have explicitly enabled
- You can create a .kiteignore file (same semantics as .gitignore) to exclude specific files / patterns.