Making d actually usable by ai

[Kapendev]

On Thursday, 6 August 2026 at 02:13:56 UTC, monkyyy wrote:
> When writing full ai code ive been going with odin, it just 
> keeps being the right choice, the reason is extremely simple 
> odin is correct on lib management d is not.

Well, I would call it a nice experience for noobs.
I personally am not a fan of locking a dependency to a language 
version.
That's why I also like things to stay outside of standard 
libraries in general.
Just git clone and done.


> They ship raylib, if I were to ask ai to make a raylib project, 
> take a wild geuss how its gonna do that; its going to grab dub 
> and get into an npm mindset which is bad enough for a human, an 
> unsupervised ai? No, it will do oo it will grab endless 
> depencies, nononono; it will make a horrible mess. It will pick 
> up the bad habits of an npm mindset, it will destory the file 
> structure, and the good compiles times of the compiler wasted.

You can start your prompt with: "Mister AI, please avoid DUB and 
git clone my deps."
AIs are dumb, you need to help them a little.
Be nice to them.
Buy them some milk.

> Instead of the good dependable raylib binding, our std has 
> *checks notes* std.json

I like raylib too, but I would prefer something like adr's simple 
display in the standard library.
Avoiding C bindings in the std is a good thing.
For example, the safe thing to do in Odin if you want your 
project to be version-agnostic is to **vendor the vendor 
libraries**.
So we are basically git cloning again, but worse because I can't 
use a tag or other git features.

That's my input on this.
Arigato.