I need to fuck her so badly
(kotlin. the programming language)

seen from United States
seen from United States
seen from Yemen

seen from Germany

seen from Germany
seen from United States

seen from United States
seen from United States
seen from China
seen from Indonesia

seen from Colombia
seen from Netherlands
seen from United States

seen from United States

seen from Malaysia
seen from China
seen from China
seen from Netherlands
seen from China

seen from Malaysia
I need to fuck her so badly
(kotlin. the programming language)

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
ohhhhh fuck just realized I'm gonna have to write websocket code in fucking kotlin (or I could use java, but I think that's worse) eventually. websockets in rust were gross enough, I don't even wanna think about how awful they're going to be in kotlin
Kotlin 入門
Running my first emulator and practising Android development.
🚨 Attention Devs! 🚨
STOP trying to convert legacy Java codebases to Kotlin, just STOP.
It's always half-baked and causes issues for everything else. and NO, KOTLIN is NOT 100% JAVA COMPATIBLE. It works most of the time UNTIL IT DOESN'T.
btw it also doubles my build time which is super annoying

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
damn
Two steps back, one step forward. Have re-written the still oh-so-crude basic rendering. Am missing h, u, o, the consonant ligatures, and minimum acceptable vowel shapes on a number of the basic forms. Which is to say a lot. But! Am still feeling happy about progress so far. The stroke tracing animation in particular pleases me.
The phonetic ambiguity resolution is still a bit janky, am not writing long term preferences to DB yet (hence a lot of crufty results) or retaining any phrases at all for that matter. But! Am getting closer and each re-write of backing logic gets easier to work with.
Too many competing next steps, but will continue to press on. Short term list: adding Gregg rendering to the IPA dictionary lookup, implementing English dictionary lookup, saving Gregg -> IPA & IPA -> English bridge preferences, finish implementing the fucking font 🙈, phrase saving/import/export. After I finish those, I think I can do an alpha app release. And then I can start implementing the practice/learn Gregg lessons.
If anyone was interested in helping, would welcome it. Am really struggling with the Bezier curve decisions needed to create font. The whole "render it all relative" constraint has me just beating my head against the wall, trying to visualize/understand/remember how vector math works.
(timelapse of me using Boxy SVG to audit the shapes I'm trying to render)