Or for another analogy, just substitute the LLM for an outsourced firm. Instead of hiring a firm to do the work, you're hiring a LLM.

This looks very interesting! Do you have any tips/pointers on how one could use Coi to generate a component and then integrate it into an existing project which uses a traditional Javascript framework?

Never forget that the majority of what you see online is biased towards edge framing, being the subject matter incredible or terrible. Just as people curate their online profiles to make their lives appear more "appealing" than they actually are, they do the same curating in other areas.

> edge framing

is this a term of art? I interpreted it as "people only show off the best of the best or the worst of the worst, while the averages don't post online", though I've never heard the term "edge framing" before

Not that I know of, it just occurred to me while trying to be descriptive and succinct at the same time. English isn't my mother tongue.

..and be unemployed.

The article doesn't define any target audience in specific, so there you go.

I don't think learning a new tool will cause you to be unemployed.

They explained it. It goes against the client's goals. Massive investment in customer support? It's about generating leads. I think you're seen it as a SaaS offering which the writer has mentioned multiple times, isn't the case for the client.

"Compatibility issues across system webviews are exceedingly rare, especially for the major operating systems."

When it comes to CSS, there will be the same vendor issues that you have on websites. It's not a magic bullet.

That's a rather obscure conflict, when you think that the two have no domain overlap

If the secrets are in a .env file and you have them in your .gitignore they don't, as you should.

did you miss the part where the agent immediately went around it?

the .gitignore applies to the agent's own "read file" tool. not allowed? it will just run "cat .env" and be happy

The problem lies in the fact that these companies are generating work for volunteers on a different time-scale and binding them to it by giving them X days before disclosing vulnerabilities. No one wants their project to have security vulnerabilities that might affect a lot of users, which creates pressure in dealing with them.

The open source model is broken in this regard, licenses need to address revenue and impose fees on these companies, which can be used as bug bounties. Game engines do this and so should projects like FFMPEG, etc. The details are complex of course, but the current status quo is abusing people's good will.