Sam Heald Responds to 83+ Problems
Posted by Nick on 19 October 1999, 23:02 GMT
I got this email in my box today and I figured I would share it with everyone. It's from Sam Heald, creator of more assembly programs than you can shake a TI-89 at (I know, lamest comparison ever). I won't say anything to this because it pretty much speaks for itself. Enjoy.
As the instigator of the 83+ "boycott", I wish that you would please post my response as you have posted Ahmed's. I'm typing it now, so if there are any gross gramatical errors, please fix them. [I changed a few spelling/grammatical errors, but otherwise the original intent of the article was not changed in any way. -ed.] The "Boycott" is over Okay, as you all have now heard, I was planning to boycott the 83+ community. TCPA got themselves involved (rather complicatedly), and now the whole thing seems rather pointless. Ahmed, fed up with the TI scene as a whole, is taking a vacation, so to speak. Therefore, I'm dissolving the 83+ boycott before it starts. It has become obvious that the whole process will be more effort than the 83+ community is worth (in my opinion). I apologize to all those infuriated and all those sympathetic with my cause whom I have disappointed. I never did give a public account of my reasonings. Here is a small summary: Why [were we] upset with [the] 83+ community? The flames had gotten out of control after the Ztetris mishap. Admittedly, Ahmed made a huge mistake, but that is no excuse. I hadn't been mailbombed since my AOL days over 4 years ago! The magnitude of hatemail increased sharply. Then, as if the Ztetris release was some indication that I had entered the 83+ realm, I start receiving many many port requests. Usually, they are complimentary. People like your game and want to play it, yes? Not these, these requests were more like demands as if my free time is their god-given right. Sorry - no. The newbie 83+ questions were also getting ridiculous. "What's ION? Where's ION? How do I use ION? How do I send XXXX to my calculator? I sent the .83p version and it doesn't work." These weren't as courteous, either. "I downloaded your program. You're a *censored* liar, because it doesn't work." Frequently in the past, I received newbie email, requests, and criticisms, and never before has it bothered me. But the sheer magnitude and attitude of the 83+ community caused me to make an exception to my tolerance. Why boycott? My "boycott" was just a silly means to an end. I want merely to raise awareness in the TI community about the problem of programmer respect. I understand that the TI community is made mostly of "immature teenagers", so I don't expect much. But keeping that in mind, I realized that if I simply wrote a TI-Files editorial or a ticalc.org news article, nothing good would happen. The same morons who send me hatemail would reply to the articles and laugh (see the ticalc.org article about Mario 83). [You can find that here. -ed.] By holding a temporary boycott (probably lasting 4-8 weeks from D-Day), the issue would be forced to the forefront. Many people appreciate my work, but they act not quite as vocally as the disrespectful ones, so they do not stand out. Those that do appreciate surely prefer my time and efforts to be placed elsewhere (Zelda), not wasting literally hours responding to the vocal garbage of idiots. Many people would dislike the policy, but with anger and tension comes the need for resolution. That's essentially the purpose of any boycott. Agitate the violators until the point of collapse. My intentions were not that sinister. If I was not going to end the boycott, why would I bother making the 83+ port work? I could have simply altered the header and recompile it. Ahmed liked the idea (he, too, suffered 83+ indecency, perhaps more than I), and he signed on. Why I did choose this method? - People can't request ports if they've already been made.
- 1/2 of 83+ owners send the wrong file anyway.
- If the 83+ versions don't work, don't release them. Don't call it a boycott, call it "extended beta-testing."
- The presence of exclusion is more emphatic and effective than mere absence. Out of sight, out of mind; so to speak.
I had some other reasons for this method (instead of a boycott), The fourth reason was the primary one. 1 through 3 were meant to agitate the 83+ [users]. With agitation comes awareness, then comes resolution. My plan was simple: - Release 15-30 Void Productions to 83 ION on one day. The sheer magnitude will bring the topic to the surface. Never before had Ahmed or I ever used our "mini-monopoly" on 82/83 games for our own cause.
- Exclude the source codes and .8xp versions (and tell why).
- Include a screenshot of the 83+ version to prove that it works.
- Post an article regarding respect in the TI community on a major TI site.
- Wait. How long depended on the TI scene's reaction to the article. I would have been forced to wait at least a month just to show the severity of the problem and my own dedication to the cause (if I folded early, nothing would be resolved).
- Once the time has come (depends on reaction to article/boycott), I release 20-30 ION games with the 83+ version and source code. I'm happy because my issue has been somewhat addressed, and the 83+ community is happy because they just tripled their game selection in one day. Ideally, everybody would win.
So, that's that. I hope the limited exposure that my "plan" received will have some effect on the respect given to authors. It seemed most "gamers" were extremely agitated with me, and most "programmers" were very sympathetic to the cause. So I guess for a "boycott" that wasn't, it was fairly successful. Whether I'm going to release any ION versions of Void games to the public is, as of yet, undecided. I haven't made any of the conversions, yet, so it depends on whether or not I feel the effort to be worth the time. I would rather (as I'm sure most would agree) work on Zelda TI-8X. I might be releasing a new demo of that soon. Sam Heald
|
|
|
The comments below are written by ticalc.org visitors. Their views are not necessarily those of ticalc.org, and ticalc.org takes no responsibility for their content.
|
|
Re: Sam Heald Responds to 83+ Problems
|
James abba shalaka Rubingh
(Web Page)
|
I own a ti-83+ and i think they utterly suck. The average 83+ user is an idiot. And ANYONE who demands a port, should get off their ass and code it themself.
|
|
20 October 1999, 02:25 GMT
|
|
Re: Sam Heald Responds to 83+ Problems
|
KnightHero
|
I just wan't to say this fact: assembly programming (for the shells if you don't know) games are tough to do even for very good programmers. In the time it takes for someone to read a long flame they could already be making a game. Just had to say that.
-KnightHero
|
|
20 October 1999, 03:32 GMT
|
|
Re: Sam Heald Responds to 83+ Problems
|
Seth Patin
|
This whole mess is a great shame. These are calculators! They are not life or death. The programers such as Sam and Ahmed (thanks for all the AWSOME programs guys) are taking time out of their busy schedule to do something that they aren't even being payed for. To say or even hint that they are obligated to write programs is stupid. These guys do it because they like to do it, no other reason. Give them a break and show some respect where it is due!!!!
|
|
20 October 1999, 06:06 GMT
|
|
Games schmames
|
PolarSmurf
|
why did you (people who have calculators, I having an 89) spend the 100$'s+ for a calculator? for freggin games? Use it for MATH, what it was made for, stop your bitching about games and do math with it, if you want games, go buy a gameboy for 50 or so, stop pestering the programmers about mindless things. Its funny how people go bezerk when they can't get games for their calculator that they probably told their parents that they needed it for some algebra 1 class or some crap like that. Use it for math, dont worry so dang much about games
Smurf
|
|
20 October 1999, 07:14 GMT
|
|
Re: Sam Heald Responds to 83+ Problems
|
RedPicasso
(Web Page)
|
I just wanted to say that ever since ION came out, I have been getting hundreds of mails from every newbie on the planet with a TI-83+, just because Joe Wingbermuhle thanked me for something in his text file... Okay, I really didn't get this at first, but eventually I got around to re-reading the ION.txt file... it seems that these brain dead newbies took the comment about information the wrong way and somehow found my E-mail address (despite their IQ). I'm not saying that people should not be thanked for their help, Just letting off some steam...
|
|
20 October 1999, 12:06 GMT
|
|
My Response #2
|
Sam Heald
(Web Page)
|
I could write pages on my feelings about the issue, and so somethings in my "short summary" to Nick were obviously a little vague. Obviously, I cannot respond directly to every single comment. Most of these things have already been said by others, but I should probably repeat them. I apologize for any quotations that may use vulgarity, but they are required both for emphasis and truth to how they were told. I hope this is a little less confusing then the last.
1)To 83+ users and others: The motive for my boycott attempt was NOT merely because I received a good deal hatemail. The point is NOT "83+ users are a bunch of immature assholes." Beleive it or not, author disrespect plagues every TI calculator today. If I had to rate them from least to most disrespecting, I would say 85,82,83,86,83+ (popularity is evident). It has been said that disrespect "comes with the territory." I just do not think it does or should. At this point in time, the 83+ community (in general) exemplifies and magnifies this flaw. By displaying that such actions do not have to be tolerated, I wished to set a precedent of respect. Ironically, I am considered "one of the most respected individuals of the TI community." If such occurences can happen to me, it certainly can happen to anyone. I reiterate that the answer to the problem is not to start a flame war with 83+ users.
2)About the Ztetris release: First, I did not make or test the port, because at that time there wasn't an 83+ emulator. I had utmost faith that Ahmed made the ports to the best of his ability. Saying that the flames were our own fault is rediculous. If I release anything for the 83+, it will be because of an emulator, and an emulator can only let you test so far. It simply doesn't offer the same level of depth as rigorous on-calc testing. Do some games not work with others? If you start game X, start game Y, exit the shell, enter a math equation, restart the shell, power-down, then try and send a game to the calculator, will it crash? I certainly don't know. I can only test the game under ideal circumstances.
3)Why I ended the boycott: Some people wish that it be started. I thought the "no games for flames" slogan was rather funny, though. This might be a more detailed explanation: TCPA wanted to make ports. I said no. They posted a premature news article. Ticalc.org followed TCPA's lead. Essentially, the boycott was taken out of my hands. Since the information that TCPA posted was rather scant, the situation confused rather than inspired. Instead of being on the offensive, I was forced to defend what I intended to do. The element of surprise was gone, and the "huge release plan" had been reduced to a single insignficant Solitaire game. Now, the plan can be viewed in hindsight at the least as being very original, with some agreeing and some disagreeing. I think that had everything gone to plan, things would have turned out better. Clearly, an action would have been more emphatic than a mere threat.
3)To those who wish to continue the boycott on their own: Don't do it. Ahmed and I have a unique position with the 82/83 with the magnitude of our releases, where a protest would be seen as a tremendous blow. If one person only denies one game, it seems rather insigficant.
4)Attitude is more important than content. I don't mind newbie mail or port requests, but when they become flaming demands rather than courteous calls, things are out of hand. I suggest that if you are going to request a port, say why you want the port. The reason is not that you want more games, but that you want a quality game like program X. Say something like "I saw the animated screen shot of X on ticalc.org, the game and gameplay look awesome. I would love to see it on my 83+. Is there any chance of a port being made?". It sounds like borderline "ass-kissing", but I assure you that kindness initiates kindness. Similarly, effort initiates effort. Your 2-minute request might mean hours of work for a programmer. Make the programmer believe that you truly want THAT game, not just any game. If you write a newbie message say something like this: "Hello, I downloaded your game and read the text file, but I still am having trouble getting X to work properly. Do you have any suggestions." Then list what you did and what is wrong. Effort initiates effort. Prove that you have tried the game and you have read the documentation. If you wish to critisize, make it constructive.
5)Zelda - Slip of the tongue. It is in no way related to this topic. I merely inserted that interjection because I know 95% of people would prefer me to work on that rather than waste my time with an 83+.
I'm going to post ION versions of Galaxian, Pac-Man, Picross, and FrAWgGuts later tonight. They should work perfectly. As for Zelda, look for more news regarding it soon. There will always be fairly frequent messages about it on void.calc.org In case you haven't heard, Harper Maddox rejoined the project. We are reprogramming it almost entirely from scratch with new great-looking 12x12 sprites and collision detection (the largest complaints of the original demo).
|
|
20 October 1999, 17:46 GMT
|
|
This is comepletely me letting of steam and griping about all this BS
|
Magicain_Synchro
(Web Page)
|
Hello, first and foremost I would like to thank Ahmed and Sam for giving the 83+ community a second chance. Second, I would like to appologize to sam, appareantly according to his post, I am among the SCUM of the earth being both a 83+ and 86 owner/user. Granted in the past I have asked for ports of decent games, among those were the games of FFX4 to Ion, and also Joltima to the 86. (Thanks Bill for Joltima!!) Being a low level programmer (meaning I only know basic and ASM confuses the Hell out of me, *at this time*) I know that some times you do get hate mail, flame mail, mail bombs, viri, ect. ect... and all i did was create a basic program that had one little thing wrong in the documentation. Not the game itself, but the walkthorugh. Finally I had to pull the plug on the game, dropped my web site, wrote a NASTY little message there and the whole world went without my game.
I thought, that will teach them. hehehe.. but it produced more flames, and more hate mail, and more viri, ect. ect.
And it was all for a BASIC game. (Yes I am the Raving Lunatic that always says that Basic can do all that ASM can do except contrast and turn off the calc.) Not only that, but it had on calc source!! Sheesh, but many people are not stupid, just ignorant. Some people buy $15,000 computers only to wind up playing solitare (read the txt file for Solytare on 82/83/86) so why not have calc users spend $50+ just to be able to play a text version of battleship. The main reason is because of advancement. We (the basic programmer community) are givin way more crap than the likes of Sam and Ahmed, the main reason is that either we can't or just haven't learned ASM and so our games are compared to those in ASM for graphics, speed, gameplay ect... look at the POTM awards even, gosh, isn't that neat that ASM has there own catagory for all calcs, but Basic is just tossed in there. Now, with the disrespect that I get for being a Basic programmer, should I quit? Should I just stop on the production of an 86 game just because all 89 and 92 users have SF2? Maybe I should, after all no one wants to play a basic game, and no one really wants to try to _teach_ ASM. I have over 20 FAQ's on ASM, and all they do is say, here is the program, this is what it does. I don't really learn from that, if someone would teach ASM like they did TI-Basic to me, it would be easier... the same way I learned C++
Print = Disp = write.line{ }
instead of the way the FAQ's are already written, you need to know most of ASM to even start. Some people say learn by source code, well you can't really learn by source code alone. Some people say, well I commented it. Yeah but like this
.db list.var \this has to be there to work.
okay. so that has to be there work. any other places that it may A) mess it all up
B) be neccessary to work? like in Qbasic, you have to have
DIM A$() = 9
to be able to have a 9 character array.
what if the source just said
DIM A$()=9 :"This has to be there to work"
so, if you later saw
input A$(3)
and wanted to add another var, but were just learning
input B$(3)
you would be awfully pissed, I know I was. In my source code (included TXT files) I had it commented like so
DIM A$()=9 :"This MUST be there to have an array variable, so if you use DIM B$()=9"
"you can put a later statement for B$() same for C$(), D$(), ect."
Now, back on my ranting and raving, if someone were to help TEACH me to learn ASM, i could help port the games, I have an 83+ which I have crashed before, and will crash again to beta test stuff. Granted that releasing a port w/out calc tests wasn't a good thing to do, but we shouldn't fault Ahmed for it, after all in his busy life right now he has college and all sorts of SH|T to think about. I'm in college right now (at the age of 17 baaabieee!!!) and i can assure you that unless you get a free ride, you ain't gonna get a new Playstation, 64, or a calc. so buck up everyone.
Oh, and I will not check this message board again, that's why I put my email adress up top. so send all flames and mail bombs. to
Bill_Gates@microsoftsuppport.com
but any CONSTRUCTIVE CRITICISM, can be sent to
ramz @ .com
|
|
20 October 1999, 19:25 GMT
|
|
|
|
|
Re: This is comepletely me letting of steam and griping about all this BS
|
Patrick Davidson
(Web Page)
|
It should be obvious why BASIC programmers like you receive a lot of flame mail. It's your claims about the quality of BASIC that cause you to be flamed.
For example, in this very message you say "I am the Raving Lunatic that always says that Basic can do all that ASM can do except contrast and turn off the calc." That's exactly why you are flamed. People read all the BASIC programmer's nonsence like that, and then see that the BASIC programs don't perform as well as assembly does. It's very interesting that you still mention having requested port of assembly programs .. one has wonder why you didn't just write it in BASIC yourself. if BASIC is really jsut as good?
You complaint that "our games are compared to those in ASM for graphics, speed, gameplay ect" seems to suggest that you don't think BASIC games should be held to the same standard as assembly ones. That is reasonable, but it goes against your other claims that BASIC really is equal to ASM.
Yes, I know you didn't technically say they were equal, but saying that "Basic can do all that ASM can do except contrast and turn off the calc" is a very misleading statement. If instead you had said that "Basic can do all that ASM can do except contrast and turn off the calc, but hundreds of times slower" then people would consider you honest and thus be less likely to flame you.
Also, your whining about us refusing to teach you assembler may infuriate the knowledgeable people, for obvious reasons. If you think that I (or any other person who knows assembler) needs to teach you everything, think about this: When I first started learning assembly, I obviously didn't already know it! Since I couldn't spoon-feed the skills to myself (since I didn't have them at the time) and still learned it anyway, *you* should be able to do the same.
If you think the many thorough assembly programming help files available are worthless, that's just because you don't seem to realize what assembly is like. A lot of BASIC programmers seem to think that learning assembly is like learning the alphabet; that there's a simple piece of information that, once you are familiar with it, you are immediately a skilled assembly programmer. That's not true. I don't know what files you're referring to, but even the tutorial I produced (which I don't consider the best of them) is far better than what you're descrbining. It begins with an explanation of how assembly works, explaining how the memory is organized and what the register are for and how assembly program control works. While I do have a sample program after that, it doesn't merely tell you what the program does, but it has several lines of comment for *each line* of code. That's a thorough explanation of what each one does and how it relates to the program.
However, those two things (basic explanations and sample programs) are only two of the three things you'll need to learn assembly. The third component is yourself! For example, even if you both have a large vocabulary and good understand of the grammar of language, that alone is not enough to be a great writer. Even reading other people's literature won't be all you need. The reason is that you must figure out how to *combine* the building blocks to express you're ideas. This is the same for assembly programming, and you can only learn it by thinking about the subject yourself.
Absolutely no tutorials are needed to learn assembly. The only files you really need to learn to program assembly are the instruction set chart (like Z80ISS.TXT for the Z80), and the files explaining the memory layout (TI-RAM.TXT on the 85), the function calls (ZSFNLIB.TXT for ZShell) and the hardware ports (TI-PORTS.TXT on the 85). Anything else is a luxury that is not necessary. One can learn to program the TI-85 simply from those four files (or equivalent for the other calculators, all available on ticalc.org). The fact that you whine about not having more shows that you simply don't try hard enough.
The earliest TI programmers learned without any tutorials, so you should be able to do so also, if you take it seriously. However, if you do want some help, there are many people who will gladly pass on their knowledge if you only ask for help respectfully.
If you would like to get more help and less flames, you could try to do the following things (I will gladly provide ASM help to anyone who does):
1) Stop stating (or implying) that BASIC programs matches assembly in performance.
2) If you want someone to help you learn assembler, it might help if you make it look like you're making at least a small effort to do some learning on your own.
3) Don't think that anyone should spoon-feed you with detailed information on everything.
4) Try to do make some effort to *think* about things yourself, instead of asking for help on anything that isn't immediately obvious within 1/2 second.
5) Try reading the tutorials more carefully, and maybe even *think* a little bit about the sample programs instead of expecting a detailed explanation of everything. If you have specific questions, people will answer, but simply "I don't understand ASM" is way too broad.
6) If you're in college, you could try taking a class in assembly programming! After all, the college actually has an obligation to teach you. There probably isn't a Z80 class, but the problems of BASIC progammers who want to learn assembly is usually not a processor-specific problem, but failure to understand the concepts of how assembly programs are put together.
7) Don't expect assembly to be as easy as BASIC. I won't say that assembly is hard, but expecting us to make it as easy as BASIC for you is asking too much.
8) Remember that the people who learned assembly before you had less help available than you did. For example, I didn't read any tutorials or ask anyone for help yet I managed to learn assembly from the documentation I listed above. If they can learn assembly without spoon-feeding, why can't you?
9) Above all, keep in mind that assembly programming is a skill, not a set of facts. You have to work on it yourself to actually gain the ability.
|
|
21 October 1999, 03:35 GMT
|
|
|
|
|
Re: This is comepletely me letting of steam and griping about all this BS
|
Fishexe
(Web Page)
|
Okay, there is no way so simple as "Print = Disp = write.line { }" to explain assembly. When you write assembly, each instruction you write is the next step the processor executes. In all the other languages, C, BASIC, Pascal, FORTRAN, et cetera, there might be tens or hundreds of instructions your processor carries out for each line you write, but in ASM you are writing directions directly to the processor. So the simple explanations you are in search of, well, quite simply, do not exist. To program ASM you need to understand the native instruction set of the processor you are writing for (z80 in this case), and you need to have the memory map and a list of rom routines for the machine you are writing for. In other words, you need to know the machine in and out. It's the next closest thing to machine language. It's just a whole new world from BASIC. I think that the resources out there are adequate (they must be, judging from the number of other assembly programmers) but they just don't fit with your paradigms of a language and how it should work.
|
|
21 October 1999, 07:02 GMT
|
|
1 2 3 4 5 6
You can change the number of comments per page in Account Preferences.
|