ruta @ruta@mastchan.org

@gothwitch That's the sitting position when he's ready to lick his balls.

Making an ORM is not as easy as I thought. damnit. I don't have much left for this weekend.

I think I should just focus on providing support for realm to push out the pod for now. core data can be added later next month.

Went past the Blizzard campus today. Looks like quite a lot of their people aren't too happy with their company's recent err...revelation.

What's a reasonably good ORM for iOS, either targeted for Realm or CoreData? @eurasierboy

Finally finished adding migration support for ActivePersistence. Now I have about 5 hours left before I "wake up" and go to work.

With a typed language on the frontend, database migration is just passing a migration block and trying to run it; Or kindly "force" all my users to delete and reinstall their app. Most people prefer the latter.

Ordered some car stuff from the internet with my fake name Spongebob. I think someone in their office also like watching Spongebob and made this sticker to send along with the package.

More obvious snapshot of the white space under the navBar.

Not my bug.

Since I like to do things programmatically, it's probably about time I rewrite the app with SwiftUI, otherwise I'll keep running into some small but annoying bugs in the future. This especially true as Apple doesn't like to open source most of the stuff their developers rely on.

If I created the app programmatically on iOS 13 without SwiftUI, then large title navigation bar seems to be having some problem with the status bar on the top. The status bar's background color api is not available anymore. But for apps that were created with storyboards, this is no an issue somehow.

Naming a protocol is quite annoying when the English word does exist, but doesn't ryhme as an adjective. Like `describable`, `errorable`

The massage cat comes to visit again.

If a method may or may not throw an exception, does it make it exceptional?

I’m seeing duplicate activity indicator when I force a manual reload on Amaroq around the top-ish of the tableView. How about remove one and leave the other alone?

Shit test needs a lot of shit to sample, apparently.

Pain and so much pain...

Shaved