I agree with you, but no one else is required to feel that way. Tuning numbers is more important to some.
We are all heated and it’s their thread. I did not come here to pick fights of semantics and I ask everyone in the shaman community to do the same.
They strongly indicated their opinion and have set that opinion in stone. Let them air their grievance. None of us are enemies here. Further hostile division in a shrinking community serves no one.
I hope none of your’s is ever heard.
I’m sorry you have decided to be that way, but I wish you the best.
I mean maybe post on your main and maybe think out your posts, suggestions, and thoughts before posting them, especially in a feedback thread made by the devs. Goes a long way to ensure people don’t assume you have no idea what you’re talking about or that your feedback is lacking a lot of elements to be taken seriously.
For sure but there’s a time and place for different types of feedback especially when considering what part of the dev cycle the game is in. And feedback that is well thought out and backed up by data, arguments, and examples is MORE meaningful than ideas that are spitballed. Like I imagine if people were more detailed and thought out why they didn’t like the Pwave gameplay loop throughout DF, the devs could have made some changes to it to fix a lot of difficulties related to its gameplay loop through adjusting abilities and/or related talents, game mechanics, and so on. Instead of “Pwave bad chain harvest good” and that’s it. Both are valid feedback, but one is way more meaningful.
Many people who don’t like Pwave don’t quite understand why they don’t like it or have trouble putting it into words. Their feedback is every bit as valid. Most people suck at communication, you can’t invalidate their opinions because of it. Their feedback is still just as important. It’s Blizzard’s job to try to understand why they don’t like it and hopefully find a solution. It’s a job that sucks and I don’t envy their position.
We’re WoW players ofc we can’t talk properly 
But on to you point. I acknowledge that somebody not liking Pwave is valid even if they can’t articulate why that is. But something being valid and something being meaningful can be two different things. And most certainly feedback can be valid but not grounded in reality. The statements “I don’t like Pwave because of how Flame Shock spread work” and “I don’t like Pwave, I hate it” are both valid but is more useful for determining solutions and changes. To validate is not normalize or accept/agree outright. You would most certainly be able to validate my feeling that Storm build should be completely removed so all focus can be on Elementalist build as I believe it is the way forward provide they fix up stuff but still point out I’m being an elitist jerk thinking about my own bubble of the game I like and not considering others.
My stance is at this point in the dev cycle with the issues that lay before us for our class and specs, meaningful and well thought out feedback should take precedence. And if somebody doesn’t have a clear idea as to why they want a certain change or they don’t like something, they have to be open to the following dialogue about it even if that involves them facing arguments or other ideas that go contrary towards their suggestion/opinions. Many people do not do that. And what you get is the current beta feedback thread: a lot of valid feedback that is devoid of meaning/utility. And then the devs are left to shake their cursed magic 8 ball to figure out why this feedback is given and leads to some of the worst cooks they make.