What we learned after a year on Kubernetes

Re:What we learned after a year on Kubernetes by kkapelon on Thursday September 17, 2020 @09:04AM (#24504096)

This is of course important but only for people who actually need this guarantee.

Yes if you are developing C/C++/Assembly then Kubernetes/containers might not be for you.

But for several other companies (e.g. Java users) the kernel version is not important.

So we are back to same argument. Just because that you personally don't see value in something, doesn't mean that it is a fad.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by pjmlp on Thursday September 17, 2020 @09:11AM (#24504163)

Java users are doing just fine with application containers.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by kkapelon on Thursday September 17, 2020 @09:17AM (#24504226)

That is a whole different discussion. If by application container you mean Tomcat then maybe. But if you mean Weblogic or Oc4j or WebSphere then hell no :-)

Then maybe you agree that Kubernetes brought some advantages that until recently only Java devs enjoyed to the rest of the world (PHP, Python etc)?

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by pjmlp on Thursday September 17, 2020 @09:58AM (#24504675)

Yes I mean WebSphere.

Kubernetes is a kludge to solve problems that should be sorted out by the respective language communities.

Then there is the whole issue that interpreters without JIT/AOT should only be used for scripting.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by secondcoming on Thursday September 17, 2020 @09:21AM (#24504265)

> Just because that you personally don't see value in something, doesn't mean that it is a fad

GP is the one who made blanket statement 'developers don't want a VM', not me.

[ Parent | on HN ]