I ported Kubernetes to the browser
1–10 of 110 posts
Re: I ported Kubernetes to the browser
#2Investing early in this hn post before it’s a banger. Instant classic
Re: I ported Kubernetes to the browser
#3Investing early in this hn post before it’s a banger. Instant classic
100%
Re: I ported Kubernetes to the browser
#4I wonder if stuff like this will also be created when token costs explode.
Re: I ported Kubernetes to the browser
#5[dead]
Re: I ported Kubernetes to the browser
#6Please port Kubernetes to common house flies so that they drop dead out of all the unnecessary overhead. That would be helpful.
Re: I ported Kubernetes to the browser
#7Interesting project and (possibly more) interesting explanation of the development process. I agree with the author that the primary difference between vibe slop and real engineering is just reading the lines of code. However it does feel like we are just on the cusp of only needing to read the tests and _not_ all the lines of code. Maybe a few more model generations and we will be there.
Re: I ported Kubernetes to the browser
#8Perhaps to anticipate the multiple jokes about kube complexity, I think there's an interesting argument to make that something like kube is the necessary complexity level for the kinds of tasks that kube is intended to accomplish, ala Fred Brooks' rule about essential complexity vs accidental complexity.
Kube rapidly becomes accidental complexity when you use it to accomplish things that could be done more simply, of course.
Re: I ported Kubernetes to the browser
#9Please port Kubernetes to common house flies so that they drop dead out of all the unnecessary overhead. That would be helpful.
what will we port to the spiders whose population will otherwise surely explode?
Re: I ported Kubernetes to the browser
#10First thing is first, this is really cool.
This feels like the right way to frame LLM-assisted engineering. AI can generate a shocking amount of code, but the actual value is in the review discipline, and tests around it. The browser Kubernetes angle is cool, but what I find more interesting is the workflow, and especially testing behaviour against k8s instead of just trusting “looks right.” I do wonder how many teams are already doing this level of verification for AI-written code. It might be the direction everyone goes in over the next few years.