diana_coman: lobbes: it's been more of a not-try-the-idea-out but anyway, fine.
feedbot: http://younghands.club/2020/05/18/jfw-review-week-of-11-may-2020/ << Young Hands Club -- JFW review, week of 11 May 2020
diana_coman: jfw: the night-time review!
jfw: , the return of ~
diana_coman: maybe I really should change the name thus, it will surely sound at least way more exciting
diana_coman: so welcome back to the review then, indeed.
jfw bows, goes to get some sleep, plan will have to come tomorrow
diana_coman: sleep well
billymg: http://logs.ossasepia.com/log/ossasepia/2020-05-16#1026033 << i wouldn't mind taking a look, if anything just so i could try it out locally
ossabot: Logged on 2020-05-16 19:44:38 trinque: at any rate, jfw I already did the postgres port if you or billymg want it
billymg: if no one objects, the next patch will rip out js and whatever features depend on it. this will be similar in absolute terms (LOCs/bytes) to the first major round of trimming
diana_coman: billymg: from my point of view js can go without any trouble; the only possibly-useful feature requiring it and that I'm aware of was editing the url of an article from the gui; from my pov the main question though would be - how separate the js is from everything else in the code so as not to take out/break something entirely different, really.
jfw: imo if there's to be a web editor anyway, it needs to be able to do all editing tasks (such as that permalink editing), and there shouldn't be any 'dead widgets' (as there are when JS is simply disabled client-side). That's where it might get tricky, but dunno how bad.
diana_coman: http://ossasepia.com/2020/05/03/ossasepia-logs-for-may-2020/#1026044 - I do hope that pile of stuff glared back at you, jfw !
sonofawitch: 2020-05-17 02:49:50 (#ossasepia) jfw: http://ossasepia.com/2020/05/03/ossasepia-logs-for-may-2020/#1026033 - I'd love to have it, if only for safe keeping; and why not publish anyway since you did the work. (/me glares at own pile of unsung code...) That said, I'm not likely to test it any time soon and will probably end up moving toward "mysql all the things" unless a strong reason turns up
jfw: diana_coman: if it had eyes, it would have.
jfw: ftr, jfw finally barfs, as the saying goes.
snsabot: (therealbitcoin) 2020-05-18 jfw: Curious game, only way to win is...
diana_coman goes to read latest dramaz
diana_coman: lol, I didn't realise trb was alf-tech nao.
billymg: diana_coman, jfw: yes, this will be a surgical snip, not a simple `find ./mp-wp/ -iname "*.js" | xargs rm`
jfw: billymg: sounds good then!
jfw: diana_coman: see, trb is this temple built by lazy ignoramus shitoshi, and it stinks, why doesn't he come back and clean it up for us!
diana_coman: dorion: how's that balanced week/time going for you?
trinque: what happened to "there is no we, only V"
trinque: who gives a fuck who likes whom? write patches, if folks sign, or not, what
diana_coman: trinque: I don't think anyone proposed anywhere they would not do whatever code development they wanted to do anyway, or anything of the sort.
trinque: sure, I just said that, but in Texan
trinque: :D
diana_coman: trinque: lolz; fwiw though, there are precious few people actually publishing whatever it is they are doing.
jfw: 'Texan' - ah ok, I was scratching head. I certainly have no objections to anyone using or signing my patches!
diana_coman: trinque: and out of curiosity, why do you ask if people want it? as above, publish it if you made it anyway and don't intend otherwise to keep it private, no?
sonofawitch: 2020-05-17 00:20:31 (#ossasepia) trinque: at any rate, jfw I already did the postgres port if you or billymg want it
trinque: I try not to do the open-source "code hucked over wall" thing, but otherwise have no objection.
diana_coman: you mean you do code hucked within the walls but not over the walls? lol
diana_coman: (I'm genuinely curious, nothing more)
trinque: yeah, I have all manner of experiments laying here in there
trinque: *and
trinque: I published early on the cuntoo project, and that didn't seem to have worked.
diana_coman: and what's the cost/downside to publishing them even signed with hucked-shit-key ? honestly, I never ever regretted documenting even shit attempts
diana_coman: trinque: that sounds like you expected some specific "worked" and it wasn't that so "did not work"
diana_coman: I certainly tried it out and provided feedback; others too; you have it there and used it to support talks eg re tmsros or even why "not that way" ; so dunno - how "not worked"?
trinque: sure, got feedback, but it was too big an item to push by myself.
diana_coman: sure; what's that to do with publish/not publish though?
trinque: I suppose we differ on whether a person that publishes "wp ported to postgres" that doesn't actually work has done something useful?
trinque: I personally would feel obligated to make it work if I published.
trinque: which is the right pressure for the right item, but not that one.
trinque: brb
diana_coman: trinque: uhm, why; publish it as "this is my shit attempt that does not work; but I explored this and that and learnt *why* it's not worth it"; listen, there's way more to learn from a published stuff than the "will grab this and it works"
trinque: so maybe there's also some narcissism in there too.
diana_coman: and as for everything else there is that part where it's *not possible* to tell upfront in *what way* it will turn out useful.
diana_coman: possibly; the thing is that the way it looks, you lock yourself into such a narrow thing that indeed, there's very, very little that can get out; honestly, it's not a problem in any possible way for me; I just fail to see how it's useful in the least for you, that's all.
trinque: some works take a long time.
trinque: for example the one I'm working on as a continuation of the OS thread
diana_coman: yes; and there's no need to publish-only-at-the-end; (fwiw I was never naturally "write and publish"; hell, not even naturally "talk")