3 ms·
It has to be an online service until they get the models more refined and hardware advanced enough that you can run these locally. If you can't run the model lo
by eikenberry 4y ago
It has to be an online service until they get the models more refined and hardware advanced enough that you can run these locally. If you can't run the model locally then it might as well be a service you tie into at the service (eg. github) level. That is, IMO, services are most useful with other services.
- andiareso 4y agoI think they are saying the app could be a pre-commit hook where their API is hit before code goes up to remote
- eikenberry 4y agoYes. I'm saying that due to this relying on an external service it would be inappropriate for a pre-commit hook as you could only commit while online.
- habitue 4y agopre-push hook?
- verdverm 4y agogit commit --no-verify ?
- bottled_poe 4y agoIf the developer wants to slow their own development workflow by delaying the code review, that’s.. concerning.
- verdverm 4y agoin what way is your comment pertaining to this thread? If a user is offline, they are not going to be able to push code for review anyway. Either way, it seems prudent to shift validation and checks closer to the developer, before pushing code. Otherwise you end up with a series of commit & push, wait for check, commit & push fixes, wait for check, commit & push more fixes...
- lwhi 4y ago> [...] it would be inappropriate for a pre-commit hook as you could only commit while online. Why does that matter?
- eurasiantiger 4y agoHey, some of us live in caves.
- eloff 4y agoAdd the —no-verify flag when working out of your cave.
- dvngnt_ 4y agoto clarify, i mean the processing would still be done remotely, but it could be done earlier in the cycle