From: Lucian Mogosanu Date: Wed, 4 Sep 2019 15:19:44 +0000 (+0300) Subject: posts: 09e X-Git-Url: https://git.mogosanu.ro/?a=commitdiff_plain;h=c479ec7aa245a7be08c7df9da83b853eb3dea124;p=thetarpit.git posts: 09e --- diff --git a/drafts/000-tmsr-work-v.markdown b/drafts/000-tmsr-work-v.markdown deleted file mode 100644 index 7675739..0000000 --- a/drafts/000-tmsr-work-v.markdown +++ /dev/null @@ -1,101 +0,0 @@ ---- -postid: 000 -title: TMSR work: plan for 2019 M9 -date: September 4, 2019 -author: Lucian Mogoșanu -tags: tmsr ---- - -(By the way, methinks that the "TMSR" bit is somewhat redundant -- -it's not like "meanwhile dead [ex-TMSR][citadel] work", or "TSIE work" -is anywhere on the horizon.) - -This July resulted mostly in Hunchentoot code reviews: -[taskmasters][hunchentoot-v]; [requests and replies][hunchentoot-via]; -and [a continuation][hunchentoot-vib] of that one. So I ate and -documented more than 90% of the thing and I'm ready to use it in the -battlefield with the reasonable certainty that it won't fall apart at -the first prod. - -Before writing down the plan for this month, let's look at the stuff -that burns: - -* this blog needs a [comment mechanism][ttp-comments]; -* all this Hunchentoot review work means nothing without a genesis; -* #trilema and other castles require a [fleet of loggers][logging] to - keep things running; and -* feedbot has some new patches that [need to be merged][feedbot] into - the current working tree. - -And as for the stuff that isn't (yet!) burning but is still important: - -* [file pastebin][pastebin]; -* there's been some recent discussion of [Adalisp][adalisp], which is - still in need of a review and further work to be made usable; -* I want to review [older Lisp works][lispwork], how else to even know - if something better is possible? -* eventually I'll want to steal and review all potential Lisp - infrastructure, to determine once and for all whether this Common - Lisp orchestra is actually worth maintaining or it's to be thrown - out of the window, or what; -* I still haven't genesized The Tar Pit; by the way, is there anyone - else out there interested in using it? -* I still haven't run a [Cuntoo][cuntoo] to this day, y'know; -* there's [a ton of other][work-ii] work there; I'm not sure how much - of this I'm going to finish during this lifetime, so at some point - I'll just sit down and re-prioritize. - -Having said this, the more detailed plan for the short term is: - -* Week **36**: genesize Hunchentoot and [everything - else][sbcl-and-others] required to run it, save for the operating - system. -* Weeks **37**-**38**: implement The Tar Pit comments and publish said - coad[^1]. -* Weeks **39**-**40**: read [Stan's logger][snsabot]; stand up a - [Logbot][botworks]; write a minimal WWW frontend that takes items - from the logotron database and renders them; publish that. - -And I could go on with this list up to week 50 maybe, but let's see -how the current items go first, then we'll get back to it. - -[^1]: I actually have this broken down into pieces, let's look at it. - - First, the posts need to be indexed somehow in some kind of - database, so that the blogotron knows how to retrieve the content - and the comments for it and render everything into a page. I don't - care about the database backend, the code that does this should be - attachable to any type you like with minimal glue. - - Then, I'll need to make some modifications to the blog itself, so - that it knows that such thing as "comments" exist and can be - retrieved from said database and rendered. This includes page - layout modifications as well as backend scaffolding for getting - comments and inserting them below the post. - - Finally, there's supposed to be a way to post comments, à la - Wordpress' wp-comments-post.php. Additionally, this should come - with anti-spam support built-in, but... well, did you see the - "stuff that's burning" list? I'll patch that wound when (yeah, - when, not if) it starts burning. Until then, I guess all comments - are to go to the moderation list, or I'll whitelist IPs or - whatever. - - Oh, and by the way, I should also implement server-side selection - for this thing at some point. - -[citadel]: /posts/y04/068-the-story-of-the-citadel.html -[hunchentoot-v]: /posts/y06/09b-hunchentoot-v.html -[hunchentoot-via]: /posts/y06/09c-hunchentoot-via.html -[hunchentoot-vib]: TODO -[ttp-comments]: /posts/y06/099-tmsr-work-iv.html#selection-176.0-176.3 -[logging]: /posts/y06/099-tmsr-work-iv.html#selection-160.0-160.7 -[feedbot]: http://logs.nosuchlabs.com/log/trilema/2019-08-23#1930279 -[pastebin]: /posts/y06/099-tmsr-work-iv.html#selection-238.0-238.7 -[adalisp]: http://logs.nosuchlabs.com/log/trilema/2019-08-30#1932159 -[lispwork]: /posts/y06/099-tmsr-work-iv.html#selection-208.0-208.13 -[cuntoo]: http://trinque.org/2018/11/27/cuntoo-bootstrapper/ -[work-ii]: /posts/y05/090-tmsr-work-ii.html -[sbcl-and-others]: http://logs.nosuchlabs.com/log/trilema/2019-08-30#1932154 -[snsabot]: http://www.loper-os.org/?p=3452 -[botworks]: /posts/y05/080-botworks-regrind.html diff --git a/posts/y06/09e-tmsr-work-v.markdown b/posts/y06/09e-tmsr-work-v.markdown new file mode 100644 index 0000000..90b1adf --- /dev/null +++ b/posts/y06/09e-tmsr-work-v.markdown @@ -0,0 +1,124 @@ +--- +postid: 09e +title: TMSR work: plan for 2019 M9, and a very brief discussion +date: September 4, 2019 +author: Lucian Mogoșanu +tags: tmsr +--- + +(By the way, methinks that the "TMSR" bit is somewhat redundant -- +it's not like "meanwhile dead [ex-TMSR][citadel] work", or "TSIE work" +is anywhere on the horizon.) + +This July resulted mostly in Hunchentoot code reviews: +[taskmasters][hunchentoot-v]; [requests and replies][hunchentoot-via]; +and [a continuation][hunchentoot-vib] of that one. So I ate and +documented more than 90% of the thing and I'm ready to use it in the +battlefield with the reasonable certainty that it won't fall apart at +the first prod. + +As for the future: at the beginning of this week I had a todo list, +and it looked like this. First, the stuff that burns: + +> * this blog needs a [comment mechanism][ttp-comments]; +> * all this Hunchentoot review work means nothing without a genesis; +> * \#trilema and other castles require a [fleet of loggers][logging] +> to keep things running; and +> * feedbot has some new patches that [need to be merged][feedbot] +> into the current working tree. + +And as for the stuff that isn't (or wasn't) burning (yet I still found +important): + +> * [file pastebin][pastebin]; +> * there's been some recent discussion of [Adalisp][adalisp], which +> is still in need of a review and further work to be made usable; +> * I want to review [older Lisp works][lispwork], how else to even +> know if something "better" is possible? +> * eventually I'll want to steal and review all actual and potential +> Lisp infrastructure; +> * I still haven't genesized The Tar Pit; by the way, is there anyone +> else out there interested in using it? +> * I still haven't run a [Cuntoo][cuntoo] to this day, y'know; +> * there's [a ton of other][work-ii] work there; I'm not sure how +> much of this I'm going to finish during this lifetime, so at some +> point I'll just sit down and re-prioritize. + +I also had a plan for the following few weeks in fact more than that, +but plans tend to change along the way. Anyway, the short-term plan, +word for word, was: + +* Week **36**: genesize Hunchentoot and [everything + else][sbcl-and-others] required to run it, save for the operating + system. +* Weeks **37**-**38**: implement The Tar Pit comments and publish said + coad[^1]. +* Weeks **39**-**40**: read [Stan's logger][snsabot]; stand up a + [Logbot][botworks]; write a minimal WWW frontend that takes items + from the logotron database and renders them; publish that. + +Then [discussion happened][so-he-was-thinking], and... well. I'm +maintaining a Lisp blog, so I guess I might as well add comments to +it, since I have a Hunchentoot genesis *almost* published, and since +the painstaking labour involved in moving every post to MP-WP (plus +fixing the links) would take a yet-to-be-determined amount of +time. For the same reasons, I'm guessing I could take a stab at a +logger WWW front-end based on logbot... or should I, really? + +I don't know, to be honest. For the record, I very much agree with +[Trinque's comment][trinque-comment]: I'm skeptical that the "Lisp +environment" can deliver more than the "Python environment", and it +might yet deliver less than the "LAMP environment" and in the end +prove to be a monumental waste of time. I'm not happy about the +prospects of getting stuck in a solipsistic hell of my own making, so +really, the thing that mainly motivates me to continue working on this +Lisp stuff is other people finding it useful. Is there anyone else in +the house who finds any use for this? + +I also agree with [Alf's comment][alf-headbashing], there's tons of +(burning) problems out there to solve, not like I need to add more on +my plate. So then I'm asking, dear forum, what do? + +[^1]: I actually have this broken down into pieces, let's look at it. + + First, the posts need to be indexed somehow in some kind of + database, so that the blogotron knows how to retrieve the content + and the comments for it and render everything into a page. I don't + care about the database backend, the code that does this should be + attachable to any type you like with minimal glue. + + Then, I'll need to make some modifications to the blog itself, so + that it knows that such thing as "comments" exist and can be + retrieved from said database and rendered. This includes page + layout modifications as well as backend scaffolding for getting + comments and inserting them below the post. + + Finally, there's supposed to be a way to post comments, à la + Wordpress' wp-comments-post.php. Additionally, this should come + with anti-spam support built-in, but... well, did you see the + "stuff that's burning" list? I'll patch that wound when (yeah, + when, not if) it starts burning. Until then, I guess all comments + are to go to the moderation list, or I'll whitelist IPs or + whatever. + + Oh, and by the way, I should also implement server-side selection + for this thing at some point. + +[citadel]: /posts/y04/068-the-story-of-the-citadel.html +[hunchentoot-v]: /posts/y06/09b-hunchentoot-v.html +[hunchentoot-via]: /posts/y06/09c-hunchentoot-via.html +[hunchentoot-vib]: /posts/y06/09d-hunchentoot-vib.html +[ttp-comments]: /posts/y06/099-tmsr-work-iv.html#selection-176.0-176.3 +[logging]: /posts/y06/099-tmsr-work-iv.html#selection-160.0-160.7 +[feedbot]: http://logs.nosuchlabs.com/log/trilema/2019-08-23#1930279 +[pastebin]: /posts/y06/099-tmsr-work-iv.html#selection-238.0-238.7 +[adalisp]: http://logs.nosuchlabs.com/log/trilema/2019-08-30#1932159 +[lispwork]: /posts/y06/099-tmsr-work-iv.html#selection-208.0-208.13 +[cuntoo]: http://trinque.org/2018/11/27/cuntoo-bootstrapper/ +[work-ii]: /posts/y05/090-tmsr-work-ii.html +[sbcl-and-others]: http://logs.nosuchlabs.com/log/trilema/2019-08-30#1932154 +[snsabot]: http://www.loper-os.org/?p=3452 +[botworks]: /posts/y05/080-botworks-regrind.html +[so-he-was-thinking]: http://trilema.com/2019/so-i-was-thinking/ +[trinque-comment]: http://trilema.com/2019/so-i-was-thinking/#comment-131283 +[alf-headbashing]: http://logs.ossasepia.com/log/trilema/2019-09-03#1933393