← | Results 5751 ... 6000 found in all logged channels for 'f:diana' | →
(ossasepia) diana_coman: lobbes: read it; what happened to the mp-wp polish idea as it seems entirely dropped?
(ossasepia) diana_coman: billymg: sure and if you publish some plan, I'll certainly read it.
(ossasepia) diana_coman: lobbes: btw, if you publish your plan, we can start with that later today.
(ossasepia) diana_coman: I need to go now but I'll be back in ~1.5 hours or so.
(ossasepia) diana_coman: something like that; if it turns out it's useful.
(ossasepia) diana_coman: yeah, no need for more than that really; and it has this advantage that I see that one can in principle update the text too to list there for each line the links to comments that refer it (basically the non-js automated inline annotations if you want)
(ossasepia) diana_coman: billymg: yes, exactly.
(ossasepia) diana_coman: billymg: I meant an anchor for each line of code; but come to think of it, there's in principle already the selection mechanism, might even be enough, hm.
(ossasepia) diana_coman: my potential suggestion - but more of an idea for laters, if needed - was to have it work backwards as well ie when a comment is approved, to collect the ref to any line-html hook and then update to add there a link to the comment; it might be overkill, not needed anyway, I don't really know atm, just throwing it out there.
(ossasepia) diana_coman: billymg: perhaps the [[]] can simply add html hooks for each line and then commenters can use those, right?
(ossasepia) diana_coman: so certainly not parsing post_content, no.
(ossasepia) diana_coman: ... anything,even just parts of a vpatch at the end of the day, even not yet signed vpatch etc)
(ossasepia) diana_coman: billymg: the .vpatch file + the .sig file surely need of course to be standalone files too, there was no idea of NOT having them separate too; just NOT mixing the two at all: there's .vpatch files and those are indexed by the code shelf (which is singular because it's meant as one single entry point) and then there is - to the extent the author makes/wants it- a bunch of articles that discuss vpatch contents (and this can be ...
(ossasepia) diana_coman: billymg: sure.
(ossasepia) diana_coman: and uhm, I'd much, much rather have *no* JS whatsoever.
(ossasepia) diana_coman: not sure I see the case for extending that sort of situation.
(ossasepia) diana_coman: aka you end up with that situation where the content of your article is partially in db and partially on disk; it's already rather annoying that this is the case to some extent for wp (eg categories iirc and at any rate, images...)
(ossasepia) diana_coman: the additional potential trouble that I see if you go the route of having [[]] take directly the vpatch from disk rather than its text is that any annotations you add inline to it would then be separated from the text?
(ossasepia) diana_coman: billymg: you might have made for yourself 2 pieces of work ([[]] + shelf mgm) instead of 1, heh.
(ossasepia) diana_coman: and also: what's the separation you see between code and article content? the way I see it, for some code review, the code may very well *be* the article content, no? and the reviews are the comments, naturally.
(ossasepia) diana_coman: but otoh why mix it with the discussion /review of code (since perhaps I even want to discuss some vpatch *before*/without adding it yet to my shelf for instance?)
(ossasepia) diana_coman: billymg: on one hand I can see the appeal of having mp-wp basically maintain the code shelf as simply an automatically updated page with all vpatch+sigs uploaded, sure
(ossasepia) diana_coman: trinque: would you care to add your view/ideas on this thread?
(ossasepia) diana_coman: billymg: also, why wouldn't it work well anyway? not like there aren't otherwise articles of thousands of words published fine with mp-wp?
(ossasepia) diana_coman: maybe it's for the better if this even *forces* one to split the damned thing.
(ossasepia) diana_coman: because also, who the fuck reads thousand+ line vpatch?
(ossasepia) diana_coman: I know we still end up with those but ...they *are* trouble so I wouldn't base the viewer on them.
(ossasepia) diana_coman: billymg: very large vpatches are a bit of trouble in themselves
(ossasepia) diana_coman: ie you risk overspecifying/making choices too quickly/before knowing the problem really
(ossasepia) diana_coman: but tbh I think this is one of the situations where it's perhaps better to wait and see what is actually *needed* because it's unclear to me that at this stage, before any serious use, one can fully tell really
(ossasepia) diana_coman: billymg: re inline comments - would it be possible for the plugin to update the article's content to provide perhaps inline links to the relevant comments or something of this sort?
(ossasepia) diana_coman: I wouldn't really go otherwise much along the slippery path of "automate a vpatch's lifecycle" because of the fundamental of V that *reading* is authorship of code (and that can't be automated really).
(ossasepia) diana_coman: if/when there's a new version of the vpatch, it's up to whoever *signs* the new vpatch to publish it as a new article, no?
(ossasepia) diana_coman: and then the comments to the post can simply reference that
(ossasepia) diana_coman: all it needs is this new tag+corresponding plugin to do the formatting (perhaps similar to that vpatch viewer, sure)
(ossasepia) diana_coman: I think the whole viewing + reviewing can happen perfectly fine on the existing blog article structure, can't it?
(ossasepia) diana_coman: for the text/article itself though, why not make it simply a different type of tag? e.g. like one has (()) for footnotes, use [[]] or something else for "this is vpatch content"?
(ossasepia) diana_coman: the upload vpatch + store in sensible place is really a script that can even be outside mp-wp, not much to do with the mp-wp itself
(ossasepia) diana_coman: billymg: there might be 2 parts to it and not even necessarily tied together really
(trilema) diana_coman: http://logs.ossasepia.com/log/trilema/2020-01-05#1956629 - this is very much so as far as I have seen/heard it/even had it explained to me in as much detail as I could listen to, over and over again.
(trilema) diana_coman: sure, no argument there either; it is how the whole pile ends up that big and stinky and intricate, after all.
(trilema) diana_coman: sure, inconsistent and annoying, there's no argument there.
(trilema) diana_coman: mircea_popescu: the = vs == is because of the confusion assignment vs comparison
(ossasepia) diana_coman: billymg: since you've been working on mp-wp anyway, what would your thoughts be on a mp-wp plugin for vpatches display+review? As hinted a bit earlier around here.
(ossasepia) diana_coman: whaack: in any case, 7 will have to do for the pilot test, so at least there's that.
(ossasepia) diana_coman: lobbes: re your search for bugs, the whole discussion can easily go through CS, Maths, Logics and Philosophy in a single paragraph too, lol; might fit better in a conversation or as an article if you want to look at that bit in more depth.
(ossasepia) diana_coman: I can imagine.
(ossasepia) diana_coman: as in "working with Minsky"; but myeah.
(ossasepia) diana_coman: and the sane retort to what I suspect is his different background simply rather than much more than that would have been that ahem, you can also learn to use $1 mil lathe on your employer's money later on as needed but you'll never get access again to far more valuable resources such as Minsky,
(ossasepia) diana_coman: btw the moment one says that "you'll learn X on your own time", that *means* the curriculum is bad; because if you can indeed learn it just the same on your own time then sure, wtf "university"
(ossasepia) diana_coman: ah, so ~the mech eng is not fashionable enough and lathe is not lisp.
(ossasepia) diana_coman: (normally there would have been a retort to that "point" of your advisor but possibly not by that time anymore so they were right either because they knew CS well enough or because they didn't know it well enough, lol)
(ossasepia) diana_coman: good point really; so... why didn't you?
(ossasepia) diana_coman: "against it" is easier than "for it", lolz.
(ossasepia) diana_coman: whaack: what did they advise for?
(ossasepia) diana_coman: whaack: anyways, I guess I still haven't fully grokked the current MIT; don't take it to heart.
(ossasepia) diana_coman: ahahaha; why not "nuts and bolts that java holds"
(ossasepia) diana_coman: ie by the name it actually intended to teach something other than a language; and otherwise hm, no..introductory programming course or something lower level (that I could see focusing on how-to-x-language)?
(ossasepia) diana_coman: whaack: software system design means > how-to-any-language
(ossasepia) diana_coman: so then programming language class was what?
(ossasepia) diana_coman: whaack: there is some space and even need for incremental, sure, but it's not all-there-is.
(ossasepia) diana_coman: whaack: anyway, if you have a use case for those UUIDs, you should have argued it and kept them in; if you don't, then they are not in.
(ossasepia) diana_coman: whaack: hm, did that MIT ever mention development methodologies at all? lolz
(ossasepia) diana_coman: whaack: anyway, each chan should be in a single db though, right? I don't see why would a single chan end up split across several dbs so not sure there's much actual trouble merging otherwise.
(ossasepia) diana_coman: blind & undocumented*
(ossasepia) diana_coman: don't attempt to build the whole thing out of incremental blind adjustments; it'll end up a mess quite predictably.
(ossasepia) diana_coman: whaack: you need to produce first a clear report re all those numbers, you know? what decision can one make on this sort of shaky sands of there-is-this-limit and that-limit but dunno exactly .
(ossasepia) diana_coman: yes, renumbering is a bitch; otoh database design has anyway some tensions as soon as the whole thing is worth anything so I doubt there's a one/single/ideal/perfect solution there.
(ossasepia) diana_coman: anyways, I was honestly curious as to why you chose that (and I hadn't caught /recalled what you said re log-line by foreign-key ref http://logs.ossasepia.com/log/ossasepia/2020-01-03#1014544 )
(ossasepia) diana_coman: the way I see it, as long as it's one db, might as well go with auto-increment since there's no loss as such; if/when mixing dbs, can identify same/different via a hash and otherwise if/when needed add perhaps another level of ref (e.g. provenance ) or otherwise still just calc and add hash at that time
(ossasepia) diana_coman: UUIDs otoh are useful precisely for identifiers though one can argue that you can always calculate on the fly some hash
(ossasepia) diana_coman: trinque: exactly; and this matters for log lines because timestamp is such a mess that you can't rely on it.
(ossasepia) diana_coman: I just think that both UUIDs and PIDs are needed because they serve different purpose really
(ossasepia) diana_coman: trinque: I didn't say they were a waste a space, no; and ftr I can state it also: no, they are not a waste of space.
(ossasepia) diana_coman: whaack: aha, no need to keep that in memory really, no.
(trilema) diana_coman: fixed aka added the links to the text I cite in the article; the archive copy you provide is also useful as it further adds the refs on tarabostes.
(trilema) diana_coman: so I'll fix that in a minute.
(trilema) diana_coman: re links from the logs, I should have added the content properly formatted with links included, indeed.
(trilema) diana_coman: mircea_popescu: your comment seems to have gotten somehow mangled and/or truncated (it has a part that repeats)?
(trilema) diana_coman: alternatively, it may also be that they simply take the words/expressions (word salad) (because ...well, they work, right?) and then they proceed to use them as it seems to them that it "should" be; (I kind of got to see this in action with that shrysr guy).
(trilema) diana_coman: mircea_popescu: that's why I find it funny; precisely because of this "it's so much further away than that, that we'll call it ...that; a sort of heat seeming cold and the other way around.
(trilema) diana_coman: I found it funnier re "trilema.com is word salad" tbh; I'm not sure there's much more to it than that though, not even sure what would "persuasive" mean in their context, exactly.
(ossasepia) diana_coman: dorion_road: oh hey, sounds good; though on the article front, dunno, does it beat hunting then or what?
(trilema) diana_coman: lolz; I'll go to see to the child for a bit.
(trilema) diana_coman: yeah, it's not ..the first time.
(trilema) diana_coman: ahahah, I can see that.
(trilema) diana_coman: heh, might end up triggering more discussion but at least I got something out of those days' reading & mulling.
(trilema) diana_coman: mircea_popescu: ^ is my current answer for that a) vs b) choice.
(ossasepia) diana_coman: http://logs.ossasepia.com/log/ossasepia/2020-01-03#1014544 - I can see that; otoh though, how would you order them? I can see the case perhaps for both UUIDs and pids but having just one still keeps a set of problems around.
(ossasepia) diana_coman: whaack: well, a test of sorts it sounds like, at least; that out of memory thing sounds gross though.
(ossasepia) diana_coman: lobbes: well, I was very young indeed (about 15-20 pretty much); looking back at it, I'd say that philosopher guy I mention in the comment had seen something ie it was a combination of "hah, I'll make my OWN if I need one, thank you very much" + they'll talk of everything and do nothing + some idiots as "teachers" of the subject in school (+ possibly more tbh).
(ossasepia) diana_coman: basically I spent quite a lot of years considering all philosophers idiots :D
(ossasepia) diana_coman: lobbes: but re Kant, I asked because on reflection, initially I hadn't included you in the recommendation for Popper mainly because I thought you were quite likely to enjoy Kant possibly even more.
(ossasepia) diana_coman: well, let me translate for you and the logs, this tidbit that might shed some light on my take on philosophy overall so what I say on it gets a bit of context too: I was once before sworn at by a philosopher as he said I was a philosopher myself.
(ossasepia) diana_coman: lobbes: did you enjoy Kant though?
(ossasepia) diana_coman: lobbes: heh, if you also add the requirement to read them in original, certainly; and that's precisely how one gets both very happy ("will never run out of stuff to do!!!") and totally useless (will *also* never get to *do* anything either)
(ossasepia) diana_coman: that is 1; then reading is re-reading is 2; and usually one needs at least 3 passes to fully get something so that's 3 and we'll stop there as it's quite enough anyway.
(ossasepia) diana_coman: lobbes: sure, you could in principle go at it historically ie start with the ancients and work your way as they did; it makes for a fun project but I wouldn't call it a very practical approach tbh.
(ossasepia) diana_coman: lobbes: yes re chewing and also keep in mind that first read is just that - the *first* read, not like you have to attempt the impossible task of "getting everything from this one read"
(trilema) diana_coman: basically timestamps have always been a total mess.
(trilema) diana_coman: and ends with 1 bc so ...
(trilema) diana_coman: iirc not even later actually ie it starts with 1 ad
(trilema) diana_coman: they didn't have 0 a.d. at *that time* though, did they?
(ossasepia) diana_coman: fwiw (and iirc) I think I read first his essays (grouped I think in "in search of a better world") - kind of made me want to listen to what he had to say; the open society and its enemies draws upon a lot of references so on one hand it can be overwhelming if you have no idea of those references, on the other hand you could perhaps use it as a starting point to learn about those too.
(ossasepia) diana_coman: lobbes: he's very readable and quite enjoyable really in ~all I read; the trouble with starting points is that they make sense or not depending on what you already have (or not); otoh, one starts wherever one can anyway, so there isn't any "wrong" starting point either.
(trilema) diana_coman: lobbes: technically new decade starts with 2021, doesn't it?
(ossasepia) diana_coman: I somehow rather doubt there's any danger of overflowing the data type there + if it's at that, there's potential trouble in theory with random hexes too via clash.
(ossasepia) diana_coman: whaack: just add an auto-incrementing id to the table and the dbms will do the rest for you.
(ossasepia) diana_coman: ah, huh; I can't see a reason for that; trinque , why did you use random hexes as unique ids for each log line in db?
(ossasepia) diana_coman: uhm, why random hexes?
(ossasepia) diana_coman: whaack: I don't recall how much xp you have with sql/similar/db.
(ossasepia) diana_coman: whaack: so myeah, not very helpful to then mess up the sequence of message ids by inserting those non-messages in there.
(ossasepia) diana_coman: whaack: basically your fleetbot messages belong in a table of their own and you can always do a join, dbms is good at that; have it log chan id or whatever for link + timestamp or something.
(ossasepia) diana_coman: (in turn, this can further complicate the trouble when you start inserting in there non-message messages); like all design, db design will end up quite a mess if you "just do it".
(ossasepia) diana_coman: whaack: also, the ordering is usually saner by id of message rather than the timestamp which can easily run in all sorts of trouble; is there an id per line?
(ossasepia) diana_coman: so yeah, that "have to fill this which has no meaning" is precisely the flag of your abuse.
(ossasepia) diana_coman: whaack: strictly speaking, you are indeed abusing the log table there since the fleetbot "messages" are not irc messages, are they?
(ossasepia) diana_coman: whaack: the DB has default values, use them; this being said, the fact that you find yourself in the situation where you need to fill in fields that have no meaning for some rows is essentially a sign that you are stuffing in there what doesn't quite belong; whether it's a problem or not, it depends.
(ossasepia) diana_coman: whaack: in general: do NOT blindly overload existing parts with whatever new meaning you happen to need on the spot, it's unsanitary, quite disgusting and the start of one full set of clusterfucks.
(ossasepia) diana_coman: and moreover, it IS the sane approach there, what; no 127.0.0.1, why would you even think of that?
(ossasepia) diana_coman: whaack: neah, add the category column; you need it *anyway*, see http://logs.ossasepia.com/log/ossasepia/2019-12-31#1014347
(ossasepia) diana_coman: it's a different category and you need categories anyway so supposedly there's already a column for that, isn't there?
(ossasepia) diana_coman: whaack: what do you mean by magic values?
(ossasepia) diana_coman: sure, you should ask for the papers anyway.
(ossasepia) diana_coman: whaack: did they actually give you any papers for that "garantia"? and even if papers - what exactly are they worth? will they replace the part if it's faulty or what? (I can imagine how that would go,lolz)
(ossasepia) diana_coman: quite possibly or for that matter even "lost/dropped as unimportant the accessories" wouldn't surprise me much; but at the end of the day, this sort of details really don't matter, as the mess is still the mess, there's not much point to differentiating now between flavours of mess based on...intentions or something.
(ossasepia) diana_coman: dorion_road: how's the cruise?
(ossasepia) diana_coman: whaack: hopefully you get the test at least started so it can have a run over the next 2 weeks when it seems you'll not have much time on this.
(ossasepia) diana_coman: lobbes: wb, hope you had a refreshing break.
(trilema) diana_coman: neither qntra.net nor thewhet.net load from here.
(ossasepia) diana_coman: whaack: more to the point, remember that basic part of being able to undo/redo? It *includes* a properly documented disassemble phase if that's your starting point; as in: disassembling happens with pen and paper at hand, parts get noted down and have their storage place; there's little more frustrating than ending up with "can't find a screw" or whatevers.
(ossasepia) diana_coman: or so you... hope; not like you can actually tell.
(ossasepia) diana_coman: whaack: the next question being of course: did you at least... count the parts? or you'll end up with a few remaining outside after you close the case, lolz.
(ossasepia) diana_coman: whaack: myeah, meaning your full plan is not a plan just like the disassembling process was probably more of an accident than a process and so on.
(ossasepia) diana_coman: ah, hope, that thing to hold on to for dire lack of anything else.
(ossasepia) diana_coman: (why and with what results should be in the notes too)
(ossasepia) diana_coman: do you have also notes re what you did on which day and how long it took?
(ossasepia) diana_coman: whaack: did you take photos?
(ossasepia) diana_coman: do you have some clear idea of all the steps required and why/how you choose "what next"? what are the parts and where they go and why and all that?
(ossasepia) diana_coman: whaack: uhm, so yesterday the few hours were to clean the paste, today a few more hours to screw the mobo in and tomorrow a few more hours to... put the drives in, or what?
(ossasepia) diana_coman: right; the bigger plan though?
(ossasepia) diana_coman: whaack: what's the plan+status on your computer?
(ossasepia) diana_coman: whaack: I guess you can call this ordering stuff through pcgamingcr a truly multi-learning experience then.
(ossasepia) diana_coman: whaack: what a mess of a day indeed.
(ossasepia) diana_coman: whaack: sounds ok.
(ossasepia) diana_coman: dorion_road: aren't those/the other < normally handled by jfw's script? ie did you just find a bug in jfw's script in fact?
(ossasepia) diana_coman: BingoBoingo: sadly no; it's only logs.minigame.biz that lobbes handles and so it's up.
(ossasepia) diana_coman: whaack: ahaha; yes, it's okay if you get to it tomorrow, no worries.
(ossasepia) diana_coman: whaack: ok; possibly "next year" even, no hurry.
(ossasepia) diana_coman: whaack: so...don't; hence - discuss/ask/talk, do NOT spin.
(ossasepia) diana_coman: heh, good; but yeah, that's what they say and why I said you should have at least explicitly stated that you need more time to consider the other points.
(ossasepia) diana_coman: basically "the rest is not worth my time" then?
(ossasepia) diana_coman: whaack: heh; did it take then more than alloted and so you cut out parts or how does this even work?
(ossasepia) diana_coman: you can always ack the point(s) otherwise and note you'll need to think it some more or something but even better maybe discuss it instead of just spinning around it.
(ossasepia) diana_coman: whaack: why the delay anyway?
(ossasepia) diana_coman: also, you glossed over/chose only some parts to answer to in that comment, lol.
(ossasepia) diana_coman: whaack: do select your sources better, really; that "definition" of codependency is worse than useless really; the first part is microsoft-style and the 2nd part reads more like a confusion than a definition; the core of it is the enabling of one's faults (hence the previous clue re don't use tmsr as a crutch)
(ossasepia) diana_coman: whaack: yes; and monitor it's run for at least several days/ a week, it's basically a first chance to get some idea of the practical issues; atm it's even unclear how much data you'll get for instance (and I expect that's anyway going to end up on some power law basically but still); test run indeed.
(ossasepia) diana_coman: but it can give I suppose an idea of just how much of the whole imagined "activity" is nothing more than ...automated processes basically.
(ossasepia) diana_coman: I'd rather it did; ideally marked as a different category (so you can filter them out/in later, at analysis time)
(ossasepia) diana_coman: whaack: does the bot log the join/parts too?
(ossasepia) diana_coman: whaack: also re "silence", do notice that it might be due to the holidays time to some extent; it is New Year's Eve, after all.
(ossasepia) diana_coman: whaack: that can also wait though; first make at the very least a "test run" that fully works and you know what's going on in there.
(ossasepia) diana_coman: sounds sensible, yes.
(ossasepia) diana_coman: all right; but it can wait.
(ossasepia) diana_coman: it's just too many to leave it at that; one way or another it needs looked into; can still wait since there's a whole lot otherwise to get started on those you could connect to, but you can't say "they don't exist, netsplit.de is wrong" just on what you have so far; leave them for now in "??? category" perhaps, for laters.
(ossasepia) diana_coman: well, at least it's funny.
(ossasepia) diana_coman: it seems rather too large a chunk to be just bogus although it's not impossible nowadays either.
(ossasepia) diana_coman: whaack: did you even spot-check those to see if it's perhaps just your bot(s)?
(ossasepia) diana_coman: whaack: btw this is NOT programming ffs, it's monkeying at the keyboard, ugh.
(ossasepia) diana_coman: whaack: lolz, quite the difference there; how come? and are there in the end ~500 networks and you're missing ~300 or are there simply ~200 total or what?
(ossasepia) diana_coman: whaack: well, spill over is spill over, yes.
(trilema) diana_coman: also, mind adding those very useful widgets for last articles and last comments? please?
(trilema) diana_coman: trinque: why does your blog send me to an empty page after I give it a comment? It's quite confusing/initially I thought it failed to eat it and I was just about to try again.
(ossasepia) diana_coman: http://logs.ossasepia.com/log/ossasepia/2019-12-30#1014311 - heh, this sounds like you need a whole lot more experience to end up with the wisdom to simplify your own workbench.
(trilema) diana_coman: mircea_popescu's first time.
(trilema) diana_coman: lolz; I was about to say that compared to further trying to get sense out of cs entrails, just about ~anything else qualifies for happy.
(trilema) diana_coman: happiness is such a relative thing, lol.
(trilema) diana_coman: ahaha, no, it's just several passes.
(trilema) diana_coman: at any rate, I'll take some days to (mull & read)*
(trilema) diana_coman: ok; worth noting that the "piped into" part might itself be quite involved / will depend on what's exactly in that pile from a/b.
(trilema) diana_coman: what are the steps going to be re "graphics on client side"?
(trilema) diana_coman: mircea_popescu: what about cs/ps anyway? ie graphics as "how & what to store" is one thing; there is still at all times some sort of "how to get from data to pretty pics/animations/etc"
(trilema) diana_coman: certainly I meant for "it can take forever"
(trilema) diana_coman: certainly; and part of why I'm not all-that-enthusiastic about it; otoh my current experience with ~equivalent of a make me also-not-that-enthusiastic; so I'm looking at "choice".
(trilema) diana_coman: I didn't keep track but I do recall at least a few off the top of my head, yes.
(trilema) diana_coman: http://logs.ossasepia.com/log/trilema/2019-12-30#1956451 - pretty much b then, for so much "choice" , huh.
(trilema) diana_coman: myeah; that basically says "you'll have to build up the people too so..."
(trilema) diana_coman: the thing with the AI/automated generation was initially that "can't beat human at this sort of task" iirc.
(trilema) diana_coman: if you mean "art products" by that everything that's conceivably useful then yes, indeed, I was thinking precisely of that rather sad attempt, hm; the idea -naive!- behind that to my mind was more to find perhaps as a result *people* doing something useful in that direction, hm.
(trilema) diana_coman: and no, I wouldn't start making another blender, ugh.
(trilema) diana_coman: re maintaining the infrastructure, I don't see how it can be really justified as such anyway given that uhm, those doing something with it are anyway essentially non-existent currently so can't maintain so they "do" anything; and if it is to *also* build them up, then well, they'll fit whatever infrastructure is provided, not the other way around.
(trilema) diana_coman: mircea_popescu: I had the article on the toolchain to help her as I knew she was having a go at it based on some discussion in #eulora I think; maybe that?
(trilema) diana_coman saw this coming
(trilema) diana_coman: ahaha, sure.
(trilema) diana_coman: ah, I see; yes.
(trilema) diana_coman: that yes, I do; though I am partial to an sukhoi more than to an AI because at least it's a concrete beast I guess.
(trilema) diana_coman: as above, it's negative value, below that "not much" for the sukhoi.
(trilema) diana_coman: rather: unclear what *useful* thing it does
(trilema) diana_coman: what, for buying an AI system that is "very powerful" when ran through the proprietary bundle & otherwise unclear what it does?
(trilema) diana_coman: lolz; and pretty light patterns possibly.
(trilema) diana_coman: myeah; I fell in love with it at 17 (when read the promise) and then promptly barfed by 19 (when encountered the full extent of the "practice")
(trilema) diana_coman: oh huh, only one? dunno, perhaps the idea is to reverse engineer, that might be about the only possible value I can see but it's dubious for all sorts of reasons.
(trilema) diana_coman: if you are asking "what is this item worth to *you*", well, not much; the fuck do I do with this sukhoi.
(trilema) diana_coman: because "what this item is worth" depends on more than just the item in itself and I have no idea even on the item really, let alone the context.
(trilema) diana_coman: ugh, this seems out of my advising capabilities really.
(trilema) diana_coman: the sort of accumulating accidental complexity, to link it in with trinque's thread re OS.
(trilema) diana_coman: hm; I keep thinking that "perhaps I don't know enough about them to find the value" ; as I see them now, they are more accumulations of trial and error/overfitting/tinkering though so they seem of very little - or indeed negative - value tbh.
(trilema) diana_coman: oh boy, I'm possibly the last person to ask for an argument pro "valuable" on those.
(trilema) diana_coman: mircea_popescu: hm, thinking now about it, I think there might be, namely the more directly game-relevant parts that are also not yet fully spec (eg character, structure/item etc); I need to go over it in this light, put the graphics to the side for now and see from there.
(trilema) diana_coman: mircea_popescu: yes.
(ossasepia) diana_coman: whaack: now the question is whether the reason you find it more pleasant writing in lisp is precisely because it feeds those bad habits, you know?
(ossasepia) diana_coman: the point with using trinque's bot to start with was precisely to not end up with repeated 12h+ days on this but I suspect you have some very inefficient habits either programming in general or unknown language specifically.
(ossasepia) diana_coman: whaack: note that testing something is *not* going to do a whole lot re understanding that something, esp not by itself; there are quite a few layers on this, hm.
(ossasepia) diana_coman: whaack: that's exactly what it sounded like, indeed; and your statement yesterday re looking for code doing this or that was also a red flag.
(ossasepia) diana_coman: well yes, that's what it suggested and part of why I asked the question.
(ossasepia) diana_coman: so neither of your guesses there, really :)
(ossasepia) diana_coman: whaack: I'm asking what took 12h+ and why is it a grind?
(ossasepia) diana_coman: whaack: what/why is the work on this so far eating that much time? It seems rather excessive from here.
(trilema) diana_coman: mircea_popescu: answered.
(trilema) diana_coman: oh; I was blissfully unaware of the extent of xml-shading, lolz.
(trilema) diana_coman: so dunno, maybe I don't fully get what you have in mind re "fuck ints"?
(trilema) diana_coman: mircea_popescu: here?
(trilema) diana_coman: mircea_popescu: tbh re ints I recall an article on trilema.com - if I can find it now, hm.
(trilema) diana_coman: fwiw I went there because of a former friend who kept pulling at me about it; nothing to do with stanca really, never even talked to him ever.
(trilema) diana_coman: ahahah; that was one of those things where "at least I figure it out quickly enough", lolz
(trilema) diana_coman: well, technically it was first the move to int64 and then the rest but practically they still overlapped to some degree and the similar pains etc.
(trilema) diana_coman: hm, in my memory the int64 kind of merges with eviscerating the gem mess out of the server
(trilema) diana_coman: mircea_popescu: that's not possible as the only "old blog not moved" is that thing on wordpress.org that dates from...uhm, 2009/10 ?
(trilema) diana_coman: hmmmm, let me see but I think it was just a mention in one of those open sores rants
(trilema) diana_coman: mircea_popescu: do you mean the move to int64?
(ossasepia) diana_coman: http://logs.ossasepia.com/log/ossasepia/2019-12-30#1014283 - what tends to be the range for those num-chans-per-nick and max-conn-per-host ?
(ossasepia) diana_coman: btw, you might want to use a html validator as it will point out unclosed tags and other such things that tend to end up in weird errors.
← | →
Download hourly DB snapshot | Get Source Code