I can offer a few observations on the "stickiness" issue since I have = come, but not stuck. (I have stuck a bit, because I have some simple = REBOL scripts in production on an RS6000 where I work, but I have not = stuck as much as I would like to.)
When I first came, I was used to languages with reserved words, so I was = looking for that in REBOL as some "firm ground" to stand on while I looked = around. I found the sample scripts VERY hard to understand since there = was no punctuation, everything was in lower case, and all the words were = generic things like "file" and "data" so I couldn't figure out what was = going on. I finally got around that by usiing upper case hyphenated words = for the words I made up, and lower case for all the REBOL words and = functions. That problem now is in the past, but it was quite a big one = for a while. The next issue for me probably is my fault for not paying my "dues," that = is, beating my head against the wall for long enough, but when I read = sample scripts, they are uncommented and I just can't seem to figure out = what they are doing, or why they must use the functions they use to do the = things they are doing. I would like to see some samples that are HEAVILY = annotated, to the point where there are more comments than code. I could = provide some examples, since I have had to do that for myself so that when = I go back to scripts I have written I myself know what I was doing. I probably shouldn't say this since I have not read the VIEW documentation = for a while, but I have read it, a couple times, and I was a bit lost in = all the "faces" and "facets" and "feels" and so on. I will accept this as = my fault; probably I just have to read it again. But a nice, thick, = complete VIEW manual would be nice. Maybe the motto should be something like, "simple things should be simple, = and complicated things should be possible, if only you can figure out how = to do them." I can't quite explain it, but I have observed it an probably = could construct an example. On thing that pops to mind is the slider. Of = course I know how to put a slider on a screen, it's as simple as can be. = But once it's there, I don't know what to do to make it slide, and make = things slide with it, and so on. I think this probably all boils down to documentation. Maybe someone = should go through every word in the dictionary and write up some detailed = explanations and examples. Actually, I would be happy to do it myself, = but of course there is that chicken and egg problem--how can I explain it = without understanding it. Now that the Microsoft antitrust settlement is in place and Microsoft = theoretically can't bully computer makers, would it be possible to get = REBOL pre-installed on all new computers? Just the free version, of = course. I have thought of some script ideas to give to people I know, but = if I do that I have to tell them how to obtain REBOL first. I think it = would be nice to have REBOL pre-installed on all Windows computers and in = all Linux distrubutions. I know it is "easy" to download and install = REBOL, but I have done it a number of times and there still is something = confusing about it (I have commented on that to the REBOL feedback). This final item probably is not relevant because any language has its own = strengths. If there is something one wants to do and it can't be done = easily in REBOL, the answer probably is to find a language where it CAN be = done. One does not fiddle bits in COBOL, for example, although it can ge = done with effort. It seems that REBOL is not designed for "data processing= " kinds of operations, but a lot of what people do with computers is data = processing in some form. The example in my mind is files. In my world, = files are composed of records, like the employee record of a payroll file. = It seems that REBOL is not designed for that. One reads a whole file = into memory, perhaps as a big block, and writes it back all at once. This = idea showed up in the first REBOL book, the Official Guide, I believe, = where one logical file in the video store data base was actually broken up = into several physical files just because there was not a way in REBOL to = read one "record" of a "file." I wonder if that might be a deficiency of = REBOL worth investigating. I have not given up on REBOL. I am trying to think of some application at = work, where we have 400 desktop computers, that is so cool everyone wants = it, and that would require loading REBOL on all our computers. No luck = yet. Steven White City of Bloomington 1800 W Old Shakopee Rd Bloomington MN 55431-3096 USA 952-563-4882 (voice) 952-563-4672 (fax) [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 07/07/05 10:21 AM >>> Prompted by my last comment, I just wanted to add something... I agree that REBOL tutorials are very important to "visitors" who are checking out the language for the first time. The way I view it is: if the userbase is not constantly growing then there is something wrong with the approach or wrong with the product (language). This is sometimes called "stickyness". People come visit the site, check out a few pages, but then... do they stick? Do they download it? Do they give it a fair chance? I think it is very important. But, I also think that we have a long way to go to improve our intro examples and tutorials. That was one of the main reasons I created the cookbook a few years ago. But, actually the cookbook is not enough. I know a lot of people who use REBOL and love it. But, I also know too many people who have tried it and not "stuck". I wish I knew more about why... and also what we could do to improve the stick factor. So, what do you think is the #1 thing we can do to get greater stickyness? I estimate we get more than 15,000 visitors checking out "newbie" pages each month. How can we get more of them learning and using REBOL? -Carl Sassenrath REBOL Technologies --=20 To unsubscribe from the list, just send an email to=20 lists at rebol.com with unsubscribe as the subject. -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
