First - I really want something like this to exists and be great, so best of luck. As of today I'd consider this or Dokploy (Docker Swarm is underrated).
Small feedback - your "Why you should NOT use Canine" section actually is a net-negative for me. I actually was thinking it was cool that it may actually list downsides, but then you did a sarcastic thing that was annoying. I think you should just be frank - you'll have to purchase and manage servers, you'll be on the hook if they go down and have to get them back up, this is an early product made by one person, etc.
I'm all for doing it, the problem as-is is there are real downsides to something like Canine especially when it's super early like this. Posthog gets away with it because they aren't alpha (and have better humor, amongst other things).
It is supported by docker and not abandoned. I just checked latest docker engine release notes and there are multiple fixes and enhancements. Certainly not as popular, compared to Kubernetes, but it is there.
Docker does support a different "Swarm mode" style deployment configuration, which is functionally https://github.com/moby/swarmkit, and really feels much more like Kubernetes to me than the original docker swarm.
I'm... honestly not sure why you'd pick it as a solution over all the k8s tooling they've been doing instead. It feels like the same level of complexity and then only benefit is that it's easier to configure than bare metal k8s, but things like k3s and microk8s tackle that same space.
If anyone is really using the swarm mode for a production service, I'd love to hear different opinions, though!
If I were going to build out bare-metal k8s, I would first try Swarm instead. I would not use k3s or an alternative. The biggest problem with k8s (any version of it) is its overall cost in expertise and maintenance is incredibly high (if you're doing it right; many people are completely ignorant to how terribly they're maintaining it and assume their cost is low). Swarm's cost is going to be significantly smaller, both in the short and long term.
Can you speak more precisely about what costs you think something like k3s imposes that are solved by swarm?
Right now this comment has the same kind of FUD that I see in the swarm docs (there is no "why" to swarm in the docker published docs that feels particularly compelling, especially given the amount of time and energy docker seems to be putting into their k8s tooling instead).
I'm willing to bite - but I run a baremetal cluster on k3s, and it's very simple to keep up to date.
If you don't change the underlying habits it simply doesn't work, like yo-yo diets, like antidepressant, it only works if you actually want help and put in the work, if you just take it as a magic pill you will for sure fail again
That's good, and I hope that one can get off glp 1 quickly too. For anyone with the discipline I'd highly recommend doing it the natural way but if one really can't then I might consider that option.
There aren't any really long term studies of it to show what other effects it might have, though.
Easy to get off. I have a feeling they are actually life extension drugs, even for normal weight people. Just reading many studies and some intuition from taking them (and not being much over).
Pretty valuable to have people who see A to be true, have presumably seen some of B to be true too (trivial to see with the many replication crises) - and then to do their best to disseminate that to the general public so change can be made. I see no problem there, and I'd hate for the case where people were afraid to make content covering it because they were waiting for years for huge studies (which could also be poorly done) to 'prove' it.
You're not explaining why you have such a good feeling - is their team uniquely good, far ahead? Is there something specific in how they architected it? I think a lot of people are headed in this direction, they have a bad brand, the need to totally restructure their team, and probably bad equity structure now and a need for a down round, it'll be hard to get good talent.
The rabbit OS project is literally the only correct path forward for AI. Hopefully they go for local on device inference, as they removes cloud costs, solving the burning pile of cash problem most AI companies have.
Directly driving a user's device (or a device hooked up to a user's account at least) means an AI can do any task that a user can do, tearing down walled gardens. No more "my car doesn't allow programmatic access so I can't heat it up in the morning without opening the app."
Suddenly telling an agent "if it is below 50 outside preheat my car so it is warm when I leave at 8am" becomes a simple to solve problem.
I feel like I am experiencing so peak level trolling right now or am completely out of the loop. Are you guys seriously trying to make the point that that rabbit R1 deceive is the best think to happen to AI?
The idea is a fully personal AI that can control ones devices to accomplish complex tasks. Rabbit is working on this through their rabbitOS project, lots of other players are doing the same thing. OpenAI is trying, and lots of open source projects. Even homekit has initial support for LLM integration.
IMHO controlling a phone directly is the best path forward. Google and Apple are best situated to exploit this, but they may be unable to do so due to structural issues within the companies.
Small feedback - your "Why you should NOT use Canine" section actually is a net-negative for me. I actually was thinking it was cool that it may actually list downsides, but then you did a sarcastic thing that was annoying. I think you should just be frank - you'll have to purchase and manage servers, you'll be on the hook if they go down and have to get them back up, this is an early product made by one person, etc.
reply