4 ms·
Thanks - we discussed that a lot - we were trying to make a simple 3 steps process. If we get a lot of feedback that it's confusing we'll ditch it.
by edbyrne 13y ago
Thanks - we discussed that a lot - we were trying to make a simple 3 steps process. If we get a lot of feedback that it's confusing we'll ditch it.
- _lex 13y agoI think you need to define your own language if it's better. 'Deck' is clearly better than 'Dockerfile'. Feel free to innovate - you're a startup, and it's what we love about you.
- antihero 13y agoWouldn't "Container" fit the analogy best?
- htilford 13y agoI think that even if [deck drop instance] is clearer than [dockerfile image container] it would be better to use [dockerfile image container] it's the standard set forth from docker, sticking to the standard makes interoperating easier for everyone.
- rattray 13y agoI agree with this, though I'm biased because I personally find [dockerfile image container] clearer than [deck drop instance]. Explicit > flashy.
- gtaylor 13y agoI'd have to agree that the standard Docker terminology would be much preferred. Your business covers what is a pretty cutting edge, advanced concept right now. Your customers are likely to be at least somewhat understanding of the standard terminology. Your custom terminology tripped me up as well, despite having a reasonable grasp of the higher level Docker terminology. Other than that, this looks great! I'm excited for you guys.
- nailer 13y agoI'm in a similar problem space to you. After a year of defining my own 'simpler' terminology, decided to abandon it in favour of being consistent with the more popular albeit complex terminology. I hope that saves you some time.