social.noyu.me

we are in the timeline where Sweden (Sverige, Svea rike) is named after the Swedes. but as anyone who's read about the titles Swedish kings used to have will know, Sweden is also the kingdom of the Goths. what if we were living in a timeline where we called it Gothen or something. that would be cool. Gothenburg would probably be the capital

i should write a blog post or something about Dashcode, and some thoughts about the web on the iPhone circa 2007

does the copy in @property(readonly, copy) mean anything. copying only applies to setters right?

“why don't languages like c++ and java have multiple constructors? they're so useful! i love that rust has multiple constructors!”

the finger curls on the monkey's paw

and i find out about the hell of objective-c designated initialisers

so, touchHLE is afflicted by a lot of “not invented here”-ism, which is all my fault. I have reimplemented a lot of stuff that other people would try to get from libraries.

in my defence though, this gives me some superpowers:

• I have a very deep understanding of the whole system! it's hard to overstate how useful that is.
• there's very few dependencies, so the binaries are small and the build times are short, and it's auditable

but there's something else cool, too…

suppose I am writing some code that will take a god object containing all the state of an emulator, move out several key components of it, reset their states, and then place them into a new god object that's meant to be almost indistinguishable from a completely fresh one. what's a nice, horrifying metaphor for this. i want a word that conveys the idea of like, organ harvesting from a perfectly healthy subject or something. or some kind of spiritual thing.

sneak peek of an upcoming touchHLE feature :3

(this is why I have been spending all this time implementing UIKit)

the cc rust crate has a new feature by yours truly: a method for specifying the c/c++ standard version :) https://github.com/rust-lang/cc-rs/releases/tag/1.0.83

aha

ahahahaha

AHAHAHAHA

bin/clang \
    -target armv6-apple-ios2 \
    hello-world.c \
    -nostdlib \
    -Wl,-U,_puts,-U,start,-alias,_dyld_stub_binding_helper,dyld_stub_binding_helper \
    -o hello-world.dylib

IT WORKS. iT WORKS,,,,

FEAR ME!!!!!

my kingdom for normal rust macro scoping

what i want:

pub macro_rules! foo {
    // …
}

what i'm forced to put up whenever i want to use intra-doc links, which is basically always:

/// Please don't write `use crate::foo;`. I know, I can't
/// stop you. But you have to write `use
/// crate::qux::baz::foo;`, because there is a meaning to 
/// this module hierarchy. I am literally Begging you. I am
/// prostrating myself before you. I'm crying. Can't you
/// see how much this is hurting me? Please. Please. Please.
#[macro_export]
macro_rules! foo {
    …
}
pub use crate::foo;