boring sunday.
today's work is going to be about finally sealing up all the memory issues in moxie. right now switching subslicing over to copy semantics so ownership of the "parent" slice doesn't get entangled with the segments cut out of it. the other task will be in switching code over that is using subslicing to do simple cut or reduction passes (one or two cursors with the writer before the reader cursor) to build a generic form of the io.ReaderWriter also with copy operations running as 64 bit segments instead of bytewise. the memory copy operations don't need to be on bytes, the optimal operation is 8 bytes at a time, that's the width of the memory bus inside the caches.
at approximately 45:30 in the 2019 movie Joker there is a scene where it shows a newspaper about the clown killing the rich jerks on the subway. at the bottom it says
exclusive: photos of disaster in ukraine, page 5 (or maybe 8)
this was also the year that zelenskiy got elected. a comedian with a chip on his shoulder.
so, been working hard on #moxie compiler for the last couple of weeks, and the current issue i'm dealing with is memory management.
as up to now, it's been one foot in GC world and one foot in ownership semantics.
currently i am working on some changes in the underlying semantics of dynamic array (slice) handling. Go's model uses the idea of "grow at append" automatically. this is doubly complicated, firstly, shared handles to subslices, and then, compound that with *concurrent* shared handles to subslices (aliasing).
i'm eradicating aliasing. instead, the default posture is copy semantics. when you subslice in moxie, it's implicitly a copy.
if you want to mutate a buffer, you use a cursor-based iterator like io.Reader/io.Writer
if your operation will not expand or more likely reduce (eg, unescaping text) you can do this with two iterators on the same buffer where the writer is before the reader.
if your operation requires expanding the buffer (eg, decompression, escaping) you have to write the copy into a new buffer.
none of this is especially cutting edge ideas but some language projects have taken one direction, while others take others. the functional drones tend to love copy semantics, and the object/imperative drones tend to like references.
i reject both as being sole solutions. sometimes copy is right. sometimes reference is right. being wedded to one or the other is retardation.
PSA:
anyone who inserts their own people to masquerade as part of another group especially in a leadership position is a
CUCK
the origin of this word comes from the work-stealing behaviour of the Cuckoo bird, which places its eggs into the nests of other birds, to steal their time and effort to raise their young instead of making the effort themselves.
this is a generic category of the activities of intelligence agencies involved in counterintelligence operations, also, which doesn't mean all cucking is done by spooks, and further, just to remind you, activists like George Soros and Peter Thiel and Klaus Schwabb are cuck-masters and do all kinds of spooky shit and are not government intelligence agencies, they are activists with a shitload of money, aka "philanthropists".
Cucking and refusing to acknowledge the blatant cucking going on in your community is cowardly and suspicious. If you go along with a cuck, you are a cuck, unpaid cuck, which is the most pathetic kind of cuck, lacking even the will to act according to your own mind.
it's the sixth of the sixth twenty twenty six
