Except we bundle it with a custom browser renderer which actually generates rewards based on dom diff...and not screenshot based.

the browser renderer is opensource https://github.com/wootzapp/wootz-browser

Comments URL: https://news.ycombinator.com/item?id=46943482

Points: 2

# Comments: 0

In anycase, India generally doesnt honor product patents for pharma. Right now, Indian pharma cos are court empowered to churn out GLP-1.

Everyone knows that we are gonna have 10$ GLP-1 before 2027 coming out of India.

NOTE: kubedock has some automatic compatibility with compose, this is not their goal - https://github.com/joyrex2001/kubedock/blob/e4c8540f63d65e33...

If you are not on the compose ecosystem, this is isnt useful to you.

Just fyi - the hottest thing in the world right now is OpenClaw. This is OpenClaw docker compose yml - https://github.com/openclaw/openclaw/blob/main/docker-compos...

even if you dont do docker compose....everyone else does it anyway.

docker compose is just as heavy. there's not a significant difference between k3s and docker compose.

Also, btw - kappal is architected AI first. Meaning: 1. we have a beautiful skill that can be used by Claude 2. The help command generates output that is useful for claude 3. we have a "kappal inspect" command that generates live output of the stack that can be used by Claude.

hope you have a great time using it. Please file bugs!

At no point, have I invented a new/better method. Perhaps your way is better.

I just recognise that Docker Compose is loved by most open source developers. And invariably any project you touch will have a docker compose setup by default. And it isnt going away, no matter hard anyone tries to kill. Some things are just too well designed. Docker Compose is one of those things.

I'm just making it possible to run those on kubernetes seamlessly.

I'm not arguing for the relative superiority of jsonnet vs yaml vs anything else. I just recognise that Docker Compose is loved by most open source developers. And invariably any project you touch will have a docker compose setup by default.

I'm just making it possible to run those on kubernetes seamlessly.

just curious - i actually didnt focus on healthcheck because i wasnt sure if anyone was using it. are you using it for local dev ?

the standard does not make it mandatory that underlying system should be docker compose (the reference server). it can be anything.

IMHO - kappal is the first project that takes your compose yml file and transparently/drop-in runs it on kubernetes. there is nothing extra you need. It is useful for people who want to maintain their stack as close to production as possible (kubernetes).

If that's not a big goal for you, then this is not very useful for you. But I'd argue ...why do you care if the compose yml is the only think you are using. you get all of kubernetes.

if you ever wanna try it again - use kappal. you will get a full k8s but with the UX of docker compose.

It takes ur standard docker compose file and runs it transparently in kubernetes (k3s actually). So ur devs don't have cognitive dissonance between testing ur stack locally on ur laptop and making it work on kubernetes in production.

It is primarily meant as a dev tool on ur laptop, and as a replacement for docker compose.

Comments URL: https://news.ycombinator.com/item?id=46896105

Points: 50

# Comments: 31

Windows is the best (sandboxed) linux

could make this considerably more robust.

to quote from their paper "In order to ensure sufficient computational performance for DualPipe, we customize efficient cross-node all-to-all communication kernels (including dispatching and combining) to conserve the number of SMs dedicated to communication. The implementation of the kernels is codesigned with the MoE gating algorithm and the network topology of our cluster."