Dlangs inconsistent decision making and ai

[monkyyy]

D's political failures waste an extreme amount of effort and has 
been an on going complaint for at least 2 decades, some possible 
contributors may not have been born before the first rage quit 
from dlang. I cant fathom how yall thought the half completed 
wasm runtime should've been allowed to rot.

This is incredibly stupid and Ive never seen the core team 
acknowledge the problem or empathize with the outsiders.

Wearing my politics on my sleeve, I believe the blunt force 
solution to communication problems is clear ownership; when 
Britain was a 2 month round trip by boat from america requiring 
paperwork to physically travel by boat to get signed off was 
retarded; the red coats may have been able to keep their empire 
if they invested in fax machines in time. When decision making 
breaks down, you move the decision making to be more local.

If upstream is adopting ai, may as well use it. While my 
historical suggestion to spread ownership around by shipping 2nd 
party libs appearly was so beyond the pale to be considered for a 
even moment. It seems to me you can get ownership-like effects 
with ai.

Instead of a fucking half-baked "lets say no by default" "you 
MUST describe your problem to half deaf ears, with possibly weeks 
of delay of communication" polices; construct personality 
profiles on representatives to review pr's and assign ownership 
by file with %'s.

Consider std.json, theres a file json.d, everyone hates it I 
wouldnt even want "ownership", the natural place to assign 
ownership is on ceo's of any of the corps that have made the 
unfortunate misinvestment to depend on it. So a major share of 
this json.d like 30% goes to grumpy ceo, the grumpy ceo 
"personality" file is loaded into the pr reviewing ai. Presumably 
the personality file will contain lines like "has project foo" 
"cares mostly about preventing breaking changes" maybe the ai can 
rub 2 brain cells together and download that project "foo" and 
check for breaking changes with the actual compiler *within 
minutes*.

So, construct the social graph, assign ownership of files to most 
important parties, set up a pr reviewing bot that at least 
attempts to find the relevant opinions quickly. It only has to be 
better then walter not reading your pr and asking for "whats the 
usecase" even when its stated 3 times in the thread.