Been trying to get the attention of people for our proposal and just to show people how important this stuff is to me, I step out of my comfort zone and try to show how it could be important for people that don't even use python or hive-nectar.
The account_json_metadata of 
Seems like something pretty useful? No?
So, I broke out of my comfort zone and wrote a little function in javascript to use dhive to query the data and create a new instance with the updated nodelist. So, now my dhive apps and scripts will use the most up to date nodelist based on benchmark scores. Pretty sweet I think.
// Example usage
updateNodesFromAccount('nectarflower')
.then(updatedClient => {
console.log('Node update complete');
// Use the updated client for further operations
return updatedClient.database.getDynamicGlobalProperties();
})
.then(result => {
console.log('Test query with updated client successful:', result.head_block_number);
})
.catch(error => {
console.error('Error:', error);
});
I don't know about you, but I hate when my scripts and cron jobs and such die because your favorite node is down. I find it frustrating, and the 
The full source of the updateNodesFromAccount{'nectarflower') example can be found it's own github repo here: https://github.com/TheCrazyGM/nectarflower-js
So, even if you don't believe that beem hive-nectar needs to exist, I feel it's pretty important stuff that we are doing for the community as a whole.
Maybe this will help someone, maybe it won't. But it is the kind of stuff I do daily just because I enjoy doing it. Perhaps you will support our vision:
Proposal 339: A modular open-source development framework with critical library maintenance.
As always,
Michael Garcia a.k.a. TheCrazyGM