For one thing, you need to ask for a clear defining of every single task the reference node performs. One thing that seems to be forgotten is that it is responsible for enforcement, which locks out everyone mining from cheating the masternode payment. Also, there was a five hour block that occured about 3 weeks ago that was only resolved by updating the reference node. It's not your fault you don't remmeber, but repeating false-mantra about the "insignificant" role of the reference node doesn't change what it is actually doing. There are atleast 5 settings. Also, drk doesn't have a very good record of dealing with enforcement sans reference node.
*crickets*
*chirp*
*chirp*
*chirp*
It's obvious DashHoles don't care about technology, fair launches, actual emission matching theoretical, decentralization, huge attack surfaces, trusted third parties, or best security practices. These kids aren't old enough to have learned about such grown-up matters.
They are fine with Dash's unproven homespun ad hoc crypto.
All that matters to DashHoles is getting a gold donkey.