If I were to hear about it and google it, I’d first search “ink” and then admonish myself for the useless search. If I then searched “ink web” I’d get the React thing. I am not invested in this project. I might stop there.
If I search “ink deploy” I get docs for deploying a different project than the two being discussed, and the second search result is a thread about THIS Ink on HN three days ago. So it’s not impossible to find, but if the necessary differentiation is built into the name they’ll improve discoverability.
Their domain already provides that differentiation. Call it ML Ink. That search brings up their site as the first result.
Is Okta supported for auth, and how does bring your own cloud work? Can you limit it to only being able to deploy certain things, within a particular VPC?
I’d suggest renaming. Ink is already a well known framework for building console apps wit react.
Why would that be necessary? Their product isn't a framework, isn't related to console apps, and isn't directly related to React.
If I were to hear about it and google it, I’d first search “ink” and then admonish myself for the useless search. If I then searched “ink web” I’d get the React thing. I am not invested in this project. I might stop there.
If I search “ink deploy” I get docs for deploying a different project than the two being discussed, and the second search result is a thread about THIS Ink on HN three days ago. So it’s not impossible to find, but if the necessary differentiation is built into the name they’ll improve discoverability.
Their domain already provides that differentiation. Call it ML Ink. That search brings up their site as the first result.
Is Okta supported for auth, and how does bring your own cloud work? Can you limit it to only being able to deploy certain things, within a particular VPC?
imo pro
noob