> While we disagree with some of the arguments and questionable rhetoric and timing of the Rocket announcement
Does anyone care to explain what's suspicious about the timing?
Initial thoughts on the Rocket announcement
21–25 of 25 posts
Re: Initial thoughts on the Rocket announcement
#22Some context, since the article contains neither explanation nor link about "the Rocket announcement":
CoreOS is building a container runtime, Rocket https://coreos.com/blog/rocket/ https://news.ycombinator.com/item?id=8682525
(This appears to be a case where the writer is so immersed in their own world, they forget readers might not be as up to speed as their own colleagues.)
Re: Initial thoughts on the Rocket announcement
#23> While we disagree with some of the arguments and questionable rhetoric and timing of the Rocket announcement Does anyone care to explain what's suspicious about the timing?
DockerCon Amsterdam is later this week. Docker plans to make some announcements during this event.
Re: Initial thoughts on the Rocket announcement
#24> While we disagree with some of the arguments and questionable rhetoric and timing of the Rocket announcement Does anyone care to explain what's suspicious about the timing?
DockerCon Amsterdam is later this week. Docker plans to make some announcements during this event.
Wouldn't it be better (for coreos) to make the announcement after DockerCon, so it if it was FUD docker couldn't counter it all week?
Re: Initial thoughts on the Rocket announcement
#25I see a parallel with what Docker did with LXC and the libcontainer debacle. What comes around goes around ...
That said, I like this announcement. Docker was focusing on becoming an App store. I like that Rocket brings the focus back to technology.