How about remove all other frontends and only leave onnx behind.

[lygstate]

No description provided.

[milhidaka]

I think it causes some problem right now, but can be considered as future direction.
Not all operators are supported by ONNX (and export feature of each framework), so user may not be able to export their model as onnx.
WebDNN also does not implement some operators, but user can add their own implementation.

[lygstate]

@milhidaka WebDNN is a accerlation framework, and costs to much time on supporting more frontends: And we have better model converters.,

[lygstate]

@milhidaka And I found the runtime testing not not passed at all, we need focus more important things.
And webdnn doesn't supporting un-even padding size.

[milhidaka]

Thanks for suggestion.
Actually, I agree that current webdnn is relatively complex to add/configure feature, especially by new user.