3 ms·

giving yourself (or your llm) infinite future work in maintaining all that duplicated kubernetes source code is a bad idea, surely? the author notes they could

by ewy1 3mo ago

giving yourself (or your llm) infinite future work in maintaining all that duplicated kubernetes source code is a bad idea, surely? the author notes they could have compiled the kubernetes to wasm, but doesn't due to... bundle size? i haven't tried, but surely it wouldn't work because all os-level functionality would cause panics. also the title is false

ballon_monkey 3mo ago
Why is the title false?
- ewy1 3mo ago
  the author paid for a robot to write the software while they watched. it's a bad faith dig at ai-driven development, not the part of the comment that was supposed to be taken seriously, sorry.
  - maddmann 3mo ago
    The author clearly explains his process in detail, explaining the pitfalls. Not sure why you’d make a dig like this. There are some useful insights in the article
stephbook 3mo ago
I've also wondered whether implementing OS calls would have been smarter. Maybe there's already a library that does 90% for you. But then, I get the idea of the project. If you wanted real kubernetes, it's easy to install on any OS or online in a VM. There has to be some cutoff of features where "it runs in the browser" makes sense. I think the project has made a good call here.
- samwho 3mo ago
  Thank you! To address the earlier comment: I didn’t go down the “implement the OS-level stuff required to get k8s to compile to wasm” path due to bundle size, honestly and truly. My testing indicated it could be over 10Mb, and I didn’t want that if I could avoid it. Turns out, I could avoid it. Whether it’s a bad idea remains to be seen. It could be! The project will never have full parity with k8s, and as k8s moves forward I probably won’t keep up. But I think the core of k8s is stable enough that that’s okay, and I can make great content about the bits that don’t change.

3 ms·

giving yourself (or your llm) infinite future work in maintaining all that duplicated kubernetes source code is a bad idea, surely? the author notes they could

by ewy1 3mo ago

ballon_monkey 3mo ago
Why is the title false?
- ewy1 3mo ago
  the author paid for a robot to write the software while they watched. it's a bad faith dig at ai-driven development, not the part of the comment that was supposed to be taken seriously, sorry.
  - maddmann 3mo ago
    The author clearly explains his process in detail, explaining the pitfalls. Not sure why you’d make a dig like this. There are some useful insights in the article
stephbook 3mo ago
I've also wondered whether implementing OS calls would have been smarter. Maybe there's already a library that does 90% for you. But then, I get the idea of the project. If you wanted real kubernetes, it's easy to install on any OS or online in a VM. There has to be some cutoff of features where "it runs in the browser" makes sense. I think the project has made a good call here.
- samwho 3mo ago
  Thank you! To address the earlier comment: I didn’t go down the “implement the OS-level stuff required to get k8s to compile to wasm” path due to bundle size, honestly and truly. My testing indicated it could be over 10Mb, and I didn’t want that if I could avoid it. Turns out, I could avoid it. Whether it’s a bad idea remains to be seen. It could be! The project will never have full parity with k8s, and as k8s moves forward I probably won’t keep up. But I think the core of k8s is stable enough that that’s okay, and I can make great content about the bits that don’t change.