This is Google solving Google-sized problems. I am afraid the rest of the world will look at this and say - "yeah we want to be like Google and adopt this". That is how Kubernetes took over the world.
I find some stuff really distracting. Sometimes I just get a local copy to get them out of my way as most are trivial to fix, but hard/draining to ignore.
> But I think several of its characteristics resemble IaaS more than PaaS.
I disagree, but I understand why someone would think that, and if I were given an assignment to argue the point then I could probably convince people that K8S is IaaS, too. BUT, I think it's important for us to recognize that K8S is a platform, and by definition, anybody providing you that platform as a service has provided you a PaaS.
Maybe we should just say people don't want IaaS or PaaS, they want Kubernetes as a Managed Platform, or KaaMP! And who doesn't like camp?!
Even though 'context' is mentioned many times in that post, I am still unsure if the power of Cody comes only if you import your repo in sourcegraph. It does not seem like using it within VSCode in your local source directory lets is understand and use everything there, but I am happy to be corrected.
Of course it is working with local files, maybe I phrased it awkwardly. I am just not sure whether it gives you full context if you do that. I have used Cody a few times in the past few months and it's good, but at least its chat feature kept saying it does not have access to the local code. Maybe that's Claude/GPT being honest but when and which local files it picked seemed unpredictable. There's a setting whether you want sourcegraph context or local context only, and from one of the previous announcements I understood it can work with public github repos. Hence my confusion whether it truly and fully can use your local folder by scanning it locally and extracting embeddings or you need it to go through sourcegraph to get the most out of it.
