Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by kmfrk on Thursday November 07, 2013 @03:08PM
(#6692046)
Yeah, these are my only problem with the service; I did not get the metaphors at all, and their descriptions only added to the confusion.
The simplicity of the service is an opportunity to attract people without a lot of webdev chops, so why not make it super simple?
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by pplante on Thursday November 07, 2013 @02:43PM
(#6691908)
I agree with this. I recently wrote a bunch of new Dockerfiles. The Dockerfile name is sort of meh, but "Deck" is not really telling me what its for.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by peteforde on Thursday November 07, 2013 @04:49PM
(#6692649)
Heroku created almost as many new terms as Tolkien, and they seem to have made out just fine.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by gizzlon on Friday November 08, 2013 @03:57AM
(#6695235)
Looked at Heruko once, but all the custom lingo really put me off it.. But, of course your point about them being successful stands
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by mscarborough on Friday November 08, 2013 @10:08AM
(#6696430)
It's worth a shot if they fit your use case. Once you get past the ninja-speak of choosing size and database, it's really simple.
For rake/rails apps at least, you just run `heroku run 'command'` and you're done.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by clebio on Thursday November 07, 2013 @05:15PM
(#6692815)
While I agree with your comment, I hope it isn't used as a measure or justification for doing so. I've had the same cognitive problem with Heroku as the parent describes.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by shiftpgdn on Thursday November 07, 2013 @07:43PM
(#6693651)
God this drives my absolutely insane. Elvish marketing speak is such a stupid waste of time. Why can't we stick to commonly accepted terms instead of trying to bake up new "Cloud"esque replacement terms.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by edbyrne on Thursday November 07, 2013 @02:32PM
(#6691842)
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.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by htilford on Thursday November 07, 2013 @02:51PM
(#6691949)
I 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.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by rattray on Thursday November 07, 2013 @03:08PM
(#6692044)
I agree with this, though I'm biased because I personally find [dockerfile image container] clearer than [deck drop instance]. Explicit > flashy.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by _lex on Thursday November 07, 2013 @02:35PM
(#6691856)
I 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.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by antihero on Thursday November 07, 2013 @03:20PM
(#6692111)
Wouldn't "Container" fit the analogy best?
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by gtaylor on Thursday November 07, 2013 @05:41PM
(#6692973)
I'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.
Re:Show HN: Hosted Docker-as-a-Service on SSDs for $5
by nailer on Friday November 08, 2013 @09:12AM
(#6696053)
I'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.
Unless you're going to try and trademark them all.