# comfy units

Freedom units are better then commie units. But, well there are allot of dead units that should be depecated for prefix list techonology, with a rather simple suggestion that if you cant devide by 3, or 4 you dont belong in my kitchen. So base 6, prefix list, a mini is 1/6th of the base unit and a very mini is a 1/36th of the unit. A big is 6 base units and a very big is 36 base units.

# petal function

I couldn’t find it under any name and had to find it via trial and error, so here is the petal function, it statelessly places the petals of a flower: float centerx=windowx/2;//dont actaully pass these, make some compile time float centery=windowy/2;//or wrap the loop in a function float layer=4.7; float scale=50; float starting=.001; float layerdistence=.3; Vector2 spiral(float i){ i+=1+starting; float angle=(std.math.PI2)/layer; return Vector2( sin(iangle), cos(i*angle) ) *log((i/layer)*layerdistence+1) *scale +Vector2(centerx,centery); } layer distance: affects how squished the inside is (.

# zig first impressions

So I worked my way thru “ziglings”, I’m not claiming to be an expert or anything but I do have some takes. Use case From the non-hype talk on zig, the impression I take away from it was it would be a good target lang for a transpiler and maybe some low-level software. After learning a bit, I’m even more sure of this. The “there is no confusing control flow” as a design goal, so no op overloading, passing a value by reference means making a pointer, etc.

# mixin interfaces

It strikes me I’ve never seen someone else explore the concept of asking for mixin templates to be a major “interface” of anything in d. It’s quite flexible, and could potentially be expandable. Imagine a UI interface implementing dirty flags, you either implement a recursive template that goes into user-generated widgets types to build up a parallel dirty hierarchy that must be similar in structure to whatever the user is doing, or you could put something that detects if the user-defined a dirty bool, and if not, mixes something that makes an educated guess of a method(perhaps you store a hash of your widget)

# walk in the rain

You are capable of surviving the elements for 20-minute chunks at a time. You can go feel nature, during a very loud thunderstorm that takes out some tree limbs; and you’ll find it’s fairly trivial when taken in small doses. Camping needs special shit, you’ll be uncomfy because sleep is important, and you’ll be dirty; shits annoying I’m not a naturephile I’m not suggesting that, but I like walking in the middle of the night during “heavy rain” when people will stop and ask if I’m alright.

# 3 year darkage

One of the possible futures I see happening is things get actaully unconfortable: uncertiony about food, eletericy is spotty and expensive, (morden) climate control is expensive enough to be unused or broken for the majority of the population, governence breaks down signifgently, voilent gangs roam the cities till poeple flee that shit. For 3 or so years. Then things get very productive and sane. This requires a few thoerys to justify and must be fairly reasonably predictive:

# Unironically antivaxx

When I wrote that blog post that I was “proudly antivaxx” I was mocking that a dictionary thought opposing vax mandates was antivaxx. I’m no longer convinced that isn’t the definition anymore, soooo, I’m for self-ownership to the point of people being able to sell organs and the current bullshit of this escalating pressure to affect mental decisions is so disgustingly unacceptable, give me the title, I’ll take it and wear it happily you fucking cucks.

# Composing state machines

After reflecting on my “lerp list” project, I conclude these are not d ranges, or any other model of iterator for that matter. I always knew I abused the interface; but I think my ideas on the subject have cystlized on the matter, I often make state machines and while community interfaces are nice, honestly truely wonderful I do just eventually learn the names, I want to make things that just won’t fit.

# playing with dimensions

So, a while ago I made a little demo of a 5d space “game”. I’m pretty sure it would be a dead-end, “warheads” that lovely game that I found in a bargain bin for 1\$ as a child isn’t exactly well known, turn-based space combat with destructive planets didn’t exactly stick, and 5d chess failed to communicate how it appended the rules to people to any practical degree. So taking a not all that well-known and loved genre of game and appending something that massively limits player bases to the point you can’t find a game.

# Community Gui Interface

So, D has ranges, I feel this is among its strongest traits that worked, despite giving zero fucks about the actual std.ranges.interfaces. “Why”? Well, the main reason is it works as a solid landmark for a naming scheme for duck typing, you can write your bonkers data structure, and when you go to name the first element, and you pick front and not: head, Front, FrOnT, start, next, _front, e, or EnterprizeGradeHeadOfIntQue, when you go and copy and paste an algorithm code to fit with your data structure code it has a chance it just magically works, and a more realistic chance you go make an ugly hack to make a compile error go away and write a unit test with your finger crossed.