00:00:00 --- log: started forth/07.10.09 00:00:02 in factor's case the problem is taht if you recompile a word, it recompiles all callers (direct and indirect) 00:00:11 the compiler needs to be a bit smarter than that 00:00:21 ahh 00:00:26 so that loading a module which defines new methods on generic words in the core library doesn't take so long 00:00:57 oxygene: that works for me 00:01:37 oxygene: I suspect that I'd want to code in a specific way for speed anyway, ie to avoid the need for runtime type checking 00:02:04 squeak has an ffi 00:02:31 oxygene: does squeak have an optomizing compiler that it uses only for code that it knows is slow? 00:02:45 squeak is abytecode interpreter 00:02:53 its a bit faster than python 00:04:00 so exupery compiles to squeak bytecode? 00:04:16 oh, exupery 00:04:21 that's an optimizing native code JIT 00:04:26 but its not part of squeak yet 00:04:34 ahh, up and coming 00:04:55 its written in squeak, which is cool 00:05:07 quite 00:05:57 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth 00:42:06 --- quit: slava (Read error: 110 (Connection timed out)) 01:42:05 --- join: arcus (n=ajt@203.109.162.167) joined #forth 02:29:19 --- quit: arcus ("Ex-Chat") 02:46:41 --- quit: H4ns (Read error: 113 (No route to host)) 02:51:20 --- quit: wossname (Read error: 110 (Connection timed out)) 03:15:34 --- join: H4ns (n=Hans@t54fc4141.pool.terralink.de) joined #forth 04:13:25 --- quit: Off_Namuh72 (Read error: 104 (Connection reset by peer)) 04:25:58 --- join: Off_Namuh72 (i=GPS@gateway/tor/x-a429561a61824b0f) joined #forth 04:33:53 --- join: wossname (n=w@CPE00195b252b77-CM001a666a6e78.cpe.net.cable.rogers.com) joined #forth 05:29:49 --- join: skas_wk (n=skas@202-90-54-135.static.linearg.net) joined #forth 05:34:22 --- join: H4n1 (n=Hans@t54fc4141.pool.terralink.de) joined #forth 05:48:30 --- quit: H4ns (Read error: 110 (Connection timed out)) 05:50:55 --- nick: H4n1 -> H4ns 06:51:24 --- quit: wossname (Read error: 110 (Connection timed out)) 06:52:13 --- join: nighty-- (n=nighty-@66-163-28-100.ip.tor.radiant.net) joined #forth 06:53:01 --- quit: nighty- (Read error: 104 (Connection reset by peer)) 07:21:02 --- quit: H4ns (Read error: 110 (Connection timed out)) 07:33:37 --- join: H4ns (n=Hans@t54fc4141.pool.terralink.de) joined #forth 07:36:09 --- quit: ecraven ("bbl") 07:54:27 --- quit: ygrek (Remote closed the connection) 07:59:33 --- join: Al2O3_ (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 08:03:50 --- quit: Al2O3_ (Client Quit) 08:05:48 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 08:11:53 JasonWoof: Keep also in mind the fact that modern computing hardware runs at effectively infinite speeds compared to computers of only 10 years ago. Much of the language inefficiencies is masked by that speed. :) 08:13:00 --- quit: Al2O3 (Read error: 110 (Connection timed out)) 08:13:04 I don't see any inherent problem with writing a web-app in Forth, provided you have a powerful enough set of string manipulation words. 08:14:00 I find the largest problem with Forth today is the lack of a standardized set of semantics and words for defining what is, and referencing other, modules. 08:14:26 But, there are, I believe, techniques that works around that limitation. 08:14:34 Anyway, I need to get ready for work. 08:25:13 --- quit: skas_wk ("I'm outta here.") 08:26:41 yes strings are a bear to work with in Forth 08:33:36 --- join: wossname (n=w@CPE00195b252b77-CM001a666a6e78.cpe.net.cable.rogers.com) joined #forth 08:42:55 --- quit: forther (Read error: 110 (Connection timed out)) 09:01:10 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 09:08:31 --- quit: warpzero (Read error: 110 (Connection timed out)) 09:48:52 --- join: Al2O3 (n=Al2O3@12.190.128.2) joined #forth 10:05:51 --- quit: FMota (Read error: 104 (Connection reset by peer)) 10:06:07 --- join: FMota (n=FMota@dhcp-36-203-57-69.cf-res.cfu.net) joined #forth 10:11:36 --- join: ygrek (i=user@gateway/tor/x-6c68adf21a4b6039) joined #forth 10:16:48 --- join: forther (n=forther@207.47.34.100.static.nextweb.net) joined #forth 10:17:21 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth 10:29:03 --- join: neceve (n=ncv@86.104.205.201) joined #forth 10:47:06 --- quit: H4ns (Read error: 110 (Connection timed out)) 10:53:10 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-113-000.pools.arcor-ip.net) joined #forth 10:57:34 --- join: Quartus__ (n=Quartus_@205.205.50.2) joined #forth 11:01:26 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 11:01:29 --- nick: snoopy_1711 -> Snoopy42 11:25:37 --- join: FMota_ (n=FMota@dhcp-36-203-57-69.cf-res.cfu.net) joined #forth 11:25:37 --- quit: FMota (Read error: 104 (Connection reset by peer)) 11:55:28 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 12:00:50 --- join: saon (n=saon@207.138.42.211) joined #forth 12:18:53 --- join: H4ns (n=Hans@p57A0D3D0.dip.t-dialin.net) joined #forth 12:20:28 --- quit: ecraven ("bbl") 12:34:13 --- quit: Al2O3 () 13:02:10 --- quit: saon ("Lost terminal") 13:34:37 --- quit: Off_Namuh72 (Remote closed the connection) 13:50:52 --- quit: ygrek (Remote closed the connection) 13:58:55 kc5tja: forth would be great for web apps if it had string manipulation, type conversion, and a few other features 13:59:10 objects 13:59:31 I started building some of that, but saw that I didn't have time to get it to the point where it was more useful than php 14:00:22 --- quit: neceve (Read error: 104 (Connection reset by peer)) 14:00:41 --- join: neceve (n=ncv@86.104.205.201) joined #forth 14:14:54 --- join: Al2O3 (n=Al2O3@12.190.128.2) joined #forth 14:15:33 --- join: Quartus__ (n=Quartus_@205.205.50.1) joined #forth 14:17:42 --- quit: Quartus__ (Client Quit) 14:18:19 --- join: Quartus__ (n=Quartus_@205.205.50.1) joined #forth 14:22:24 --- join: doublec (n=doublec@202.180.114.137) joined #forth 14:32:32 --- quit: timlarson_ ("Leaving") 14:43:05 --- quit: neceve (Read error: 104 (Connection reset by peer)) 14:43:29 --- join: neceve (n=ncv@86.104.205.201) joined #forth 14:46:18 --- join: Raystm2 (i=NanRay@c-24-8-127-241.hsd1.co.comcast.net) joined #forth 15:01:09 --- join: crest_ (n=crest@p5489D9A8.dip.t-dialin.net) joined #forth 15:15:51 --- quit: crest__ (Read error: 110 (Connection timed out)) 15:53:28 --- quit: forther ("Leaving") 15:58:21 --- quit: wossname (Read error: 110 (Connection timed out)) 16:09:16 --- quit: Al2O3 (Read error: 104 (Connection reset by peer)) 16:14:37 --- join: skas_wk (n=skas@203-217-61-74.perm.iinet.net.au) joined #forth 16:37:53 --- join: warpzero (n=warpzero@208.74.136.138) joined #forth 16:53:52 --- join: Off_Namuh72 (i=GPS@gateway/tor/x-fba6d35ec4123405) joined #forth 17:09:12 --- quit: XeF4 (Remote closed the connection) 17:09:42 --- join: XeF4 (n=xef4@64-13-127-207.anc.clearwire-dns.net) joined #forth 17:40:34 --- join: wossname (n=w@CPE00195b252b77-CM001a666a6e78.cpe.net.cable.rogers.com) joined #forth 17:41:53 --- quit: XeF4 ("leaving") 17:42:04 --- join: XeF4 (i=xef4@epilogue.org) joined #forth 18:47:34 --- quit: skas_wk ("I'm outta here.") 19:28:51 --- join: Al2O3 (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 19:34:31 --- join: edrx (i=edrx@189.25.92.174) joined #forth 20:55:06 --- join: slava_ (n=slava@99.241.52.58) joined #forth 21:15:47 --- quit: doublec () 21:32:35 --- nick: slava_ -> slava 21:45:17 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 21:50:29 hey slava 21:50:32 hey 21:50:41 what's new? 21:51:00 gearing up for a new release 21:51:14 new features? 21:51:31 mostly behind the scenes improvements 21:51:48 fun 21:51:51 better performance across the board 21:52:23 any sacrifices required? 21:52:45 not really. i have a ton of things i want to improve but there's only so much time in a day 21:53:15 that's the truth. 21:54:31 how's the book? 21:54:56 haven't had much time to work on it so far in October. 21:56:06 have you looked in on poppavic? 21:56:19 no, how's he been doing lately? 21:57:13 Haven't been on much lately, hence my question :) 21:57:42 i'm not privy to any details 21:58:14 he was spiraling appreciably down last time I was on ##c 22:00:47 I see a decrease in recent werties 22:01:19 what's happening to the world!? 22:01:51 heh. Hi Jason 22:02:10 we need nut cases in order to feel good about having our shit mostly together 22:02:22 hi :) 22:03:13 I just find some of the real nutters remarkable 22:03:24 doty? 22:03:29 he hasn't been that nutty lately 22:04:02 Quartus__: in what way? 22:04:03 I don't read his messages any more; his banjo only has one string. 22:05:32 jason, perhaps that their fixations are so single-minded and invariant :) 22:06:17 whoever made that comment on c.l.f that people there tend to only compare forth against C and Ada and Fortran, and not modern languages, was spot on, though. 22:06:35 it seems a lot of people there are not even aware there have been any advances since C 22:06:42 heh 22:06:56 there are some pretty cool languages out there 22:07:04 luddites! :) 22:28:14 --- join: arcus (n=ajt@203.109.162.167) joined #forth 23:09:16 Woolites! 23:14:34 --- quit: forther ("Leaving") 23:27:40 * kc5tja must remember to record a continuation when he stops coding on a project for any significant length of time. :) 23:59:59 --- log: ended forth/07.10.09