00:00:00 --- log: started forth/08.02.10 00:04:42 --- quit: warpzero (Read error: 104 (Connection reset by peer)) 00:04:45 --- join: warpzero (n=warpzero@208.74.136.138) joined #forth 00:10:42 --- join: sauvin (i=sauvin@74-136-191-237.dhcp.insightbb.com) joined #forth 03:04:50 --- quit: sauvin (Remote closed the connection) 04:17:15 --- join: r2dtue (n=r2dtue@74-132-210-197.dhcp.insightbb.com) joined #forth 04:46:53 --- quit: r2dtue (Remote closed the connection) 07:50:04 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth 08:48:39 --- join: Quartus__ (n=Quartus_@209.167.5.2) joined #forth 09:03:00 --- join: foxchip (n=fox@166.129.132.126) joined #forth 09:05:39 Hello 09:10:08 Hello. 09:34:15 Hello. 09:38:00 hello 09:40:19 ok. 09:40:31 (wait, is there supposed to be a full stop there?) 09:41:05 Not according to gforth. 10:30:40 --- join: arke_ (n=arke@p57A74FDC.dip.t-dialin.net) joined #forth 10:31:52 --- quit: foxchip (Read error: 110 (Connection timed out)) 10:48:44 --- quit: arke (Connection timed out) 11:08:38 --- join: swestres (n=hihihi@Doc-14-47.veberod.com) joined #forth 11:13:50 --- join: X-Scale (i=email@89-180-19-16.net.novis.pt) joined #forth 11:23:07 --- join: foxchip (n=fox@166.129.132.126) joined #forth 11:25:06 --- join: ygrek (i=user@gateway/tor/x-10f1cc128ba92e6f) joined #forth 11:58:51 --- join: Snoopy43 (i=snoopy_1@dslb-084-059-110-159.pools.arcor-ip.net) joined #forth 12:11:29 --- join: sauvin (i=sauvin@74-136-191-181.dhcp.insightbb.com) joined #forth 12:15:43 --- quit: Snoopy42 (Read error: 110 (Connection timed out)) 12:15:55 --- nick: Snoopy43 -> Snoopy42 12:51:50 foxchip: so when is seaforth being released? 13:17:05 As Niel Bohr said, "Prediction is always difficult, especially about the future." And I am not sure how you define the term. 13:18:09 First SEAforth prototypes were shipped in 07, second and third gen should ship in 08, and production quantity is scheduled for 08. 13:21:06 As always existing chips have gone to people who were doing things with them. People who have shown impressive applications running on the simulator have been the first to get hardware. 13:22:45 Do you have a link to the simulator, or a page with more information? google is not being helpful. 13:24:30 rob_ert: kc5tja has seen it in person, maybe ask him. 13:24:43 --- nick: arke_ -> arke 13:24:50 I'm reading his post about it. 13:24:56 The waveguide synthesis came out of Russia. 13:28:02 --- quit: ygrek (Remote closed the connection) 13:29:41 64 words of RAM. Pretty tight. 13:33:23 Have you been working on a parallel version of factor? 13:35:07 Very tight. But it could hold up to 256 Forth words which would be 1kB on a 32 bit threaded implemenation. 13:35:52 foxchip: were you asking me? its not parallel in the sense of seaforth, no 13:35:57 is that 64 words per core? 13:36:08 Resources are distributed but even a node with 64 words of local ram may also see the ram on its neighbors through the shared ports and distributed code. 13:36:36 One has to factor into small pieces. 13:36:39 do those 64 words include a stack(s) or is that different? 13:37:52 Years ago, 03 I think, Chuck said that everyone seems to agree that Forth has its biggest advantage on machines with restricted resources and that he was going to create a machine with such constrained resources that Forth would be the only thing that would fit. 13:38:42 'restricted' is relative; what seemed like a supercomputer 10 yeras ago is restricted now, especially if you want to run linux/mac os/windows 13:38:44 Is there a useable simulator available? I would be interested in trying to at least try different tasks, in case I manage to get hold of a physical device one day. 13:38:46 After all the idea how much Forth needs, not how much Linux or C need. Hence there are a lot of other processors with nodes that are a thousand times larger. 13:39:12 foxchip: but the same code could run just as well on a machine with more memory 13:39:29 64 words of ram, 64 words of rom, stack is registers. The architecture is optimized for stacks, and they are stack registers that are faster than general purpose registers. 13:40:40 the latest compiler/simulator is available. There were a couple versions released so far. Currently they mail it out, or mail out a link or something. 13:41:11 The thumb drive comes with the compiler and documenation installed. 13:41:56 I am used to simulation in cad, which is painfully slow from a software perspective. The t18 compiler/simulator is very fast in comparison but is very slow compared to real hardware. 13:42:33 As long as it's fast enough to do some useful testing on, I'm happy. 13:43:20 "just as well" in the embedded world means at the same cost and power consumption and the problem is that a thousand times more transitors tends to mean a thousand times more cost and power consumption, or a thousand times less parallelism. 13:43:45 And certainly a big machine can do bigger sequential programs in a more straightforward way. 13:45:39 One thing that I like about multiprocessing, besides the software, is the realtime response aspect of it. 13:47:07 Bigger processors and interrupts can't compete there. 13:47:13 is anyone using seaforth for tcp/ip? 13:47:22 servers, clients 13:49:45 I enjoy using a big PC and I look forward to getting a SEAforth box on that scale some time, something with a few thousand clusters to do comparisons to Pentium instead of comparisons to other <$.10 processors. 13:50:11 what PC OS do you use? 14:01:52 On a PC I use ANS Forth or colorforth but I look forward to having a SEAforth PC box someday. 14:07:19 --- quit: foxchip (Read error: 110 (Connection timed out)) 14:26:50 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 14:26:51 --- mode: ChanServ set +o tathi 14:37:44 --- quit: ecraven ("bbl") 15:04:45 Hi tathi. 15:05:00 hi Quartus 15:05:06 Hey slava. 15:05:18 Get working on that parallel Factor, eh? :) 16:31:21 --- join: bit` (n=bit`@222.124.69.141) joined #forth 16:36:39 --- quit: sauvin (Remote closed the connection) 16:55:06 --- quit: rob_ert ("leaving") 17:40:23 --- quit: Baughn (Read error: 110 (Connection timed out)) 19:25:17 --- quit: proteusguy (Connection timed out) 19:26:11 --- join: proteusguy (n=proteusg@ppp-124-120-226-175.revip2.asianet.co.th) joined #forth 19:47:07 --- join: sauvin (n=sauvin@74-136-191-181.dhcp.insightbb.com) joined #forth 20:25:01 --- quit: tathi ("leaving") 20:43:46 --- quit: timlarson ("Leaving") 20:49:36 --- join: timlarson (n=timlarso@user-12l37rb.cable.mindspring.com) joined #forth 21:41:21 --- quit: X-Scale (Remote closed the connection) 22:09:00 --- quit: proteusguy (Read error: 104 (Connection reset by peer)) 22:27:07 --- join: proteusguy (n=proteusg@ppp-124-120-226-171.revip2.asianet.co.th) joined #forth 22:46:11 --- join: Baughn (i=svein@084202038064.customer.alfanett.no) joined #forth 23:00:36 --- quit: timlarson (Read error: 104 (Connection reset by peer)) 23:01:12 --- join: timlarson (n=timlarso@user-12l37rb.cable.mindspring.com) joined #forth 23:16:37 --- quit: arke (Client Quit) 23:53:46 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth 23:59:59 --- log: ended forth/08.02.10