I use AI toolings to generate snippets of bash scripts because I can't be fucked to remember that syntax. Obviously not for anything with high risks or that I can't easily verify. But things like parsing through mass amounts of files

[–] blackbirdbiryani@lemmy.world 8 points 19 hours ago (1 children)

But... bash snippet extensions already exist. The only difference is maybe it doesn't auto name your variables for you. I'd take that over non-deterministic LLM outputs.

[–] Monstrosity@lemm.ee 3 points 14 hours ago* (last edited 14 hours ago) (1 children)

I have no idea what the hell a bash snippet extension is, but I do know what a local llama.cpp instance running a small model to tell me bash commands on the fly is.

I use it to make .desktop files, too. Isn't that so lazy?

[–] Initiateofthevoid@lemmy.dbzer0.com 3 points 8 hours ago* (last edited 7 hours ago)

They seem to be genuinely trying to provide information about a tool that they find preferable to your solution. And you're not even the OP they were responding to. Nobody in this thread has called you or your solution lazy.

A bash snippet extension is "an extension [for a code editor] that provides a collection of snippets for bash scripting." It's a tool that is purpose-built to tell you bash commands on the fly, but smaller, more efficient, and easier to install than a local LLM.

The user you are replying to appears to prefer this because it will also tell you the same bash command every time you ask (non-deterministic outputs can be different for identical requests)