3 ms·
Hi! I can see where you're coming from; however, since this product is initially intended to tightly work in conjunction with Render, which uses the fast.ai nam
by _Tyler 7y ago
Hi! I can see where you're coming from; however, since this product is initially intended to tightly work in conjunction with Render, which uses the fast.ai name in it's repo (https://github.com/render-examples/fastai-v3 https://github.com/render-examples/fastai-v3) and the fact that this model (to my limited knowledge) only works with models produced by fast.ai, making a clear naming distinction was crucial so that someone creating models using another library would realize they couldn't use this. If you have a suggestion for how to make that distinction in a clear and concise manner without coming across as an official product I would definitely be willing to hear you out!
- nl 7y agoWell I don't see why the fact it uses a fast.ai model is particularly relevant for the name. You don't mention PyToch or ResNet of Python or any of the million of other libraries it needs.
- _Tyler 7y agoRight, but this library is designed only to be used with a fast.ai model (and the hope is that fast.ai practitioners will find it helpful). I suppose you could create your own backend that worked with another library if you wanted to take the time, but that's not how it's designed. EDIT: Regardless, I've updated some of the language on the readme to be more clear that this is not an official fast.ai product (and made it more clear in the header that it uses fast.ai models), because I do think your criticism had some validity and I really do appreciate the feedback.