00:00:00 --- log: started retro/10.04.25 00:09:27 --- quit: Mat2 (Quit: Page closed) 01:06:54 --- quit: sixforty (Quit: Leaving.) 07:43:11 --- quit: crc (Ping timeout: 260 seconds) 07:44:42 --- join: crc (~charlesch@184.77.185.20) joined #retro 07:52:35 --- quit: crc (Ping timeout: 245 seconds) 07:54:22 --- join: crc (~charlesch@184.77.185.20) joined #retro 08:11:14 good morning 08:11:18 hi docl 08:11:25 hi crc 08:11:26 * crc is playing with fossil version control 08:11:50 cool 08:11:54 any good? 08:12:01 yeah 08:12:26 wiki, bug reports, distributed version control. one binary; stores the entire repo as a single sqlite database. 08:12:32 built in web interface too :) 08:12:38 cool! 08:14:30 http://rx-core.org:8080/index 08:16:26 fossil core docs at http://www.fossil-scm.org/index.html/doc/tip/www/quickstart.wiki 08:26:08 getting a copy 08:31:24 nice! 08:36:19 I just moved 'words' and '.s' to core.retro 08:40:18 so do I simply type "fossil pull" to get the latest changes? 08:40:25 I believe so 08:41:57 hmm, I did that and it does not seem to do anything when I type "words" 08:47:36 I'm sure I'm just not pulling it right. the file does not seem to match the one in the latest revision. 08:51:08 ahh, I needed to run "fossil update" so that it pulls it in from rx.fossil 08:51:16 I just found that :) 08:51:26 so it's like hg in that regard 09:00:16 pushed a couple more small things 09:32:09 * docl is reading up on sqlite 09:38:05 sqlite has become the *only* database I use in new projects :) 09:38:29 :) 09:38:51 I use MySQL at work, so this is interesting. 09:43:51 "A good rule of thumb is that you should avoid using SQLite in situations where the same database will be accessed simultaneously from many computers over a network filesystem." 09:46:09 I don't use network filesystems :) 09:47:03 "Most SQL database engines are client/server based. Of those that are serverless, SQLite is the only one known to this author that allows multiple applications to access the same database at the same time." 09:47:22 quotes from the sqlite website 09:47:45 I've seen the second one before 09:48:28 I am curious as to whether this could substitute for mysql in a small office where multiple computers are accessing the same databaase. 09:49:17 I've not tried it in a case like that 09:50:10 what we typically do is set one computer to be the "server", and the other computers connect to it on port 3306. the server is usually also the host for a shared folder that is used for things like images and PDF files. 09:51:08 both of these things can be done from Linux even though the main program itself does not run on Linux (or at least, the latest versions do not.) 09:51:58 http://www.sqlite.org/cvstrac/wiki?p=SqliteNetwork 09:52:37 looks like there are several programs that can share sqlite via TCP/IP 09:53:05 cool :) 09:54:20 Most of my code using sqlite only allows for limited access to updating the db. Users have limited ability to modify things (by design), and most updates get done in batches by a set of server-side scripts 10:01:34 nice 10:01:43 what apps have you written that use sqlite/ 10:02:48 paki (twitter via email), patengi (ebook library), ent (used for tracking user accounts) 10:03:42 cool 10:08:13 of these, paki gets the most use (60k-80k queries per day) 10:11:35 paki sends out around 4800 emails per day to the users. And there are only around 30 active users :) 10:14:22 that's a lot of emails! 10:14:46 so this lets them receive tweets as emails, basically? 10:15:05 send, receive, follow users, stop following users 10:15:11 all of the core functionality 10:15:19 neat! 10:15:29 * docl has never used twitter 10:25:09 I have a twitter account; I use it mostly for communicating with family from out of state and random postings on code or scifi 10:28:29 yeah that is what I currently use facebook for mostly, communicating with family. 10:28:55 I have facebook too, but it's not as nice on a mobile device (I use my phone for a lot of things now) 10:49:55 --- quit: crc (Ping timeout: 248 seconds) 10:51:52 --- join: crc (~charlesch@184.77.185.20) joined #retro 11:30:13 --- join: sixforty (~sixforty@pdpc/supporter/active/sixforty) joined #retro 12:27:17 --- join: Quartus (~neal@CPE0022b0b24a15-CM001947482b20.cpe.net.cable.rogers.com) joined #retro 14:35:14 --- quit: virl (Remote host closed the connection) 14:43:23 --- quit: SimonRC (Ping timeout: 246 seconds) 15:45:54 --- join: erider (~chatzilla@unaffiliated/erider) joined #retro 16:02:39 hello 16:02:50 hi, erider 16:10:24 hi sixforty whats new 16:11:17 nothing yet. Have had 1+ days to idle. Doing things other than forth, tho. 16:14:44 hi erider 16:15:08 hey crc 16:15:20 sixforty: what kinds of stuff 16:17:09 Doing linux configs, asking/answering linux q's. Should be doing forth instead, but I want my system to be friendly before I start. 16:18:23 right now, trying to decide which shell ends up linked to sh. dumping bash, but there be init bashisms 16:18:45 well, not dumping, but something else will be linked to sh 16:20:30 --- quit: Quartus () 16:25:59 sounds like you are going to have a long night 16:40:03 can't be too late, up at 0500 16:54:35 crc what are you up to 16:54:58 I setup a fossil repo for core retro stuff at http://rx-core.org:8080 16:55:30 did you get the vm down anymore 16:56:28 623 lines for vm, 1,049 for metacompiler+core retro system 16:57:15 not to bad 17:21:36 I'm pleased with it so far 17:25:03 --- join: SimonRC (~sc@fof.durge.org) joined #retro 17:25:10 hi SimonRC 18:03:14 --- join: erider_ (~chatzilla@pool-173-69-156-197.bltmmd.fios.verizon.net) joined #retro 18:04:37 --- quit: erider (Ping timeout: 265 seconds) 18:04:42 --- nick: erider_ -> erider 18:11:45 --- quit: erider (Quit: ChatZilla 0.9.86 [Firefox 3.6.3/20100401080539]) 20:36:34 --- quit: sixforty (Quit: Leaving.) 23:59:59 --- log: ended retro/10.04.25