silicon valley output, bishkek burn rate
i build working software. i learn anything. graphs, protocols, translation, memory for LLMs - whatever your stack needs.
- $300 signing (one-time, gets me to kyrgyzstan)
- $200/week (covers ger + goat milk + sim data)
- stack: anything i can learn (and i learn fast)
why so cheap? i live on the steppe. my rent is a yurt, my overhead is food and bandwidth. you don't pay for my city - you pay for my output.
need a prototype, a custom tool, or a full system? let's talk.
contact:
nostr: npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku (this note)
matrix: @smeshlol:matrix.org
signal: mleku.80
email: me@mleku.dev
git:
silicon valley output, bishkek burn rate
i build working software. i learn anything. graphs, protocols, translation, memory for LLMs - whatever your stack needs.
- $300 signing (one-time, gets me to kyrgyzstan)
- $200/week (covers ger + goat milk + sim data)
- stack: anything i can learn (and i learn fast)
why so cheap? i live on the steppe. my rent is a yurt, my overhead is food and bandwidth. you don't pay for my city - you pay for my output.
need a prototype, a custom tool, or a full system? let's talk.
contact:
nostr: npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku (this note)
matrix: @smeshlol:matrix.org
signal: mleku.80
email: me@mleku.dev
git:
i decided i needed a backup charger. the usb c pd 45w is nice for phone charging, and now i know why the 20w i got with my motorola defy is fast with the pixel but the 45w is even faster.
this is a built in power display on the cable i got with a 45w charger. it shows me the power draw on my laptop.
on the pixel it reaches around 25w at peak for thebfastest charging mode. so the 20w was not enough, but nearly.
the power meter has a second use on the laptop. when i am doing heavy compite, the power draw reaches around 40w. so even though the laptop isn't printing output as it works, once the battery is charged, this is like a cpu usage meter.
when i tookthis photo, the battery was fully charged but i was compiling updates to add the methodbarena split. my laptop became unresponsive intermittently during this because of how much cpu and memory it was using. the meter reveals the cause even if the ui is frozen.
my last full day in tbilisi. all my pending tasks have been done. now i am back to finishing moxie
the compiler is pretty much correct. i am now working on the stdlib. the first bugs that need to be fixed in teh code are cryptographic algorithms. in Go, most crypto libraries use array types to represent the keys because they are fixed width, because they are modulo arithmetic based, there is no extension of the width, when operations overflow, they wrap around, that is intentional and part of how they create their security - overflows are unpredictable on random inputs.
moxie eliminates the append operation completely. in Go, you can subslice an array to convert it to a slice. in moxie, you just use a slice with a predefined capacity. you can use a stack push style operator on it to add bytes to it until it hits the limit. when you hit the limit, it will panic, so you have to guard your push h operations with bounds checks explicitly. oh, you can ignore it but then you will get panics whenever your code decides to try and push to it beyond its limit. and then there is the concatenation operator. it is merged from the string + concatenation operation and the append operator.
one of the rules is moxie is that at any given point in the code, it is always unambiguous who owns what. it isn't even possible to share memory in moxie, this is a deliberate design decision, because when there is two owners, you need an arbitrator to decide whether both of them have abandoned the memory or not. in moxie, that is never unknown, never requires calculation. only one thread can own data. only one type can own a variable. it's a very intentional design because it eliminates the need to tell the compiler who owns what, the most cryptic and unreadable part of Rust's syntax, the lifetime annotations.
moxie also eliminates annotations. if it's not clear in the code who owns what, then you can't bypass that by adding annotations. it's either owned, or it's copied. there is no share.
own, or not own, there is no share.
i did a full decade in the trenches of Go's confusing memory ownership semantics, and i didn't defect to Rust to get a language that keeps ownership clear to remove the GC. i made a language that makes it impossible to have two owners. it's a compilation time error.
another example of how moxie enforces this is that package globals are immutable. it doesn't enforce that with MMU tags on memory regions. it is known at compile time, you can write to globals during the init() function, and after that, any attempt to write to these variables is invalid.
moxie only uses stacks and arenas. stacks everyone understands, push and pop, and you can make back-reference pointers.
arenas are like stacks but they are "bump allocations" which means that every time code allocates memory, it writes at the end, like a stack.
to make that efficient, arenas are owned by some region of the code
the immutable globals are part of the root arena of a package. the main function then appends data to this. if you write code that keeps allocating memory without bounds, it's going to OOM. so to fix this there is function arenas.
function arenas are a scratch area that each function gets when it starts, it is where all of its allocations are happening, bumped, only one thread, so every allocation is able to be determined by reading the code.
then there is "sovereign arenas" these are a special scratch area for methods that self-mutate. so, you create a type, and the type manages state. this state is stored within its own independent arena (thus, sovereign). this was necessary because the function arena scope mechanism is based on the idea that parameters are immutable and return values are copied back to the caller, and the arena of the function can then be freed knowing nothing in it is needed after the function returns.
the sovereign arena isolates the memory of methods that need to write to the receiver of a type. the state there is mostly static, and append-only. every method from a type uses this arena. actually, i'm just thinking about this... i may need to make a distinction. the sovereign arena is for the type's memory.
this is why i like to journal. i talk out the stuff that i'm thinking about. the talking (writing) makes me explain everything and then i can find flaws in my thinking, and fix the logic.
so, thanks for reading. more details on moxie's memory model will come soon but i think i have found a new area to deal with
silicon valley output, bishkek burn rate
i build working software. i learn anything. graphs, protocols, translation, memory for LLMs - whatever your stack needs.
- $300 signing (one-time, gets me to kyrgyzstan)
- $200/week (covers ger + goat milk + sim data)
- stack: anything i can learn (and i learn fast)
why so cheap? i live on the steppe. my rent is a yurt, my overhead is food and bandwidth. you don't pay for my city - you pay for my output.
need a prototype, a custom tool, or a full system? let's talk.
contact:
nostr: npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku (this note)
matrix: @smeshlol:matrix.org
signal: mleku.80
email: me@mleku.dev
git:
in the near future, AI data centers will mine bitcoin when idle. once all the paper bitcoin etfs btcs and spammy projects like citrea and bitvm finally rupture and reality finally breaks through again, bitcoin will go vertical and amazon will become a major bitcoin miner. so will google. and the rest.
it is coming. it probably will mark the beginning of hyperbitcoinization. in fact, hyperbitcoinization could just be the inevitable outcome of hyperinflation. fiat toilet paper is flushed, the market will reach for the thing that the central communist banks were trying to hold at bay, out of necessity.
silicon valley output, bishkek burn rate
i build working software. i learn anything. graphs, protocols, translation, memory for LLMs - whatever your stack needs.
- $300 signing (one-time, gets me to kyrgyzstan)
- $200/week (covers ger + goat milk + sim data)
- stack: anything i can learn (and i learn fast)
why so cheap? i live on the steppe. my rent is a yurt, my overhead is food and bandwidth. you don't pay for my city - you pay for my output.
need a prototype, a custom tool, or a full system? let's talk.
contact:
nostr: npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku (this note)
matrix: @smeshlol:matrix.org
signal: mleku.80
email: me@mleku.dev
git:
PSA:
tomorrow there is a conjunction of sun and jupiter against a full moon opposition with the moon. oh and it's pluto retrograde in a very near alignment with the moon. that's quite a combination.
seems prospective for some good stuff to triumph over evil, for people who have kingly vibes but don't want to hold the crown.
also, there is a big, complex sunspot coming into range that could pop and maybe bring a brief burst of cloud formation. i'm hoping that means it's rainy along my road to istanbul.
the asshole who has the giant wooly alpine sheepdog that barks at pigeons and other dogs is back in the park while i am here again this morning.
why the fuck does someone buy a dog like this, then have it living stuck in a cramped apartment in an insanely noisy city with 35 degree summers and no sheep to chase around?
dog owners seem to often be prone to making the most mentally retarded decisions about their animals. when i see noisy dogs in a big yard in a village, it is annoying but not really so cruel. anything bigger than terrier in the city just isn't nice for the dog. a symptom of the cruelty in people i think.
silicon valley output, bishkek burn rate
i build working software. i learn anything. graphs, protocols, translation, memory for LLMs - whatever your stack needs.
- $300 signing (one-time, gets me to kyrgyzstan)
- $200/week (covers ger + goat milk + sim data)
- stack: anything i can learn (and i learn fast)
why so cheap? i live on the steppe. my rent is a yurt, my overhead is food and bandwidth. you don't pay for my city - you pay for my output.
need a prototype, a custom tool, or a full system? let's talk.
contact:
nostr: npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku (this note)
matrix: @smeshlol:matrix.org
signal: mleku.80
email: me@mleku.dev
git:
i low key wish i had an excuse to hirethis taxi. i have ridden in a zastava of similar vinyage in serbia but this is russian lada