4 ms·

> I assume this is hyperbole, but for anyone who is unfamiliar with either system this statement isn't right And for people who don't know what they are talkin

> I assume this is hyperbole, but for anyone who is unfamiliar with either system this statement isn't right And for people who don't know what they are talking about general reactivity "isn't right" ... not sure why anybody cares about the opinion of those without the requisite understanding. In actual functionality, and applications, LXD does not offer the same functionality as K8S, nor does it claim or attempt to do so. The "similarity" you are pointing out is between K8S container runtimes[1] and LXD - and even they are quite different, and there are already many container runtimes. [1]: https://kubernetes.io/docs/setup/production-environment/container-runtimes/ https://kubernetes.io/docs/setup/production-environment/cont...

hardwaresofton 6y ago
> And for people who don't know what they are talking about general reactivity "isn't right" ... not sure why anybody cares about the opinion of those without the requisite understanding. reactivity = relativity? And as people we must* care about the opinion of people without requisite understanding, because for most pieces of knowledge that is indeed the majority of people. If we ever hope to grow knowledge you normally must get other people involved, so good explanations and keeping in mind the layman when he might wander into the conversation (AKA this thread) is a good idea. > In actual functionality, and applications, LXD does not offer the same functionality as K8S, nor does it claim or attempt to do so. k8s manages the orchestration of compute, network, and storage for applications running on a group of machines, LXD fits this same exact description. > The "similarity" you are pointing out is between K8S container runtimes[1] and LXD - and even they are quite different, and there are already many container runtimes. LXD is not a container runtime -- lxc is the container runtime. LXD manipulates lxc the same way docker swarm manipulates docker, or kubernetes mainpulates docker/containerd to get things done.

hardwaresofton 6y ago

> And for people who don't know what they are talking about general reactivity "isn't right" ... not sure why anybody cares about the opinion of those without the requisite understanding. reactivity = relativity? And as people we must* care about the opinion of people without requisite understanding, because for most pieces of knowledge that is indeed the majority of people. If we ever hope to grow knowledge you normally must get other people involved, so good explanations and keeping in mind the layman when he might wander into the conversation (AKA this thread) is a good idea. > In actual functionality, and applications, LXD does not offer the same functionality as K8S, nor does it claim or attempt to do so. k8s manages the orchestration of compute, network, and storage for applications running on a group of machines, LXD fits this same exact description. > The "similarity" you are pointing out is between K8S container runtimes[1] and LXD - and even they are quite different, and there are already many container runtimes. LXD is not a container runtime -- lxc is the container runtime. LXD manipulates lxc the same way docker swarm manipulates docker, or kubernetes mainpulates docker/containerd to get things done.