Rufasu wrote: ↑24 August 2024, 20:30
It is ludicrous to state to a disgruntled player that he or she has faith in probability or in the BGA.
It is wrong from a mathematical, computer science, and business standpoint.
This is the same mentality that feeds into mentality like, "The customer is always right," which, in the moment that it was first used, was entirely fine. But that mentality, extended to infinity, results in companies being ruined by bad actors, people looking to take advantage of the goodwill of the store.
Similarly, gaming companies that have bent over backward to add every idea that the fans demand results in a worthless sludge of a game that barely resembles the original product. Quite a few games have gone from being rising stars to failed duds because of listening to the customers
too much. Not every person with a suggestion has a complete comprehension of what's going on under the hood. Not every customer is right.
As I have said many times, the BGA should do what every developer does.
Just improve the quality of the game, constantly upgrade the PHP version and use new libraries.
I'm not a BGA programmer. Neither is romain672. Neither is Jellby (As far as I know). They might be programmers. They might even be programmers for game representations here on BGA... but that doesn't make them BGA programmers (at least, in the way that you mean it).
That said... the idea of "continually upgrading" is another path to failure. Real programmers for game engines don't do that. It's far more common for devs to use a method called "leapfrogging." They pick a version of an engine that works for them, and stick with that version for a while. They only make interim upgrades when there's a discovery of a significant flaw or vulnerability, and continue to develop on a stable platform that everyone understands. When there's a significant change to the underlying engine that benefits the game, the developers will upgrade to the newer version (but often, even then, only after that new version has proven itself stable). Some developers don't even do that - they start with a set example of an engine, and stick with it from start to finish. For most games, there are few engine changes that will actually matter enough to upgrade for.
Now obviously, there's a significant difference between a single stand-alone game and a live framework like BGA. BGA is naturally going to have upgrades, updates, and so on. But that doesn't mean that it has to change to the new version of PHP as soon as it comes out. They may not even want to use the new version, if there's no major changes from the one they're currently using. Upgrading takes programming time - time that would be taken away from other purposes.
The current version of PHP is 8.3.3. That was released
yesterday. 8.3.0 was nine months ago. 8.2.0 was 20 months ago, and is still fully supported. 8.1.0 was 33 months ago, and still has security support. Do you believe that BGA should be rocking 8.3.3 right now, even though it only came out yesterday?
For the record, BGA requires that new game modules that third parties create be compatible with 8.2. That gives third-party programmers a level of stability to work with, instead of having to be using the most current version, which might change tomorrow...
If you have time to write long excuses, write programs.
If you have the time to complain for pages and pages
and pages without ever once taking any opportunity to demonstrate what the actual problem is... perhaps you should find a different path. The one you're on is mulishly stubborn and utterly valueless. Just because you are making an accusation, does not automatically make that accusation correct.
Instead of actually backing up your demands with evidence, you keep stomping your foot and shouting that because you're upset, we (and BGA) should just do what you wish. That's not how reality works. Trying to do that will snap your neck when you run into people with opposing demands.