Erockbrox wrote:
if you dont enter something in EXACTLY it doesnt work.
Computers are stupid. It's much, much harder to make a stupid machine find mistakes and correct them automatically than it is to require smart humans to type commands precisely. If you were on the other side, programming command line software, you'd be complaining about the users who aren't clear about what they want to do and thus can't get the software to work.
Keep in mind that assembly language in general is way more anal than any command line tool you can think of. The NES (or any other console for that matter) is completely unforgiving of any mistakes you make. The NES doesn't know what games are, it's just a machine that draws pictures and makes sounds if you give it the correct orders. This means that in order to make a game you have to simulate everything that constitutes a game yourself (physics, collisions, A.I, animations, etc. - the NES doesn't know about any of that), and tell the NES EXACTLY how it must display the pictures and make the sounds based on your game calculations.
Quote:
ive had to take screen shots of me entering in the correct spacing and correct syntax
You could have used the time you spent taking screenshots making batch files instead. You probably didn't know about batch files back then, but now that you do, please make use of them and make your life simpler.
Quote:
which is better, having to manually type in a complicated file destination of where a rom is located and where the patch is located or just easily search or it and click on it?
The problem with GUIs and clicking is that you can't easily automate the use of such tools. When you're assembling a game for example, there are several assets that need to be prepared to be included in the ROM. Imagine if I was creating a new level, editing graphics, palettes, level layout and object placement all at once... if each of those needed a different GUI to convert the data into binaries I can include in my game, I'd have to do an awful lot of clicking every time I wanted to test any changes. With command line tools I can just script all the conversions one after the other and have the ROM ready in seconds just by double-clicking a single batch file.
So yeah, if it's a task I just want to get done once I'll surely prefer a GUI that allows me to get the job done in a few clicks, but if it's a part of a project that will have to be compile/assembled thousands of times I'd much rather script the whole thing once and forget about this process.