[05:34:49] * flogbot [flogbot!~flogbot@2001:4800:7814:0:2804:b05a:ff04:4ba7] has quit (Ping timeout: 246 seconds). [05:34:57] * flogbot [flogbot!~flogbot@2001:4800:7814:0:2804:b05a:ff04:4ba7] has joined the channel. [05:34:57] :karatkievich.freenode.net 353 flogbot = #concatenative :flogbot ephe_meral FreeFull rotty ecx86 diginet earl Sgeo mtp rgrinberg sclv zgrep amuck lonjil delvinj MDude dustinm` pointfree rprimus groovy2shoes apajx doublec erg shmibs jeaye m_hackerfoo hackerfoo mollerse otoburb jeremyheiler strmpnk carvite jlewis merry @shapr shachaf cstrahan [05:34:57] :karatkievich.freenode.net 366 flogbot #concatenative :End of /NAMES list. [06:05:34] * FreeFull [FreeFull!~freefull@defocus/sausage-lover] has quit. [07:53:08] * Sonderblade [Sonderblade!~fack@h-52-183.A157.priv.bahnhof.se] has joined the channel. [08:21:39] * MrBusiness3 [MrBusiness3!~ArcMrBism@2602:306:8325:a300:c801:d7f:77e1:92be] has joined the channel. [08:22:23] Wait, this is the channel for discussion of the Kitten language? [08:22:35] Or is it for discussion of multiple languages? [09:21:41] MrBusiness3: multiple [09:21:48] MrBusiness3: Kitten is discussed here though [09:21:57] interesting [09:22:38] Kitten is a fascinating evolution of the basic Forth notion. The application of Hindley-Milner strong typing is especially fascinating, and I think well-suited to the application space. [09:22:53] I've barely dived into it though. [09:23:12] Already got a chaotic mess of programming languages floating around this machine. [09:26:29] My current project is attempting to make an Intel Compute Stick that boots into a ColorForth with a couple of drivers I may have to get off of archive.org's Wayback machine to enable me to use the scant SSD space available to write my words to disk for preservation between boots. [09:26:50] I'm not sure precisely how doomed I am here, but I'm betting that this project will be reasonably abortive. [09:30:05] IT's mostly an object in trying to mutate what currently seems to only exist as a bootable iso image into the main bootable image on the small device, then perhaps do some custom keyboard construction to adapt to the bizarre-o requirements of the thing. [09:30:57] well, the strange semantics of the keyboard that apparently change in such a way that only 27 keyboard buttons are used, and the whole thing is bizarrely modal, in addition to the actual colorization of inputs. [09:57:21] I've not used colorforth but from what I've read it looks like quite a challenge. [10:34:01] Yeah, the challenge is definitely the thrill of the otherwise useless exercise. [10:34:09] Be worth a blog post or two at best. [10:35:17] Unless I can then transact the second part of my plan wherein I attempt to redefine the whole thing into another Forth of my own creation that takes whatever good ideas I can extract from CF and other stack-based langs, as well as anything I can scrape out of embedded C libs to add some low-level framebuffer controls. [10:40:48] Also be nice to make it multi-core aware, such that I can create complete, independent Forth environments, one per core, and provide them with a shared memory area as well as private memory contained within each Forth stack. [10:41:26] But ultimately I just want something that'll take away all the basic advantages of an OS and force me to work with raw machinery. [10:42:10] Probably end up doing better to look to a non-X86 type of embeddable Forth, but ColorForth always fascinated me. I still have my first ColorForth disc somewhere around here. [10:42:47] And I seem to have found a few GitHubs mirroring the code for it somewhere, so maybe one of those can give me a base to work from for adding and subtracting my modifications. [10:43:46] But I reckon that First I'll need to figure out some way to get the .iso translated into something that I can `dd` or otherwise write onto the compute stick. I'm sure Rufus can provide some kind of result to this effect. [10:44:34] Worst comes to worst I'll just have to wax whatever is on the compute stick and then have Rufus dd the ColorForth.iso onto a small MicroSD card, then have the compute stick boot from that somehow. [10:45:16] No telling how well it'll work, if at all. Realistically, I guess I could even run a disc from it if I added a powered USB hub and a USB DVD burner [10:46:08] might work as long as the stick can do a USB boot. That seems more likely than a MicroSD boot. Of course, all this assumes that the compute stick is a versatile medium with an accessible UEFI/BIOS [10:46:38] and given that it's just a really small Atom SoC, I don't see how it could be anything else, but I hear that some atoms don't have the gumption. [10:47:20] Originally I wanted to do a stick with multiple environments and a classic GRUB 2 bootloader to permit selection of runtime environment at boot that ideally wouldn't need much maintenance. [11:31:30] * MrBusiness3 is now known as MrBusiness [16:02:26] * FreeFull [FreeFull!~freefull@defocus/sausage-lover] has joined the channel. [17:54:05] KITTEN [17:59:02] ahoy [18:05:34] howdy mtp, how's code? [18:05:39] not bad [18:05:45] i put two PRs on the factor gitblub [18:05:53] under username "twopir" [18:06:15] seems like it's a pun on tapir, but I don't get it [18:06:25] it's a mathematical formula [18:06:28] two*pi* r [18:10:00] ohhh [18:10:02] that is punny [20:09:09] mtp: cool, i can look tonight [20:28:34] thx [20:28:41] also i found the theme support [20:29:06] https://pbs.twimg.com/media/DM2WfFfU8AAKyaF.jpg:orig [21:06:13] * jtimon [jtimon!~quassel@164.31.134.37.dynamic.jazztel.es] has joined the channel.