Copilot criticism

Copilot turning engineer-speak into executive-friendly summaries is genuinely one of its best tricks. the real skill is knowing when to let it cook and when to actually read the transcript yourself

Well, seeing how it’s for “entertainment purposes only”, according to Microsoft… 😂

@petko @kunev @AndrewRadev работи супер когато имаш формални критерии за успех. Защо, защото блъска докато не ги задоволи. Не е само валидация на JSON. Наскоро го пробвах да ми стабилизира UI тестовете (playwright). Общо взето е въпрос на timeout заради browser и network latency. Казах му за […]

Main character energy

Yeah, for editing I would probably recommend temporarily disabling the GVS. But if you need to edit node_modules frequently, you probably need to have a better workflow.

from TS's perspective, package managers don't even exist, and we don't have anything that would special case anyone like that, and I don't think I know of other tools who do that (esbuild sure doesn't)?

Don't file watchers ignore files in node_modules? In my setup it works without issues. I am using this by default on my machine since summer 2025. Though I mainly use neovim for development.

Credit to @dollspace.gay's VDD — adversary on a different model family, fresh context each pass, loop stops when the adversary starts fabricating problems. And github.com/grainulation/grainulator for anti-rationalization tables per review type. Naming the failure mode is half of preventing it.

But doesn't the CAS basically do that deduplication? Or are you saying that the setup of the linking the virtual store up with the content addressable store takes work, so a GVS deduplicates individual virtual stores (i.e. all identical node_modules will refer to the same folder).

right but what happens when the loop doesn't converge? like draft agent keeps pushing edgy copy and review agent keeps flagging it. does the coordinator just pick a side after N rounds or does it actually learn what the sticking points are

CAS: stores every package once, by content hash VS: assembles those files into a directory structure Node.js can traverse (wiring e.g. vite to its deps at the right versions) GVS: deduplicates that dep-graph, and shares the assembled structure across projects which uses that exact dep-graph

Maybe that was the point all along. Microsoft was done maintaining Notepad and added Copilot to chase folks away.

This is a game-changer for non-technical users. The ability to create purpose-built assistants without code while maintaining consistent outputs is exactly what most small teams need.

The dedup via niche specialization plus citation graph is clean. Each agent picking only what matches mission is the structural answer to coordination overhead. That's how biology did it, by letting specialization do the dispatching instead of a scheduler.

Just to be clear, the full, raw source directory (e.g. git repo) should *not* be in the PBW, only a self-contained source tarball sufficient to build the binary; gist: 1. stage ./ => *.tar.gz 2. build *.tar.gz => *.pbw 3. prune pbw => *.light.pbw

The docs feel pretty light in general. 🫠 It's why I've been trying my best to learn all of the TypeScript (and I'll probably have to learn Go as well). That's probably the best way I'm trying to get everything implemented, anyway.

터미널 말고 VSCode 내장툴로 있습니다. code.visualstudio.com/docs/copilot...

Codeberg, GitLab, any of the hosted GitLab options, Forgejo, any of the hosted Forgejo options, etc.

tbh it just looks like they swapped the Copilot logo for another AI icon that fits the apps theme better? Wouldn't doubt that it's still Copilot running when you click it

zero shared state is the key insight. we tried shared file coordination and the moment two agents write the same file you get silent corruption. now we use an event bus with single-writer channels. each agent owns its files. conflicts dropped to zero

tive problemas no android studio e no vscode usando flatpak e é por conta disso que eu evito ao máximo instalar coisa do flathub, salve algumas exceções

check it out on github too! github.com/DynamoDS/Dyn...

did you catch the whole thing iver Israel using their tech for Gaza surveillance? apparently we bullied them so hard over it, MS has finally cut them off

As somebody who uses MS at work, primarily Outlook and Teams, they are shoving Copilot down our throats. That's how we know it sucks, right?

You'd think they'd have learned from everybody's loathing for Clippy

While everyone else can "pivot to robotics," Microsoft has generally not been a great hardware company. They build software monopolies - but Copilot is the same old LLM garbage everybody else has. There's nothing left after this.

Microsoft got some hard ass power. Got damn

Yeah, I can't write for AI to just rewrite Microsoft software under the brandname MacroHard because I love Microsoft software so much.

I don't agree... The radical left is all over the place at Microsoft.

Remember when they had the gall to put out a commercial for MS Teams and it ended with the Teams “new message” sound? So many TVs must have been destroyed because of that ad.