A lot of times the "no nothings" are actually important for software pipelining. They enable the hardware scheduler to "figure out" that things are independent and to overlap their execution. Too tightly coupled and the INCREDIBLY limited on-die smarts can't separate things.