Recent Posts
Gary... knowing your end goal, to have a computer that could absorb every hit song and then spit out a great song of its own devising; I went ahead and finished your program for you.
Here is our first product in the key of E!:
Lovefizz
Oo baby, I love your eyes
Each night I doubted myself
And learned to need the lies
I’m taking the redeye sky high
Why, why, why, baby, why?
Oh baby, love ain't what you get
It’s always been who you know
And never who you’ve met
It’s the reason that we treason until wet
Wet, wet, wet, baby, wet.
Prechorus:
We danced among the stars
We ate a big sandwich (??? Well, that’s what it spat out, man)
We hated every foreign car
But only cuz we couldn’t afford it
Chorus:
All there is to know about love
Is that love is all there is
Your bubble butt really makes me fizz
Lovefizz! I is lovefizz!
:\ Sweet Sally Brown what happened?
I think we still need to work the kinks out. Either that or put Ray Davies from The Kinks to work as a co-programmer.
After watching a NOVA documentary on the development of ape minds, I think proper development of a society of mind requires a society of minds, and that's far beyond what I can even imagine doing right now by myself. It's not enough to have one "parent" teaching a "child".... intelligence requires a whole community of others engaged in the process. Even for something as simple as a musicbot.
So I'll go back to exploring the contraption. Perhaps one piece of the puzzle might be solved in my lifetime. Perhaps not... at the very least, it's interesting to me. Like a classic rust-eaten car in the garage. I can tinker with it on weekends.
"Your big ideas don't fit!" -- Randy Stonehill
It is probably fairly easy to get a computer to spew out fairly basic chord sequences and musical lines. What you might have problems with is how it might innovate. A computer will have no aesthetic sense, so it can't tell if something sounds good or bad, or catchy even.
To a great degree, we're programmed to like certain patterns in music. The computer could be told to create only the slightest deviations from time to time, then solidfy the deviation's place by intensifying this offshoot with each new song, thereby "educating" the listener and eventually creating a bona fide genre.
The days are long, and now I read and code.
I have been torn between building a front-end for a system I nearly (but not quite) understand, and re-creating everything from the ground up. So many ents! So much there that almost works! So much spelunking into the crazy!
Screw that. There are too many snarfs, waldoes, febes, bebes, turtles, agendas, and a thousand other things to make it work right now.
So my current hobby is, I'm gonna extract a library. Let's see if we can't make something of spaces.
Well, clearly I never got around to extracting a library. But I just had a great idea: Use a graph database as the persistence layer for the ent.
Those which are no more: SnarfStatistics, Cattleman, DiskTester, SpecialistRcvrJig, FakePacker, FakeDisk, MockTurtle, TestPacker, TestFlockInfo, PairFlock, SnarfHandler, SnarfRecord, SnarfPacker, LiberalPurgeror, Purgeror, SanitationEngineer, CloseExecutor, DeleteExecutor, RepairEngineer, gchooks, PersistentCleaner, SpareStageSpace, StackExaminer, DoublingFlock, SimpleTurtle and DiskIniter.
In the crosshairs: Pumpkin and Turtle. Probably Abraham, too, but that might take awhile.
More excisions: CategoryRecipe, StubRecipe, BogusXcvrMaker, Binary2Rcvr, Binary2XcvrMaker, Binary2Xmtr, CommIbid, DiskSpecialist, Rcvr, Recipe, ShuffleTester, SpecialistRcvr, SpecialistXmtr, TextyRcvr, TextyXcvrMaker, TextyXmtr, TransferGeneralist, TransferSpecialist, XcvrMaker, Xmtr, XnReadStream, XnWriteStream, ActualCookbook, BootMaker, BootPlan, Connection, Cookbook, DirectConnection, cobbler, TokenSource, CountStream, HashStream, ReadArrayStream, ReadMemStream, SnarfInfoHandler, WriteArrayStream, WriteMemStream, WriteVariableArrayStream, urdi, DiskCountSpecialist, CopyRecipe, cxx, ActualCopyRecipe, PseudoCopyRecipe and ShepherdStub.
There are now 1,749 compile errors.
I am home sick and bored. It's hard to concentrate but I decided to remove a bunch more stuff, mostly related to the server and promise manager. The promise manager stuff got removed because a) it's weird compared to how modern servers do things, and b) the guy who did most of the promise manager stuff has since had better ideas about how to do it.
Newly excised: ByteShuffler, CommFillDetector, CommFillRangeDetector, CommRevisionDetector, CommStatusDetector, CommWaitDetector, DetectorEvent, DoneEvent, ExceptionRecord, FeArchiver, FilledEvent, GrabbedEvent, NoShuffler, Portal, PromiseManager, RangeFilledEvent, ReleasedEvent, RequestHandler, RevisedEvent, SimpleShuffler, ServerChunk, ServerLoop, ChunkCleaner, Category, MultiCounter, BatchCounter, Counter, SingleCounter and FluidPromiseVar.
Except it turns out that Counter and its cousins are used by the BeGrandMap, among other places, so I put them back. 237 compile errors. No idea when it might be back in a runnable state, because even when I fix all the compile errors, I've surely removed something the beast currently depends on.
