WHAT the hell is going on? #2

[Renegade]

[...]
So unless you can do a better job, DON'T ATTACK HIS WORK SO HARSHLY!

I'm not going to say VK's work is bad, but:
Just because we can't do better doesn't mean VK's work is good.

@Banshee:
I was not talking about understanding in the sense of knowing how more code is always more bugged. We all know that. And be it only hunting down a single godforsaken IE through a thousand lines of .ini code. What I was referring to are practices like the one shown in 4StarGeneral's post quite well - absolute support no matter the problems, decisions or number of people voicing concerns.

For example: After we were all getting pushy (and maybe a little asshole-ly at times), he directly asked "And what is your ideas?". I responded with a simple, reasonable, elaborate 10-point-plan that'd not only improve the experience for us, but help him get things organized and people off his back as well.
His reaction?
In that same thread, none. Despite the fact that he posted three more posts. I directly responded with ideas he requested, and he ignored me. He later replied in a total different thread (when I called him on it) to a few minor, partial sentences, but still ignored the thing as a whole.

Now, don't get me wrong - I'm not trying to play the "omg I don't get enough attention!!!!" whiny teenager here, what I'm pointing at is that despite such obviously inconsistent behavior, despite this obvious unwillingness to change anything (even securing the status quo through bullshit "rules" now), disregarding any criticism or point made by the community, people like 4StarGeneral still blindly follow him crying "four legs good, two leg---" err, "as long as you can't do better, shut up". It is that touchy, feely, fanatic, protective, pseudo-"understanding" behavior I was talking about.

Yes, I know he didn't mean to code the bugs. Yes, I do realize we should be grateful for what he does. And yes, I do realize I can't do better. But all of that doesn't change the fact that his way of working lead to a state were pd himself returned and asked "WHAT the hell is going on?".

I don't have anything against VK, personally. In terms of hosting, general interaction, etc. he was always reasonable, friendly, and intellectually understanding. But his style of work and the state he lead RockPatch to are alienating a great deal of people using RockPatch. And people like 4SG, who still sit there saying "don't listen to them, they can't even code!" aren't making it better.
Even if it turns better for the moment (yes, I saw all his "I fixed that" posts and AG's apology), if his style of work doesn't change, this'll all play out again after the release of RockPatch 1.08 Ultimate Editon #0030.


Sorry if I jumped to "epic mode" there again, but this damn coding argument is pissing me off. Yes, he is the only Assembly coder doing it at the moment, and yes, we are at his grace. But that doesn't automatically mean we have to be happy with everything he does, and it most certainly doesn't automatically make his work "good". You implied it yourself: A little more testing would make things a lot more stable, and lead to less bug reports. I had the same in my 10 points. People like Marsh have said it for ages. But he doesn't care. And, at least in my opinion, his stubbornness has lead to a point where he just doesn't deserve neither the he-is-unique-we-can't-lose-him-loyalty nor the "cut him some slack, Assembly is hard" excuse anymore. We are trying to help, as good as we can. Best example is Marsh's launcher: It'd make using RockPatch so much easier for everyone, inevitably leading to more user adoption - but VK wasn't even willing to discard his stupid (universally hated) string naming scheme to ease integration. VK is asking us why nobody helps writing the docs - yet when somebody touches any RP-related page on ModEnc, he's quick to revert the change. (Favorite quote: "... nobody ask you ..." - not to mention the fact that he discarded the RockPatch Docs on ModEnc in favor of the offline help.)

We are trying to help as much as we can from our non-patching position. If he won't let us, it's not our fault. And as long as he won't let us help reducing the number of bugs and improving the documentation, he'll have to deal with us complaining about the number of bugs and the quality of the documentation.

[/epic]