00:00:00 --- log: started forth/02.01.31 00:29:45 --- join: ree (user@ip68-3-237-161.ph.ph.cox.net) joined #forth 00:57:57 --- quit: ree (Read error: 110 (Connection timed out)) 01:23:20 --- quit: MrReach () 01:32:18 --- join: aum (~aum@l76-145.world-net.co.nz) joined #forth 03:02:24 --- quit: aum (Read error: 110 (Connection timed out)) 08:53:45 --- quit: clog (^C) 08:53:45 --- log: stopped forth/02.01.31 08:55:34 --- log: started forth/02.01.31 08:55:34 --- join: clog (nef@bespin.org) joined #forth 08:55:34 --- topic: 'do drop >in -- Extra Extra - Read all about it - (;code) (;uses) and does> all now work in IsForth - shock horror!' 08:55:34 --- topic: set by I440r on [Tue Jan 29 16:23:38 2002] 08:55:34 --- names: list (clog @ChanServ oxygene) 09:11:38 --- join: futhin (thin@h24-64-174-54.cg.shawcable.net) joined #forth 09:20:00 hey oxygene 09:20:27 hey 09:21:11 yay, chuck moore responded to my email :P 09:22:08 it was a stupid question though. . "what would a publication standard look like" 09:22:27 wow... :) 09:22:32 "publication standard" ? 09:23:16 yeah, he thinks ANS standard sucks, and that forth needs a publication standard, rather than an execution standard (like ANS) 09:23:23 hmm... I think I found the ideal combination of programming languages for a modern computer: forth for Firmware and lowlevel OS, smalltalk for the high level stuff 09:24:29 you could implement smalltalk within forth, and then have both smalltalk and forth equally accessible 09:25:00 yes, something like that 09:25:36 squeak can compile smalltalk into c-code so it can be linked into the vm-executor - if it'd be forth, it could be linked on runtime and is platform independent 09:25:50 i don't know smalltalk yet, but i don't see why forth can't be as high-level as you need it. remember simply coding in forth creates a new language.. 09:27:03 of course, but the smalltalk language is a very clean OO-language, therefore very useful for highlevel stuff like GUI 09:27:03 I think it's pretty easy to implement it in forth (as the language core is even smaller than forth's) 09:32:18 --- quit: futhin ("bye") 12:08:30 --- join: TheBlueWizard (~tbw@ip-216-25-205-128.vienna.va.fcc.net) joined #forth 12:08:30 --- mode: ChanServ set mode: +o TheBlueWizard 12:08:41 --- part: TheBlueWizard left #forth 14:15:31 --- join: futhin (Havoc36@ab-cal-a52-03-42.look.ca) joined #forth 14:22:50 --- part: futhin left #forth 14:22:52 --- join: futhin (Havoc36@ab-cal-a52-03-42.look.ca) joined #forth 14:22:52 --- mode: ChanServ set mode: +o futhin 15:04:40 --- join: TheBlueWizard (~tbw@ip-216-25-205-128.vienna.va.fcc.net) joined #forth 15:04:40 --- mode: ChanServ set mode: +o TheBlueWizard 15:04:40 hiya 15:04:40 hihi 15:04:40 how's it going? :) 15:05:02 hiya futhin ... I notice you power grabbed #forth from I440r :) 15:05:19 doing fine...I am at work; I will be departing soon 15:05:35 I showed Linux to a couple friends at work 15:05:37 :) 15:05:43 (I'm on my laptop) 15:05:44 heh 15:05:53 they've never seen linux before? 15:05:57 wow :P 15:05:59 nope 15:06:12 at my work everything is M$!!!!! 15:06:14 :P 15:06:25 yeah 15:06:35 you are doing networking/security? 15:06:45 yes, plus other things 15:06:57 how familiar are you with forth/ 15:07:38 I used to write Forth stuff for fun on C-64...haven't actually done much since then...but I do find it sexy ;) 15:07:58 heheh, nice to hear ;) 15:08:12 bet you're coding in Forth for eons :) 15:08:32 what's that supposed to mean? heh 15:08:46 by the way, I have come to realize Forth's limitations as well as its power 15:09:06 huh? how familiar are you with Forth? 15:09:20 discovered it 8 months ago 15:09:28 somewhat familiar 15:09:32 haven't really coded much 15:09:36 oh? so you're a relative newbie, eh? 15:09:41 but i understand stuff like does> 15:09:49 yeah i'm pretty newbie 15:09:52 I learned about Forth about 15 years ago 15:09:58 cool 15:10:35 what limitations? 15:10:42 why aren't you coding in forth these days? 15:10:44 when I spotted an item "C-64 Forth" (a cartridge for C-64) in an electronic store 15:10:46 when are you gonna get back into forth? :P 15:11:02 when are you gonna join forth orgy of sexy ppl? :P 15:11:33 long story....time limit, many projects, many chores, etc...I need to do grocery shopping tonite (ran out of milk) 15:11:45 lol re: orgy proposal 15:11:59 i don't really see any limitations. forth can do anything, and it can do many things in a simpler way than i could do in some other language 15:12:51 i'm interested what you think are forth's limitations as well as powers.. 15:12:53 one limitation is that Forth lacks decent organization (e.g. how do you deal with naming while developing a very large app, like, say, a graphic web browser) 15:13:42 another: suppose I need a systematic scan of source code for something...Forth's laissez faire approach to programming proves to be a problem 15:14:05 yeah 15:14:07 I could go on....but you get the idea 15:14:30 other limitations that i percieve: poor support, no real newbie-friendliness for forth.. etc.. 15:14:40 my solution 15:14:52 Forth OS! TA DA DA DUM DA DUMDAAAAAA :P 15:15:46 yeah...also many dialects of Forth prevents it from being really portable....actually, it is really an issue of standardization and agreements on API stuff...just a Forth OS would not solve much 15:16:21 eh? i don't care about the implementations etc. Forth OS would be its own implementation, and it would be portable across architectures 15:16:45 it would be a consistent standardized easy to understand implementation, etc.. 15:17:03 * TheBlueWizard points to his previous arguments as the resason why 15:17:53 eh?? 15:18:03 eg namespace issue (Forth has a weak notion, provided by VOCABULARY), library routines (eg Internet API), .... 15:18:34 it's not like this Forth OS is going to run code besides forth code.. 15:18:55 even then there is still some issues... 15:19:08 those issues can be solved right? :) 15:19:51 if you define them yourself, then great 15:20:37 basically put, you'd have to define a new standard...like standard for doing string manipulations, standard for doing floating point math, .... 15:21:17 well vocabulary would need to be improved or some other word would be defined since we'll have applications and we'll want them to run separately, not to conflict in code, etc 15:21:45 well yeah, it's not like anybody likes ANS Standard 15:21:49 it's not like there's any standard in place 15:22:04 then again there are many Forthers who disagree on what should constitutes the "Forth way" of doing something 15:22:04 sometimes rather violently :) 15:22:11 * TheBlueWizard nods 15:22:20 now you see my points, yes? 15:22:29 good, tell them to bring their guns to the pub! 15:22:36 we'll have a good old fashioned shootout :P 15:22:49 we need to get forth coders riled up 15:23:14 i once got on CLF and told everyone to come to #forth on irc.openprojects.net only 1 person came. bastards! :P 15:23:23 LOL....anarchy rulez! Uh-oh...run! The Bushies are coming to arrest us cuz we're being called terrorists! ;) 15:23:47 lol re: recruitment effort 15:23:58 i'm thinking of a new one 15:24:00 a really leet one 15:24:10 ask chuck moore to come to this channel for like an hour 15:24:23 advertise on CLF that ppl can get on and ask questions 15:24:28 moderate the whole thing 15:24:35 isn't it a slick idea? :P 15:24:46 now that'd be a l33t thing to do...but Chuck has a polemizing effect on many people.... 15:25:01 heh 15:25:07 * TheBlueWizard shrugs 15:25:09 i worship chuck 15:25:15 he is a radical minimalist 15:25:27 so? forth is a radical minimalist language 15:25:42 it has a value....but one can go only so far.... 15:25:46 i think it's bizarre that ppl will use forth and then disagree with chuck moore.. 15:25:53 lol 15:26:01 what do you mean "but one can only go so far..." ? 15:26:31 sure, it's probably too minimalist, forth coders should start building a bigger system, like a Forth OS to replace windows/unix/etc 15:27:14 and only forth coders on #forth can join FNRC (Forth's New Ruling Class) and get to code on the Forth OS ;) 15:27:26 except for chuck moore, he's automatically in :P 15:27:36 something along that line of thought, yeah...eg Chuck deems floating point stuff irrelevant (methink), multiple apps being unnecessary, and so on 15:28:19 lol....and what do you view I440r...a fellow member? 15:28:45 well, floating point stuff _is_ irrelevant, and can be easily abstracted from fixed point math, so that ppl can think they are using floating point math when it is actually being done in fixed point. besides, it depends on the architecture. today, floating point math is pretty fast 15:29:25 abstraction is one thing...mapping it to architecture is another thing 15:29:45 --- topic: set to 'do drop >in, if you don't, you won't be able to join FNRC (Forth New Ruling Class) | -- Extra Extra - Read all about it - (;code) (;uses) and does> all now work in IsForth - shock & horror!' by futhin 15:30:02 lol 15:30:50 well for each architecture parts of forth will be coded for it 15:31:24 hey, i read that ANS Standard actually killed Forth. before ANS came out, there were 40,000 memebers in FIG, after, there's only 2,000 in FIG 15:31:41 * TheBlueWizard blinks 15:31:54 pretty amazing eh? :) 15:32:03 that's why ANS Standard is evil 15:32:44 things have changed a lot...the advent of 32-bit systems and the demand for more complicated stuff has pushes Forth to a corner.... 15:32:54 now that's radical coming from you hehe 15:33:32 * TheBlueWizard is quite pragmatic about things 15:35:13 it's bullshit that "32-bit systems, demand for more complicated stuff, etc" has pushed Forth into a corner. i know why Forth is in a corner, it's because it was never promoted properly, it was never developed to please many programmers, it was never user-friendly/newbie-friendly, etc.. 15:35:28 plus, the older forths, 15:36:18 FIG-Forth, Forth-79, Forth-83 never actually implemented much, they were pretty minimalist because the coders believed that other forth coders did not want to be hindered by a large forth implementation, that other forth coders would extend their forths themselves 15:36:19 by demand I'm talking about the market...the consumers don't care a shit about what's under the hood... 15:36:26 yes true 15:37:13 yeah...there is that urge for minimalism...also the machines back then don't have much memory...say 32K RAM...so this urge for minimalism makes sense 15:37:41 forth is fast, it's fast to code in, etc.. no reason why we can't be using it to code every application out there 15:38:31 technically no reason, yeah...but practically...? has anyone actually pulled off developing a one meg sized app? 15:39:12 Forth has a way of "hating" the notion of "application" anyway 15:39:55 what's the need for a one meg-sized app? just because some app is 16 megs in some other language, does it mean it'll be 16 megs in forth? 15:40:07 or will it be 160k in forth? :) 15:40:32 forth coders don't really seem to do much :( 15:40:45 a 16 meg app in language X would be 1 meg app in Forth....now it is a 1 meg app :P 15:41:26 I often say "stop whining, code away!" ;) 15:42:12 no, what i mean is, forth coders don't really seem to code much.. 15:42:26 they seem to be lazy or something lol :P 15:42:35 my idea for solving this problem is: 15:42:56 online collaborative forth universe!!!! 15:44:10 :) 15:44:19 well, I need to go now...bye! 15:44:34 noooooo 15:44:34 noooooo 15:44:46 let me tell you about my leet collaborative forth universe!! :( 15:44:51 must go home...must shop.... 15:44:56 bye 15:44:57 heh 15:45:00 --- part: TheBlueWizard left #forth 16:48:22 --- part: futhin left #forth 16:48:33 --- join: futhin (Havoc36@ab-cal-a52-03-42.look.ca) joined #forth 16:48:33 --- mode: ChanServ set mode: +o futhin 17:07:17 --- quit: futhin ("-HAVOC- :P") 17:57:35 --- join: mememe (agaga@AC964CF6.ipt.aol.com) joined #forth 17:57:40 --- part: mememe left #forth 19:31:09 --- join: qless (~qless@clgr000977.hs.telusplanet.net) joined #forth 19:41:39 --- quit: qless ("changing dimensions") 19:53:50 --- join: TheBlueWizard (~tbw@ip-216-25-205-185.vienna.va.fcc.net) joined #forth 19:53:50 --- mode: ChanServ set mode: +o TheBlueWizard 19:53:59 --- part: TheBlueWizard left #forth 21:05:46 --- join: kholmes (~kholmes@client1175.sedona.net) joined #forth 23:09:34 --- quit: kholmes ("zzz") 23:46:06 --- quit: clog (^C) 23:46:06 --- log: stopped forth/02.01.31 23:46:21 --- log: started forth/02.01.31 23:46:21 --- join: clog (nef@bespin.org) joined #forth 23:46:21 --- topic: 'do drop >in, if you don't, you won't be able to join FNRC (Forth New Ruling Class) | -- Extra Extra - Read all about it - (;code) (;uses) and does> all now work in IsForth - shock & horror!' 23:46:21 --- topic: set by futhin on [Thu Jan 31 15:29:45 2002] 23:46:21 --- names: list (clog @ChanServ oxygene) 23:59:59 --- log: ended forth/02.01.31