Up until now I stayed away from replying to this topic since I would only be adding more fuel to the fire, but since @Deu asked for me to make a statement, I will.
So let's start with what kickstarted this topic, Silence's radio script.
Several days ago Silence came to me with his suggestion for a new radio script that would replace the current one. Which would allow for you to also listen to the regular GTA SA radio stations. So the procedure started as it normally would where I start reviewing code, and once that is done the rest of the HQ team would review the concept itself.
Over the course of a week I had given him feedback several times. Some points were relatively minor, some were more major 'issues' with the script. But these were all issues that needed to be resolved before the code would be accepted for the live server.
This happened several time, where I gave feedback, explained what some of that feedback meant, and then awaited a new reply. Now by the time I brought up the boolean inversion Silence speaks of during his first post, some of the original pieces of feedback still were not resolved. (this is several days after the first 'round' of feedback) So at that point to have Silence say "I just did x to piss you off", that did indeed piss me off. And meant I wasn't going to spend any time reviewing that same piece of code.
After that I told Silence if he did want to continue to come back later with a new script of higher quality.
To me, that wasn't anything special, the code for his current script wasn't sufficient to be allowed on the server so I informed he it would be better to spend his time on a different feature. Up until I saw this topic I had no idea on how much offense Silence had apparently taken.
Why did I share this here anyway? I don't know, guess to just tell my side of the story.
Some of you might wonder why? Why are there these code standards for SAES?
It's no secret that SAES' code base is flawed, parts of it even are utter shit. But that's to be expected when there's "legacy code" (Code that is really old, which is the case with SAES). So we've been trying to fix some of these issues, and make sure any new code that's pushed to the server is of more quality than some of the stuff that's already there.
The reason this is important is because when code is properly structured, it makes it significantly easier to work on it as another developer. Which we do have to do since SAES is not a one man project.
Now to touch on some other people's comments on this thread
Firstly, everyone is entitled to their opinion (Which is also why this topic is not locked) and I must respect that, even if I would disagree with your opinion.
@BlaZZey If the script's code quality is improved to the point where it is sufficient, then the chances are that it would be uploaded to the server, but that's up to all of HQ to decide, not me.
Now it's also no secret that TheKiller and I have run into some issues in a similar situation, where I denied some of the code he suggested because it did not meet the standards. However as you can probably see in this topic, TheKiller does take it very personal, attempting to offend me by calling me an autist (Just for everyone's information, I'm not. No idea why TheKiller does think so, but I can imagine it being offensive to people who actually do have autism)
And I don't think the disagreements TheKiller and I have are going to be solved, we simply don't get along together. And to TheKiller that means he can not work with me.
Now it's also brought up by other people that my main priorities are not SAES, but KATLA.
Simply put, this is true. At first the idea for KATLA was that it would be SAES' new version, and be released for the clan. However due to a disagreement between Desolator & myself, and the majority of the current SAES HQ team Desolator and I have decided to take KATLA our own way.
This does not mean however that I do not care about SAES anymore, I still care to review code, to make sure that the code base remains maintainable for future developers. And to every now and then help fix bugs, resolve issues or create new things.
Now to @Lamza, I do not recall the run in you had with me two years ago, but if it is as you describe it that is not how I should have acted, and I'd like to apologize.
And to @Deu , yes. Desolator and I have been working on KATLA for close to two years now, and it's still not done! It's almost as if we don't work on it full time.
Sarcasm aside, Both Desolator and I have other things going on in life (our studies, work, other projects, etc). So yes it's taken a long time, and it will probably take quite some more time.
And no, I'm not "restricting" people from working on 1.4 because I am too busy with something else. I'm simply reviewing their code to make SAES 1.4 easier to work on for our current (and potential) future developers.
And yes, there have been many great suggestions that haven't been implemented, if we (the dev team) had the time to implement every good suggestion that's made, live our life, and work on our own things. Then we would, but we can only spend our time once, so we all spend it on what we would like to do the most. To us scripting for SAES is a hobby, not a job. So you can't expect of us to work tirelessly on it.
So that's it for now, if I've missed your post, feel free to quote me here, or come talk to me on discord.