News for hackers. Stuff that matters.
Re:What job interviews taught me about Kubernetes by BobbyTables2 on Monday June 15, 2026 @07:25PM (#48548470)
Pretty sure if there was a simple alternative, people would hate it.

Everyone initially wants thing A. But then they want to customize it to do all permutations and combinations n of A, B, C. They want it to be extensible. They want redundancy. They want orchestration. They want integration.

It’s why practically every config file format eventually becomes its own scripting language. Even HTML started off simple — now ridiculously complex — all the more ironic since practically nobody writes it by hand. Instead of CSS simplifying it, it became more complex.

There is another thing that is extremely customizable and extensible. It’s called a programming language. People write programs to solve specific problems.

There seems to be a perverse trend of cobbling together a Byzantine mesh of libraries, plugins, and services with complex configuration files to make it do practically everything possible. We just used to write software for such purposes…

And for anyone who thinks HTML is simple… the A (anchor) tag has an “ping” attribute that results in POST requests to a list of URLs when a link is clicked ! The list of attributes and resulting variations in behavior is quite mind boggling. It was supposed to be a damn link! https://html.spec.whatwg.org/multipage/links.html

Re:What job interviews taught me about Kubernetes by chaos_emergent on Monday June 15, 2026 @08:40PM (#48549067)
Totally agree with you. K8s ends up being the simplest solution for a very complex problem
Re:What job interviews taught me about Kubernetes by ajayvk on Monday June 15, 2026 @09:20PM (#48549351)
I don't think you can provide all the features of Kubernetes while reducing the complexity. What is possible is to support a subset of the features of Kubernetes while making it easy to use.

https://github.com/openrundev/openrun is a project I am building. It supports declarative deployments, on a single-node with Docker or onto Kubernetes. The target use cases is limited to standalone web app, like internal tools. No support for stateful services, you manage stateful services yourself. With that simplification, OpenRun provides a much easier developer experience.

Re:What job interviews taught me about Kubernetes by SOLAR_FIELDS on Monday June 15, 2026 @09:33PM (#48549452)
I look forward to the evolution of your project into a less standardized Kubernetes as end users request more and more features of your project.
Re:What job interviews taught me about Kubernetes by ajayvk on Monday June 15, 2026 @11:26PM (#48550197)
Targeting a specific use case (internal tools) should hopefully help avoid feature creep. Also, the goal is that an OpenRun config should work on a single-node with Docker and with Kubernetes. That limits the types of features which can be implemented (for example no Docker Compose support, no Helm support).
Re:What job interviews taught me about Kubernetes by bbkane on Monday June 15, 2026 @10:49PM (#48549938)
Re:What job interviews taught me about Kubernetes by notarobot123 on Tuesday June 16, 2026 @03:32AM (#48551845)
Wow, I didn't know about ping attributes.

Advertisers have really shaped the Web right down to it's core specifications.

Re:What job interviews taught me about Kubernetes by threethirtytwo on Tuesday June 16, 2026 @03:32AM (#48551847)
not true. The market OFTEN prefers simple things over complicated things.
Re:What job interviews taught me about Kubernetes by chvid on Tuesday June 16, 2026 @05:54AM (#48552899)
But there is money in complexity.
Re:What job interviews taught me about Kubernetes by threethirtytwo on Tuesday June 16, 2026 @09:40AM (#48555161)
There is money in simplicity as well. The market demands and prefers it.
Re:What job interviews taught me about Kubernetes by linksnapzz on Tuesday June 16, 2026 @12:37PM (#48557960)
This so isn't true, that it's not even wrong.
Re:What job interviews taught me about Kubernetes by linksnapzz on Wednesday June 17, 2026 @11:06AM (#48571552)
Ahem:

“Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it. And to make matters worse: complexity sells better.” ― Edsger Wybe Dijkstra

Re:What job interviews taught me about Kubernetes by threethirtytwo on Thursday June 18, 2026 @04:37PM (#48591203)
This quote is a common myth and a perversion of what he really said:

“Complexity is a great virtue but it requires hard work to achieve it and education to appreciate it. And to make matters worse: simplicity sells better.” ― Edsger Wybe Dijkstra

That's what he actually said, but many source misattribute the inverted version of the quotation.

Re:What job interviews taught me about Kubernetes by bandrami on Tuesday June 16, 2026 @04:20AM (#48552186)
It was supposed to primarily be a link target as well as possibly a source. Berners-Lee guessed the ratio of in to out wrong there.
Re:What job interviews taught me about Kubernetes by DrScientist on Tuesday June 16, 2026 @05:06AM (#48552554)
+1 on the problem of moving complexity from programming languages to configuration.

One of the main problems here is that programming languages typically have lots of tools to help validate correctness, whereas configuration tools are typically either much less mature or woefully underused.

There is nothing more frustrating in something failing due to a misconfiguration - but you've no idea what the correct value should be.

Re:What job interviews taught me about Kubernetes by sethammons on Tuesday June 16, 2026 @08:57AM (#48554538)
My helm adventures (a while back now, so maybe better these days):

> You have an error in your config on line 1. Good luck.

Re:What job interviews taught me about Kubernetes by jmaw on Tuesday June 16, 2026 @11:06AM (#48556426)
Wait did it actually say "Good luck" in the error message? If so that is hilarious
Re:What job interviews taught me about Kubernetes by aranelsurion on Tuesday June 16, 2026 @06:57AM (#48553314)
There are already simpler alternatives, and yes people hate them too. Usually for the opposite reason of k8s: something they need isn’t included, and now bringing it is difficult or impossible.

Fargate and Cloud Run first come to mind.

Re:What job interviews taught me about Kubernetes by panny on Tuesday June 16, 2026 @09:07AM (#48554718)
>Pretty sure if there was a simple alternative, people would hate it.

>Everyone initially wants thing A. But then they want to customize it to do all permutations and combinations n of A, B, C.

Oh, I wouldn't be so sure of that. Think about Eclipse vs IntelliJ. 10 years ago Eclipse had all the features, and IntelliJ didn't so it was fast. Most developers don't use all the features, so most developers were very happy to move to IntelliJ, even if it was not free. Then IntelliJ spent the next decade building lots of features it didn't have. Now everyone wants off of IntelliJ, because it's no longer fast. Now it's got a lot of "useless" features like Eclipse too.