Amazon

Would have been much cheaper in the first case on Cloudflare

Wow what a terrible and misleading article

is it not a file exfiltrator, as a product

Suggesting this in 2025 is wild

No it isn’t, otherwise Closure Compiler would (still) be running MS365

“There’s nuance” yeah as much in my comment as the headline at the top of the article

Dagger is already a very popular thing -- a DI framework

It's also a type of blade, been around for hundreds of years!

/s I've never heard of Dagger the DI framework but I have heard of this Dagger. Names will overlap sometimes and it's not a big deal.

People likewise won't confuse a DI framework for Android with a GitHub Actions replacement. Complaints about overlapping names would make sense if both Daggers were DI frameworks or Github Actions replacements, but they're not.

> can’t live up to owning it.

?

People absolutely might confuse a DI framework for Android with this, seeing as lots of teams use both? They are both software products, to start?

> > can’t live up to owning it.

> ?

Dagger, the DI framework, is very popular, supported by Google, and the primary way to do DI on Android (for many). It is not going anywhere. It is unlikely that this tool or product will create a bigger audience. Therefore, it might never "live up to the name," compared to the benchmark set by current Dagger. It's a simple concept.

Yeah I initially thought of this coming from android

> I usually try to strip the pointless comments

You could add your own instead, explaining how things work?

> It's possible to ask AI to write code and then read the code yourself

Sure, but then it would not be vibecoding.

>> It's possible to ask AI to write code and then read the code yourself

> Sure, but then it would not be vibecoding.

Wait, what?

Vibe-coding as originally defined (by Karpathy?) implied not reading the code at all, just trying it and pasting back any error codes; repeat ad infinitum until it works or you give up.

Now the term has evolved into "using AI in coding" (usually with a hint of non rigor/casualness), but that's not what it originally meant.

AI assisted coding/engineering becomes "vibe coding" when you decide to abdicate any understanding of what you are building, instead focusing only on the outcome

This feels like a silly semantics argument, but how is the outcome not what you are building?

If the author doesn't understand their own code, I probably won't

Vibe coding doesnt mean the author doesnt understand their code. Its likely that they don't want carpal tunnel from typing out trivial code and hence offload that labor to a machine.

JNI for io_uring is not trivial code.

"Vibe-coding" means the author deliberately does not understand their code. "AI-assisted engineering" is what you are thinking of.

Well, it is the original poster that used vibe-coding as "AI-assisted engineering".