To play devil's advocate, that sounds like the sort of uncomplicated thing that you could've manually vibecoded in 2020 without an LLM. What changed is that the LLM doesn't let you get analysis paralysis.

▲

yuye 2 hours ago | parent [-]

>manually vibecoded

What the fuck does this even mean?

▲

cowlevel an hour ago | parent | next [-]

You just write the code, don't stop to think. You only have to implement the very small set of requests that an apt client can make to an apt server. Probably "get package index" and "get package file".

Like za_creature said you can use a language more towards the YOLO end of the spectrum - more Go or Python or JavaScript than assembly or Rust.

Your commit history shows you had an issue of high background CPU use. You probably wouldn't have it in a manually coded implementation.

	▲	sublinear 10 minutes ago \| parent [-]
		> you can use a language more towards the YOLO end of the spectrum - more Go or Python or JavaScript than assembly or Rust You might want to change the way you phrase this idea. I think you meant that Go/Python/JS are more "YOLO-friendly languages" (you'll get into far less trouble if you write slop in them). My initial reading was the opposite. It sounded like you were saying the languages themselves are the slapped together garbage. Assembly is most certainly not "YOLO-friendly", but is more YOLO.

▲

za_creature an hour ago | parent | prev [-]

It means that you use an interpreted language without checked types and have a `test` command that prints out "lol"

	▲	yuye an hour ago \| parent [-]
		Seems like I did a lot of manual vibecoding back in college