That seems like a terrible response... Or maybe I just don't understand the logic behind the comment. My take on it:
1) We don't want our users obsessing over which amp or effect uses more or less DSP -- And yet people already do because as we're trying to build patches all of a sudden we can't add the 4th block we wanted and we have to go online to try to figure this sh!t out and work around these limitations.
2) we want them choosing what sounds best to their ears. -- Everyone also wants this. Adding a % value of a DSP would not stop people from choosing what sounds best to their ears, but it would help them build patches that in the end sounds best to their ears.
3) We also want POD Go users to almost never run out of DSP -- Well that's a fail because most people will quickly run out of DSP, then it's a PITA to work around the issue without knowing which effect uses less/more DSP.
4) opening more blocks ... 90% hitting the wall much sooner—is a non-starter -- Not sure what he was responding to, but if you give the DSP % and add a block slot if there is still room for another effect, you don't "hit the wall much sooner"...!
Anyway, just imho a very bad take. It really sounds like someone doesn't want to do something and is looking for excuses, rather than having pertinent and logical reasons.
- They say they don't want users to run out of DSP, but they don't give users the tools not to run out of DSP.
- They say they want users to choose what sounds best to their ears, but they won't allow them to make the patches they want because they're locking out blocks even if DSP is available, for absolutely frivolous reasons.
- They say they don't want users to obsess about DSP, but they make DSP management as obtuse as possible, and force users to go online and research that sh!t to death because the product as is is incomprehensible and they don't give users the info they need to use it properly...!
Very disappointing answer, as you said, features the majority of users would love to have implemented.
Too bad we can't make a poll here, can we on ideascale? % of users who want the features vs don't want the features. And if really some users, for whatever reason, just can't handle seeing a DSP % usage or having an extra block appear if they have room (LOL does such a person even exist?!) then you can make the 2 options disabled by default, and allow users to activate it if they choose in the global settings. And in all honesty, I can't imagine a grandpa/grandma that wouldn't welcome the features. But yeah, that notion is so silly, it's obviously looking for excuses for not doing it.