[02:36:10] I never used the deploy or shaker stuff. How well does it work? [03:08:31] <^alex> the deploy stuff works decently at high reflection levels, but produces big executables [03:08:33] <^alex> ime [03:17:51] * df1scher [df1scher!~df1scher@cpe-172-114-80-45.socal.res.rr.com] has joined the channel. [03:56:49] * df1scher [df1scher!~df1scher@cpe-172-114-80-45.socal.res.rr.com] has quit (Read error: Connection reset by peer). [04:51:53] doublec: surprisingly well, https://github.com/factor/factor/issues/2329 pretty much sums it up tho [04:52:45] my stuff works at lvl 1-2 too (4M binaries) because I manually mess around with the shaker.factor file lol [04:53:28] the max (full environment) is 60-64M for me [04:54:01] but I only use it for debugging purposes, when it fails to run at lvl 1-2 [04:56:35] although I will have to check out why V{ } requires those 3 stuff to be deleted, that's gonna be much harder to "fix" imo [04:56:40] so for now I'm just using { } [04:57:15] because the binary without them stripped is ~60M [04:57:36] so almost as if I just used max reflection level [04:58:58] V{ } requires higher levels to run without an error (the binary), at lower levels it requires "root-cache", "vocabs:dictionary" and "vocabs:require-hook" to be kept (i.e. removed from being stripped in shaker.factor) [04:59:18] but since the size is the same as the max level, it doesn't make a difference [05:01:16] so the major issue is that at lower levels, the binary typically doesn't run, you get an error instead [05:02:20] because stuff it requires is stripped away [05:02:38] cuz everything is essentially hardcoded in shaker.factor [05:02:57] that needs fixing :p [05:04:14] and err, "stuff to be deleted" = commented out = stuff to be kept or not stripped away [05:18:56] and correction, the binary without them stripped (V{}-related stuff) isn't ~60M but 26M, apparently, but I'd have to re-check.. doesn't matter that much anyways, funnily enough a random go binary of mine is 21M, so that 4M is pretty neat with lvl 2, which is what I'm aiming for all the time [05:19:40] and I usually get away with it, but I couldn't this time (V{ }) :( [05:25:17] I was hopeful about vocab-uses (for getting rid of hardcoded shaker.factor) but I just used it with 2 vocabs and my crap that works uses the same stuff according to it as vectors, yet V{ doesn't work [05:27:48] it might be related to "growable" [05:28:20] which vocab-uses. doesn't even print, but vectors.factor uses it [05:29:08] could be related to "syntax" [05:29:33] not sure, but "growable" uses a lot of stuff, and the vocabs it depends on even more so, for example "syntax" [05:30:01] maybe a "deep" vocab-uses is what we need [05:30:06] idk [05:30:33] that goes through all vocabs and their deps and their deps and so forth, avoiding all duplicates [05:30:59] but still no clue how to make it work with shaker.factor anyways [05:31:11] haven't examined it that much [05:36:08] <^alex> we're just wondering what vectors do that plain sequences don't [05:51:51] they are resizable sequences, whereas arrays are fixed-length [05:52:16] you can use push and pop on them [05:53:15] see more at "Treating sequences as stacks" [05:53:21] and "Collections" [05:57:08] and ofc there r differences in performance, in diff use cases [05:57:34] gotta sleep, good nighties [09:07:33] * ephe_meral [ephe_meral!~amnesia@ip5f5bf7d1.dynamic.kabel-deutschland.de] has joined the channel. [10:05:15] * Sgeo [Sgeo!~Sgeo@ool-18b982ad.dyn.optonline.net] has quit (Read error: Connection reset by peer). [14:36:26] <^alex> ptrkriz, no i mean, we know _that_, i'm just wondering why they behave differently in the tree-shaker than plain sequences [14:37:44] <^alex> the "growable" seems to be a good clue [14:47:48] * tgunr [tgunr!~davec@dsl-dhcp-conrtxxahre-76-164-103-181.consolidated.net] has quit (Ping timeout: 258 seconds). [15:57:13] * ephe_meral [ephe_meral!~amnesia@ip5f5bf7d1.dynamic.kabel-deutschland.de] has quit (Ping timeout: 260 seconds). [17:01:24] * Sgeo [Sgeo!~Sgeo@ool-18b982ad.dyn.optonline.net] has joined the channel. [23:00:31] yeah [23:01:16] doublec: how come u have never used it btw? never needed an executable? [23:01:44] I think if factor couldn't do this, I would have just disregarded it [23:01:58] thankfully it supports it and I am using it now [23:02:02] it's a great piece of tech [23:02:17] best of all worlds I think [23:02:58] wish slava still had some time on improving parts here and there :p [23:16:56] <^alex> we follow slava on twitter, he posts good garden pics [23:46:42] I wonder why isn't he working on Factor, at least a bit :c [23:46:49] is it cuz of money, or lack of interest? [23:47:25] like what if we put up some ways for ppl to donate (on github) and on factorcode.org [23:47:33] and use it for hosting and whatever else [23:47:47] just dont let it corrupt ya!