2,192 karma · joined July 1, 2017
Seriously though, Fable was not that great facing a greenfield subject. It is excellent at oneshotting some math problems, but if you want it to do some cutting edge tech stuff, say like piecing together a new Crossplane XRD, by reading existing Helm chart and with application source code available. I still have to get a few pass for Fable to get it done right, and at this point I may consider making a skill for it. I even gave it the source code of the Crossplane itself and tell it to be careful about CRDs and data flow, but it is still pretty silly. Adaptiveness for Fable is still not great, and I think it is a well known problem for Anthropic, albeit all LLMs do suffer a lot from subjects they don't know and will hallucinate stuff very frequently.
...well, AI infra stacks are more or less k8s/cloud native, especially on the inference side. Nvidia GPU operator plus KubeFlow makes deploying models easy, and I did that manually as well using just the ollama, llama.cpp containers and especially vllm operator. I'm not sure about what's the measuring notation of "large" is, but OpenAI had a blog post about how to manage 7500+ nodes Kubernetes (https://openai.com/index/scaling-kubernetes-to-7500-nodes/). That's 5 years ago and I speculate it will only be even more.
> completely re-implemented under the hood for anything halfway serious
...an example please? I'm building a platform to deploy hundreds of open source apps on Kubernetes, you know, the boring thing you can do with a VPS and maybe use Docker Compose to start -- with an ergonomic twist. I relied on so many features of what Kubernetes and its ecosystem provided, especially with persistent volume, volume snapshot, CRDs and cron job, and all of it is just composed from open source and cloud native software...I'm not sure if that sounds "half way serious" to you.
I know those boring monolithic apps can be done with a VPS, as I exactly came from that background, and I know what the shitty points of having just a VPS are. You don't have a clean control plane, you don't have HA, you don't have distributed storage, and you have to be super aware of the apps that you are deploying with Docker Compose.
What you would think "completely re-implemented under the hood for anything halfway serious", perhaps it means that you don't want to get in the fuzz to manage the complexity and prefer to trade for a far simpler but more primitive solution, and that's totally fine.
Pro tip: Codex seems to love generating great Helm charts so much for some reason unknown. I tried GPT-5.4 high in codex and it easily beats Opus 4.7 max on my own internal helm chart generation benchmark evaluation, which measures HA, deployment and app-specific probes. I've given source code to both Codex and Opus and research about the app config structure, and Codex did so well to just generate secret key-value and convert it to JSON and environ, while Opus insisted on using a dynamic generator at runtime.
> Nomad was cool though
Ahem. I used to deploy Nomad too, but I found it too underwhelming, especially with the networking side of thing.
Consul is perhaps one of the most hated thing in my entire career that I would call it bullshit. I know that later Nomad has its own Raft mode, but the Consul brain rot to me is already very sickening such that I don't want to touch Nomad no more. Vault is fine though, but I prefer OpenBao now.
> Dart is also complete shit: Speed of javascript with verbosity of Java
I don't get where the "speed of javascript" is from. Dart/Flutter is JIT on dev mode, and AOT compiled on production, is that you didn't get the compiler options right?
And also Go. While I'm not a Go guy (speaking as a C# and Rust guy, I did wrote a good amount of Go before) it has a huge dominance in Cloud-Native application. For one, Zitadel, an alternative to Keycloak, is written in Go and only takes a fraction of what Keycloak needs.
Flutter/Dart is catching up, but the ecosystem is still relatively weak.
During the process I learned a lot more about giving a chance for LLM to do commit after its work because it will sometimes just give up. Also learned a hard lesson on C preprocessor and why tokenization is necessary.
Oh, that's the reason the SurrealDB operator was here in the first place because I need the full K8S lifecycle to maintain the database state such as backing up, that is not really doable with Helm.
It is worth a try for startups if you won't mind. Try to vibe code around it and give the data model a new look. I have a prototype project that combines both tree-sitter AST and converted it to JSON, then since SurrealDB accepts JSON as native input I now get free graph lookup on the control flow and easily did ancestry analysis and finding what functions potentially calls to this segement. All of it is in SurrealDB nested graph queries and the performance is alright, but is abysmal in Postgres JSONB since JSONB does not linearize the JSON data structure.
ps: I'm building a K8S operator for deploying SurrealDB with TiKV operator integration too.
> But there's no sense crying over every mistake
> You just keep on trying 'til you run out of cake
What I suggested is to steal the (possibly intermediate) weight in between by sniffing the network communication bus, which means MITM for getting the exact values. Or unless it turns out OpenAI or Anthropic leveraged homomorphic encryption, or I'm not certain how is Anthropic would safely allow Mythos to run on AWS without their control.
LL and LR parser generates different derivation, and as such it is deterministically non-deterministic, hence UB.
Not just like "what kind of gender people I like" this kind of oversimplification but it's more about your attitude towards gender stereotypes and roles, for that's what I saw in a more deep connotation.
I observed this through observation of the attacks to Rust due to the huge presence of LGBT people.
Now while I'm pretty much straight myself, I don't reject LGBT people and don't want to partake in identity politics.
I just want things that works no matter what background you have, yet there are some people attacking Rust because of its inclusiveness nature.
And just like Linux is being perceived as nerdy and geeky and "gaming socks ready", the tokenization of things, and there attaching political meanings to it, are quickly coming to everything, so perhaps I'm too general here as well.
Let's say it is not political, but definitely adding more meanings to its technical origin and nature