The code isn't perfect, I'll agree to that completely. Start submitting adjustments through official means and maybe you get your clean code. Bitching about it on a forum has little effect other than giving RB opportunities at a dev quote.
Whos bitching? People were discussing ideas for changes.
However, a Dev couldnt handle seeing a discussion on a forum, and went Berzerk.
So I suppose you missed out on the years that H*** ~was~ in heading the project? Things didn't seem so stagnant back then...
(I can't believe I'm sticking up for the tosser)
- Id argue that theres been much more positive progress now that hes not.
Features is a word that just shouldn't be argued at all.If MAME truly is a documentation project, any "Features" you get are pure cream. Enjoy what you get.
- When a feature is part of the games History, then Documenting it Accurately should be part of it. Documenting select pieces and parts, with poor accuracy and inconsistencies, isnt really the way you Document things.
As for bit rot, that really would fall under the Dumping Unions mission at the moment, which is a separate entity entirely. Not that they beckon to the call of the whiny either. If you donate for something specific, all efforts are made to get that item. If you throw in $5 for a $300 PCB and start to get bitchy about things, you'll get your money back. I promise it. In the end these are just games, and attitude takes the fun right out of them.
- You can recite all the canned answers you want, but everyone knows that without the help of non devs, the project would screech to a snails pace.
If you treat ppl like crap, cant budge an inch, then I can assure you, the project will suffer for it. It already has.
If you yourself place little importance on them, because to you, games are not too important... then I think most would be glad you are not heading up the project.
Many people could care less about fossils / dinosaur remains... and putting a person who only mildly has care, and only documents partially.. will yield poor historical accuracy. Luckily, that isnt the case. However, unlike Dinosaurs, we live in the time period where its possible to capture most of the information well before it gets lost forever.
Some may argue that Dinosaurs are much more important to document accurately than video games. Then again, many could care less about the Dinos, even If they provide useful knowledge to mankind... and care much more for a painting, piece of music, a weapon, a movie, or even... a video game.
===
- Well, Ive re-read the thread and fully understand the points on both sides now.
By means of looking at a driver, one cant easily extrapolate accurate information about a game. Especially when code is opposite to the way the game actually functions. That surely goes against the idea of good Documentation.
The only way around this, may be use of some sort of database. Which I believe is: listxml. However, from what I gather... the database is highly flawed, inaccurate, and lacking major levels of details. Ive also heard that its a very poor choice for database files. For one, its not even really legible.
From what Ive seen, Giles makes more code changes than can be fathomed... and yet, all the devs deal with it. Sure, these changes are more critical and important...
However, there are many cases where good accurate game and cabinet information is rare to non-existent. And if its hard to pull up now... Imagine 40 yrs from now. Then 150.
In mames current iteration, you cant even really tell what controllers many games used... because so many hack options are all lumped together in the same menu, rather than being separated. Some games dont even allow use of real controllers, and are hacked programatically in ways that do not represent the real hardware at all.
While flipping the screen is trivial, and is already exists as an option, I can understand why someone may not care about having to deal with a new method, especially since the original method still works. However, if mames real goal is accuracy, then I think its a worthwhile & justifiable cause.
Other people can head up the task of collecting accurate information, so long as theres a way to input it, and implement it.
The Devs stances are pretty contradictory currently. The canned arguments about Documentation seem to go out the window, when it suits their desire to 'not' document, document incorrectly, or poorly.
I realize theres certain reasons for this, but they are not always the best reasons, nor the best ways to do things.
We can appreciate the great work they do for sure. But, that doesnt mean we cant disagree.
|
Index 
Flat 
Re: continued....
Reply
