trinque: and jfw, dorion_road, if you don't see the word "Gales" in there, it's because I'm trying to disabuse you of the notion that there's such thing as a "Gales" which you made, by way of sheer numbers.
trinque: and I'm not even halfway to a blinking cursor yet
trinque: ftr not saying anything about the value of the gales work, above. I think it's quite valuable, but we'll get there.
diana_coman: trinque: is the select thing not working on your blog? I'm trying to select that great "fits in hand" and I can't seem to,
this doesn't do anything.
mircea_popescu: in this morn's stray thoughts : if "wife" ends up spelled "waifu" in japanese, is it the case "kungfu" really should be "knife" ?
ossabot: Logged on 2019-12-28 07:29:14 spyked: mircea_popescu: hm, from what I see it only sent the comments/new feeds since it first saw mircea_popescu offline
mircea_popescu: sorry for the constant complaints borne out of user error, plox don't take it to heart.
ossabot: Logged on 2019-12-28 09:08:25 hanbot: in other unexpected wins, wikipedia started redirecting my browser to "mandatory upgrade" sometime last week. of all the deprecations i've steadfastly watched pass by in my box's moat as it were, this one is by far the most satisfying.
mircea_popescu: in keeping with the theme, "pedoworld reality distortion field" ends up spelled "wiki" in hawaii or some shit.
ossabot: Logged on 2019-12-28 12:21:04 trinque: specifically, if you saw fit to issue a deed for #trinque , I'd happily accept
ossabot: Logged on 2019-12-28 17:35:36 trinque: god damned bootloader being larger than an entire userland, holy hell.
mircea_popescu: incidentally BingoBoingo what's the snag now ? your client ran off from under you after paying ?!
deedbot: 2019/08/01 17:40:34 <shrysr> mp_en_viaje: yes selection on your pages work, and so does younghands.club, .. seen it before and just rechecked.
mircea_popescu: apparently now there's
drama about people i don't even recall ever hearing of. i have fiddy tabs open struggling to keep up with everyone over here and barely managing... it's like an xmas miracle or something.
BingoBoingo: rilema/2019-12-23#1956012][instructions for me,] which I also submitted to deedbot.
whaack: mircea_popescu: approved ^
mircea_popescu: BingoBoingo, aite, i might be out for a few days seeing how it's new year but we shall resume in 2020
mircea_popescu: "A feature that I liked a lot is that shell is the only scripting language in the default install of the distribution. Typically perl and python get pulled in unconditionally as a build dependency of a runtime dependency of some rarely-used default-installed utility, or are directly used to implement package manager, etc. With Gales, a decision about what scripting language to use can be made without constraints created
mircea_popescu: by ready availability of python or others." << indeed this is mindblowingly beautiful, and as far as i current;y know the foremost fearher in jfw 's cap.
mircea_popescu: neways, as to the burning "OTOH, I wonder if things like Apache or imagemagick get installed, how will the package management system work out, and how comprehensible will system stay?" question -- i see the merit of using the clean spot as a fixed point to attempt expanding cleanliness. so, it would work by apache becoming tmserv or w/e, and not sucking anymore.
mircea_popescu: or to put it another way, i do not believe it is either intelligent or even tolerable to try and carry forward the "install" paradigm from derpworld. something much more akin to diana_coman 's work on eulora is what "get installed" will have to mean.
trinque: mircea_popescu: does this mean "everything is always built and installed" ?
bvt: mircea_popescu: ty; fixed.
trinque: I don't for example need anything GUI-related in an embedded linux device
trinque: I agree that there should be single, correct answers when choosing components (as I'm trying to lay out the options for such selection in my series), but not that each component is always present in any system.
trinque: they are however all to be in the source v-tree, of course.
bvt: mircea_popescu: re second q, imho cleaning up the components will be driven by how the OS gets [re]structured around V, too early to say right now
trinque: bvt: not trying to be a pedantic dick over here, but it's v that's the boundary around the other stuff, not the other stuff around v
bvt: at the individual v-trees sure, but on the yddragsil level?
trinque: no, there's only one v tree
trinque: we've just only ever composed fragments of it yet.
bvt: in this case, i can restate it as 'depends on how current fragments will get composed into one tree'
ossabot: Logged on 2019-12-29 05:44:04 diana_coman: trinque: is the select thing not working on your blog? I'm trying to select that great "fits in hand" and I can't seem to,
this doesn't do anything.
diana_coman: trinque: I had a look at your published
paster lisp code; my current understanding is that it's only a part of what's required to stand up a backup paste service though, isn't it? mind pointing me to the rest of the bits/a recipe to put it all together? I had this idea that it's saner to replicate at the very least the paste service and a mirrored wot website. My current understanding of that paster ...
diana_coman: ... lisp code is that it pulls in the drakma
http client that pulls in as far as I can see another 18 deps (and moreover so far one of them fails anyway on my current setup aka centos 6 with sbcl 1.0.39, asdf 2.26; but I see that whaack reports
sbcl 1.4.14 working for the logbot so I'll try it next with that and see.)
trinque: yeah, that thing's just a lib around doing
http posts to what's a very simple wad of php
diana_coman: whaack: what version of asdf did you get to work with all the rest anyway?
whaack: diana_coman: From my experience, for most packages from quicklisp you're going to have problems if you don't have asdf 3+, which comes with sbcl 1.4.14 (not sure what the first version of sbcl with asdf 3+ was)
trinque: I can genesize the phpwad as well.
whaack: diana_coman: i'm using asdf 3.3.1
diana_coman: noted, thanks; basically so far it's have fun with python versions or fun with asdf version, lolz.
whaack: diana_coman: I tried and failed to upgrade to asdf 3+ while keeping my sbcl 1.something . That is one reason why I switched my sbcl to 1.4.14
trinque: whaack: what's the principle upon which you choose versions of these?
whaack: trinque: I can't say I am principled in the manner. in general, i use the lowest version that works
trinque: I think this is a bad heuristic.
trinque: version is serving here as a proxy for complexity
whaack: trinque: i am more than open to hear yours
trinque: there's also this hard-to-define cultural decay element
trinque: whaack: in this case, between sbcl-1.0.50 and the latest, the C kernel of the thing actually got smaller by roughly a third, while the lisp part expanded by about 100k lines
trinque: so it's not so clear that it got harder to maintain as time went on, depending a whole bunch on where that extra lisp ended up
trinque: lines are another bad proxy for complexity, but they're a better measure than the version triple
whaack: trinque: what were the sizes of the C kernel and lisp part to begin with?
whaack: trinque: And what version of sbcl + asdf do you use yourself?
trinque: I try not to use asdf at all, anymore.
trinque: but I've had a pretty violently negative reaction to the whole pile.
trinque: I'd be willing to abandon lisp for now, seeing as how the usable components incur at least another 400k lines of bloat, and for that you gain yet another javascript ecosystem.
trinque: if we were to retain lisp, I'd say pick one, don't have a python alongside it, and don't expect to use much "open source" to help you.
trinque: clozurecl ftr is just about as fat as sbcl these days.
trinque: and both of these are larger, again, than ALL OF BUSYBOX
trinque: and that's the latest, fattest busybox yet.
trinque: anyhow, gonna stop skipping ahead and get to writing
whaack: trinque: well fwiw I sincerely hope tmsr-os comes with a lisp over a python
trinque: not saying it shouldn't, but why do you hope that?
diana_coman: ahaha, by now I see that trinque will measure everything in multiples of busybox.
whaack: trinque: First, I find it more pleasant writing in lisp. Second, I like the cultural aspect of a (present day) more niche language. Then for problems with python: i find the single line lambdas a strange requirement, and not having tail call optimization is lame (although i admit i can't think of many/any cases where that's been a problem)
diana_coman: re paster though tbh this attempt (coming as it does on top of the previous mess with
python and its flask) left me looking again for not using either.
whaack: trinque: pasting chunks of python code is also a pain given the blocks-created-by-tabs design
diana_coman: whaack: wtf's "the cultural aspect of a (present day) more niche language" ?
trinque: nobody's defending python; I'm questioning the superiority of lisp for anything you might actually be doing on a regular basis.
trinque: all my tmsr work to date could've been php or pyshits for all the difference it would've made.
whaack: diana_coman: if i search for a piece of lisp code to do something, I have a (perhaps naive) belief that I am more likely to find something well written, since there are fewer people using the language
trinque: which is not just a bunch of bawww. it's worthwhile to question wtf we use to value things within which *whole lifetimes* can be lost, wasted.
trinque: whaack: starting at beliefs is going to be a shaky foundation, but fwiw I "believe" most folks writing lisp today are compulsive masturbators like gabriel_laddel
diana_coman: trinque: I'll take some more time to digest both the article and the comment.
ossabot: Logged on 2019-12-28 22:56:45 trinque: and jfw, dorion_road, if you don't see the word "Gales" in there, it's because I'm trying to disabuse you of the notion that there's such thing as a "Gales" which you made, by way of sheer numbers.