This was my first thought; I've been working as a dev for almost 20 years, and "ghosting" is the norm.
Having seen it from the other side, one oddity I've noticed is that being "ghosted" usually means you were being considered; if they get back to you with a "no" it means they don't think the person would work out, and even if nobody else comes forward, they don't intend to hire that person. "Ghosting" is typically what happens when they are thinking "well, maybe", and they keep looking for an even better fit and then find one. Either it's been long enough that they've forgotten, or it's been long enough that they assume (usually correctly) that the person has figured it out by then.
I'm not saying it _should_ be that way, I'm just saying it's not "new". Letting this mess with your head is a bad situation, because it won't be that unusual. Just keep in mind that it typically means "near miss", and keep looking.
Having seen it from the other side, one oddity I've noticed is that being "ghosted" usually means you were being considered; if they get back to you with a "no" it means they don't think the person would work out, and even if nobody else comes forward, they don't intend to hire that person. "Ghosting" is typically what happens when they are thinking "well, maybe", and they keep looking for an even better fit and then find one. Either it's been long enough that they've forgotten, or it's been long enough that they assume (usually correctly) that the person has figured it out by then.
I'm not saying it _should_ be that way, I'm just saying it's not "new". Letting this mess with your head is a bad situation, because it won't be that unusual. Just keep in mind that it typically means "near miss", and keep looking.