Don't you know we're fasting?

What should I do if I already did that in 2022?

#Bitcoin doing Bitcoin things...

Maybe my media jobs weren't that bad in the end. If somebody has an idea where an old fart can make a buck writing, You know where You can find me...

so again, that's the point, they are just a double indirection like an interface, a static type abstraction, just as it is cheap to resolve a pointer it is cheap to resolve the "fat pointer" of type and variable in an interface

it's just an interface

they muddy the waters by inventing new names for well established concepts

ok so they are just another silly name for interfaces, but trying to say they are not interfaces

you can do that now with interfaces with generic parameters in Go since 1.24, this "prototypes" thing

it's a relaxing of a rule that you can't define external (not in package) methods on a type, you can now define methods on a type alias

i barely even use generics in Go yet, mainly i just use it to make it so people can call my code with strings but my internal implementations remain in mutable bytes. they won't retract the mistake of making strings immutable

rust's immutable by default is exactly the opposite of how i think it should be done, and the immutables in Go are the biggest pressure on GC because you can't just make them into freelist buffers, they are immutable, they have to be disposed with the GC unless you want to dice with unsafe

also, in Go, effectively declaring a type is creating a prototype, because you can embed them in other types, you can alias them into new types, and now you can even declare new methods on the aliased type

Go lets you do all the things that you need, and rejects all the things you don't, in the overriding prime directive that no construct should be expensive to compile, or execute.

how do prototypes differ from interfaces and structures (named ordered lists of variables)

Dude one thing I learned early on is to never trust someone who says how many years of experience they have. Cause the biggest morons I've ever met in the powergen industry had the biggest "years of experience" stat on their lapel.

I'm always going to look down on code that has exactly zero tests and assume it doesn't work. Cause most likely the developer doesn't even know what it actually does. Just what they hope it does.

go has closures as well, and prototypes smell objecty to me

Until you ship code that never fails in its primary function, you'll never get the point of TDD.

But the fiat market loves buggy code, so that's what it gets.

Until you ship code that never fails in its primary function, you'll never get the point of TDD.

But the fiat market loves buggy code, so that's what it gets.

classic example of how #golang does #composition better than any other language

took me all of about 30 minutes to completely refactor #realy to separate the "filter" out of the filter type, which i achived by extracting the fields (kinds/authors/tags/since/until) from the existing plain muddled "filter" structure

it is now called `simple.Filter` and the reason for doing this was to make a single structure that embeds elsewhere that is the primary parameters for an actual `/filter` request on the simplified nostr HTTP API

now i have a full interface composed of single APIs so i can treat them as a whole or separately... it was an important step on the path to implementing a full simplified API

i did add a `/subscribe-fulltext` endpoint to distinguish between the words-and-filter distinction instead of repeating the same mistake of making "optional" things when i want them to be extensions

continuing...

...he's 5(35). Should our sweet boi still be...the way he is?

I remember these times so clearly. I was a little bit concerned. It is time for people to wake up from this hypnosis though.

Some dogs look _where_ you're pointing; others look at _how_ you're pointing (i.e., at your finger).

Our pup looks at my finger.

Handsome? Definitely. Sweet? Usually. Bright?...ah, no.

But he's our good boi.

#whoosagoodboi #petstr #dogstr