00:00:00 --- log: started forth/18.01.05 00:08:50 --- quit: dys (Ping timeout: 240 seconds) 00:45:20 --- quit: groovy2shoes (Ping timeout: 250 seconds) 00:59:07 --- join: dys (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) joined #forth 01:05:57 --- quit: Keshl (Read error: Connection reset by peer) 01:06:38 --- join: reepca (~user@208.89.170.230) joined #forth 01:06:39 --- join: Keshl (~Purple@24.115.185.149.res-cmts.gld.ptd.net) joined #forth 02:45:20 --- quit: ThirtyOne32nds (Read error: Connection reset by peer) 03:53:09 what are the opinions of Lua vs Forth? 04:03:27 ryoshu: forth could almost do anything 04:07:49 can I replace use-cases of Lua with Forth? 04:16:23 why cant you? actually i was the one who talk about replace lua using forth again and again in this channel 04:16:36 for eg, replace lua in nginx and redis 04:47:30 --- join: ncv_ (~neceve@90.192.52.48) joined #forth 04:47:30 --- quit: ncv_ (Changing host) 04:47:30 --- join: ncv_ (~neceve@unaffiliated/neceve) joined #forth 04:50:17 I'm looking for comparison of features, performance, integrability, management etc 04:54:28 --- join: gravicappa (~gravicapp@h62-133-162-164.dyn.bashtel.ru) joined #forth 04:54:52 ryoshu, forth applications, properly used are generally domain specific languages that fit the nomenclature of the application you're trying to build. If that's a desirable characteristic then forth is quite likely for you. If not, then the commonality of Lua might be a preferable option. Naturally it all depends on your app. 04:55:20 --- join: ThirtyOne32nds (~rtmanpage@76.sub-174-204-16.myvzw.com) joined #forth 05:50:14 --- quit: gravicappa (Ping timeout: 248 seconds) 05:54:52 how large applications are maintainable in Forth? 100k LOC? 05:54:59 are there any of that size? 05:55:12 is Forth terribly slow with a large dictionary? 06:02:40 whether forth is slow with a large dictionary really depends on the forth implementation. on my (very unfinished) forth, only compiling would become slow, not running words (once a word is looked up), because it only walks the dictionary when it looks up words, calls between words are O(1) 06:03:17 --- join: lijero (~lijero@unaffiliated/lijero) joined #forth 06:04:10 some forth implementations could also implement word lookup more efficiently than a linear search 06:04:22 calls between words are O(1) - ah, this is what I wanted to know 06:04:32 is this hash table? 06:04:37 implementation 06:06:14 what do you mean by "is this hash table impmlementation?" 06:07:13 my implementation (only i get around to finishing it) uses a singly linked list for the dictionary structure and call instructions for calls 06:07:24 ah, I see 06:07:38 now clear 06:09:07 a hash table would make dictionary lookup faster when there are a lot of words 06:17:03 are there some notable programs written in Forth? 06:18:51 except firmware 06:21:46 i think there was a successful space exploration game written in fortht 06:22:11 https://en.wikipedia.org/wiki/Starflight 07:03:50 regarding the question about large dictionaries: I would imagine such a large codebase would probably be broken into vocabularies, which would limit the scope of searches 07:15:33 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 07:41:12 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 08:08:28 --- join: gravicappa (~gravicapp@h62-133-162-164.dyn.bashtel.ru) joined #forth 09:12:27 --- join: tomlukeywood (~tom@host-92-19-232-58.static.as13285.net) joined #forth 09:33:45 --- quit: dys (Ping timeout: 276 seconds) 09:42:58 --- quit: djinni (Quit: Leaving) 09:46:49 --- join: djinni (~djinni@68.ip-149-56-14.net) joined #forth 11:33:12 --- quit: gravicappa (Ping timeout: 248 seconds) 11:34:38 --- quit: zy]x[yz (Quit: leaving) 11:35:07 jn: the uder interface reminds me of MS space simulator 11:35:08 D 11:35:09 XD 11:36:54 --- join: zy]x[yz (~corey@unaffiliated/cmtptr) joined #forth 12:08:19 --- part: tomlukeywood left #forth 12:31:23 --- quit: ncv_ (Ping timeout: 268 seconds) 12:55:56 --- join: groovy2shoes (~groovy2sh@unaffiliated/groovebot) joined #forth 13:02:40 --- quit: groovy2shoes (Quit: moritura te saluto) 13:05:34 --- join: dys (~dys@tmo-099-188.customers.d1-online.com) joined #forth 13:08:25 --- join: groovy2shoes (~groovy2sh@unaffiliated/groovebot) joined #forth 13:14:35 --- quit: dddddd (Remote host closed the connection) 13:32:12 --- quit: sigjuice (Ping timeout: 256 seconds) 13:33:29 --- join: sigjuice (~sigjuice@107.170.193.86) joined #forth 14:14:41 --- join: jcob (~user@cpe-172-74-189-35.nc.res.rr.com) joined #forth 14:36:00 --- join: MrBismuth (~ArcMrBism@2602:306:8325:a300:1426:998c:b44b:81fb) joined #forth 14:39:31 --- quit: MrBusiness (Ping timeout: 265 seconds) 14:41:59 http://www.forth.org/successes.html 15:11:43 --- quit: dys (Ping timeout: 268 seconds) 15:22:42 --- quit: ThirtyOne32nds (Read error: Connection reset by peer) 15:50:16 --- quit: jcob (Ping timeout: 252 seconds) 16:54:48 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 17:53:39 --- join: ThirtyOne32nds (~rtmanpage@180.sub-174-204-5.myvzw.com) joined #forth 18:19:07 --- join: MrBusiness3 (~ArcMrBism@2602:306:8325:a300:1426:998c:b44b:81fb) joined #forth 18:20:38 --- join: lijero_ (~lijero@2601:600:8180:4d:fabc:12ff:feff:f5a) joined #forth 18:27:10 --- quit: MrBismuth (*.net *.split) 18:27:10 --- quit: lijero (*.net *.split) 18:27:12 --- quit: Riviera- (*.net *.split) 18:32:52 --- join: Riviera- (Riviera@2a03:b0c0:1:d0::10:b001) joined #forth 19:52:06 --- quit: proteusguy (Ping timeout: 252 seconds) 20:39:22 --- join: proteusguy (~proteus-g@182.232.28.195) joined #forth 20:39:22 --- mode: ChanServ set +v proteusguy 20:43:48 --- nick: lijero_ -> lijero 20:43:55 --- quit: lijero (Changing host) 20:43:55 --- join: lijero (~lijero@unaffiliated/lijero) joined #forth 20:53:12 --- quit: proteusguy (Ping timeout: 248 seconds) 21:13:07 --- join: gravicappa (~gravicapp@h62-133-162-39.dyn.bashtel.ru) joined #forth 21:57:10 --- quit: Gromboli (Quit: Leaving) 22:08:27 --- join: proteusguy (~proteus-g@182.232.28.195) joined #forth 22:08:27 --- mode: ChanServ set +v proteusguy 22:09:12 --- quit: dddddd (Ping timeout: 268 seconds) 22:11:24 ryoshu, dictionary size only impacts compilation. Once your words are compiled, invoking them is straight up function calls. 22:11:50 oh jn already covered that. :) 22:15:08 --- quit: lijero (Remote host closed the connection) 23:59:59 --- log: ended forth/18.01.05