>All this work to promote someone else's laziness?? I don't think it's laziness. It's called sharing code. There are several really good operating systems based on this thoery.
> -----Original Message----- > From: Tom Whiting [mailto:[EMAIL PROTECTED] > Sent: Friday, December 21, 2001 3:35 PM > To: [email protected] > Subject: Re: [(evil aura) general flame] Re: Style and possible (fun) > isset > > > > The response they get: "Smarten up! You're being dumb!" And > as true as > this > > is, in most cases, it's uncalled for. ;) > > Sure it is -- A stupid question, deserves a stupid answer.. I remember > starting out with mud programming, the first I used was circlemud.. > Somewhere buried in that FAQ (that few if any read) is something that > should be pretty much included in all documentation I believe.. > -------------------------------------------------------------- > -------------- > ------- > First, a Mud is not a learning project. It has thousands of lines to > it many of which are obscure and unclear to even moderately skilled > programmers. > Second, if you are persistent, get a good C reference book and > read the code, (how many do THAT before implementing a snippet???), > try to comprehend what everything is doing (to some small extent). > > Mud Experience doesn't help a huge amount. Code experience does. > (regarding newbie coders starting up a mud and all). > -------------------------------------------------------------- > -------------- > ------- > > > Seriously, most of the questions > > anymore have to do with "How do I implement this snippet?" > That's because running a mud has become child's play > (literally) any more. > All one has to do is download the code for it, find this > snippet or that > snippet, or the like, throw it in the mud and whine when it > doesn't compile > right out of the box.. Few understand WHY it doesn't compile > out of the box, > or even HOW to get it to compile, fewer still actually try to > solve their > own problems before sending it to the list, they just simply > fire up their > favorite email client and write an email to the list (or the > author) and try > to get them to do their work for them. > It goes back to actually UNDERSTANDING what you're doing, rather than > throwing a snippet in a mud and getting it to work. > > > Hmph. Nobody wants to write their own snippet! > > > Heh, well, that's the truth if I ever heard it. Of course, > I've written > quite a few, stuff that takes a bit to get implemented in any mud, but > WRITING a snippet, well, its impossible. When I write a > function for DR, I > don't sit and think about whether or not I'm going to > snippetize this or > that function.. Hell, that's the LAST thing on my mind. Then > again, when I > do, I usually tend to forget this and that and the other thing where > differences are concerned (merc threw everything into merc.h, > I've actually > gone through and split that up with a LOT of help from the > list, etc), so it > IS a lot of work to release a snippet (at least for me). All > this work to > promote someone else's laziness?? Hrrrm... > > > TJW, head tech, Dreamless Realms mud. > mud: telnet://drealms.kyndig.com:9275 > web: http://drealms.kyndig.com > code snippets: http://drealms.kyndig.com/snippets > > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom >
