The perfect /prog/lang

I'm trying to determine the common traits of /prog/-approved languages:
lets start
1.GC is shit.
Does everyone agree? Are incremental GC's or automatic refcounting also shit?

>>11

Splitting code into small modules is an anti-pattern due compiler deficiency(in parsing these nested abstractions) which forces the programmer to follow a map of dependencies for every module instead of working with larger files

I can't even guess what kind of drugs you take, but it must be something really hard. What compiler deficiency? Who forces the programmer to "follow a map of dependencies"? Any IDE will let the programmer instantly view information about any function defined in another file, as well as jump to its definition. But there is no reason to run a parser on the whole codebase when only a minor percentage of modules underwent changes.