#lambdamoo — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lambdamoo, aggregated by home.social.
-
#lambdaMOO #sixel #scheme #schemacs #lisp #interface #learning #accessibility w/ Ramin, Kent Pitman #lispyGopherClimate
-
https://mastodon.murkworks.net/@wrog/116755896874528089
stupid version was 60 lines
30 days later, the insane version is ~900 lines of m4 = 2000+ lines of shell script (after m4sh has done its bulletproofing)...
...not counting 600+ lines of "semi-literate m4 programming" that expands into ANY of:
. the (markdown) reference manual
. the case statements for each of the passes over the command line,
. the function to save all of the "sticky" arguments
(and probably should also generate routines to
. initialize the underlying variables
. display all inferred settings [for --dry-run]but for now I just have it produce the checklist so I know I've covered everything,
...there being only 26 actual options
...so far
https://wrog.net/moo/l8tf/Install_Tests.html
aaaaaaa
-
https://mastodon.murkworks.net/@wrog/116755896874528089
stupid version was 60 lines
30 days later, the insane version is ~900 lines of m4 = 2000+ lines of shell script (after m4sh has done its bulletproofing)...
...not counting 600+ lines of "semi-literate m4 programming" that expands into ANY of:
. the (markdown) reference manual
. the case statements for each of the passes over the command line,
. the function to save all of the "sticky" arguments
(and probably should also generate routines to
. initialize the underlying variables
. display all inferred settings [for --dry-run]but for now I just have it produce the checklist so I know I've covered everything,
...there being only 26 actual options
...so far
https://wrog.net/moo/l8tf/Install_Tests.html
aaaaaaa
-
@wrog Just curious, what are you doing, modernizing #LambdaMOO? Are you going to be implementing any of the features some of the forks have done? E.G. sub-second suspend/fork, waifs, anonymous objects, 64-bit ints, etc? Also I assume you know of the rewrite in Rust called Moor?
-
@wrog Just curious, what are you doing, modernizing #LambdaMOO? Are you going to be implementing any of the features some of the forks have done? E.G. sub-second suspend/fork, waifs, anonymous objects, 64-bit ints, etc? Also I assume you know of the rewrite in Rust called Moor?
-
(I evidently suck at capitalism; oh well...)
and on the off-chance there *does* turn out to be some way to monetize this, the most likely outcome is that some asshole trillionaire will just buy the empty shell of Xerox and claw back all of the rights
(not that legality seems to matter a whole lot for the folks with That Much Money...).
(oh weird, spell-checker doesn't like "trillionaire"? wtf?)
-
(I evidently suck at capitalism; oh well...)
and on the off-chance there *does* turn out to be some way to monetize this, the most likely outcome is that some asshole trillionaire will just buy the empty shell of Xerox and claw back all of the rights
(not that legality seems to matter a whole lot for the folks with That Much Money...).
(oh weird, spell-checker doesn't like "trillionaire"? wtf?)
-
(in order to, say, know that a particular commit actually fixed something, or that a particular problem indeed existed in an old version) ...
....cannot imagine how devs would consider that acceptable and yet that seems to be the typical way of organizing codebases these days (i.e. one repo with everything + test subdirectory in the source; and frameworks I've looked at seem to assume this)
There's also the small matter that many of the tests may well be applicable to the various MOO forks out there, say if you want tests for language definition compliance or database file format correctness
(yeah I know, heaven forbid I should do anything that might benefit my competition; I evidently suck at capitalism; oh well...)
2/2
-
(in order to, say, know that a particular commit actually fixed something, or that a particular problem indeed existed in an old version) ...
....cannot imagine how devs would consider that acceptable and yet that seems to be the typical way of organizing codebases these days (i.e. one repo with everything + test subdirectory in the source; and frameworks I've looked at seem to assume this)
There's also the small matter that many of the tests may well be applicable to the various MOO forks out there, say if you want tests for language definition compliance or database file format correctness
(yeah I know, heaven forbid I should do anything that might benefit my competition; I evidently suck at capitalism; oh well...)
2/2
-
also I feel like I'm re-inventing a wheel, but for some reason the question of exactly how you graft a testing regime onto a codebase that didn't previously have one doesn't seem to come up a whole lot these days
... or at least something you would **expect** to come up way more often with 30-year-old codebases that predate the "write your tests while you're writing your code" paradigm that seems to be prevailing now
Although I am perhaps also being weird in insisting that the test repository remain separate from the source repository because, oddly enough, I want to be able to switch between source commits/branches/versions without having my tests changing out from under me ...
1/n
-
also I feel like I'm re-inventing a wheel, but for some reason the question of exactly how you graft a testing regime onto a codebase that didn't previously have one doesn't seem to come up a whole lot these days
... or at least something you would **expect** to come up way more often with 30-year-old codebases that predate the "write your tests while you're writing your code" paradigm that seems to be prevailing now
Although I am perhaps also being weird in insisting that the test repository remain separate from the source repository because, oddly enough, I want to be able to switch between source commits/branches/versions without having my tests changing out from under me ...
1/n
-
This is so weird. I'm actually writing documentation *first*.
(well all right, I did already code the really stupid version of what I wanted, but now I'm having to write the less-stupid version, but there's also the small matter of deciding how insane we want the less-stupid version to be...
...guessing I've probably summarized All Software Development right there)
-
This is so weird. I'm actually writing documentation *first*.
(well all right, I did already code the really stupid version of what I wanted, but now I'm having to write the less-stupid version, but there's also the small matter of deciding how insane we want the less-stupid version to be...
...guessing I've probably summarized All Software Development right there)
-
The world of MUDs is incredible ! Tu pouvais jouer avec des inconnus à l'autre bout de la planète en ligne #mud #web1 #telnet #lambdamoo #rpg #tabletoprpg #jdr #roleplay #mmorpg