Even then, probably more important things like hooking into the API of the various platforms

I feel like these days it's absolutely essential for your app to serialize data. If not to save it, then to transmit it over a network or something.

it does for every data driven projects

And it seems most projects are these days

Win32 🙂

32? What year it is now? 🙂

The year of using a modern language to interact with terrible legacy Windows libraries, I'm hoping.

Isn't windows trying to ditch Win32 in favor of UWP?

Not that it's likely to happen (Win32 has more legacy than Java), but would it make more sense for Kotlin native to work with the newer spec? (It's an honest question about a subject I know absolutely nothing about)

Windows 7 is supported until 2020, so until then Microsoft can change strategic direction a thousand times for all I care.

Getting Kotlin running on Windows and working with the basic Win32 API would probably be a prerequisite for the UWP stuff anyway, I imagine.

They're trying but they conceded and now let Win32 apps on Windows store from what I've heard

Can't say I'm too interested in it, nor are many (the store sucks, they treat their owners like dirt), and it seems thus far their "want to run opengl\vulkan on UWP?" The answer is "use d3d". They even go so far as to show you how to use ANGLE to translate to d3d at runtime for your gl apps facepalm

Okay, good to know

Win32 just brings up some pretty terrible memories 😕

but it is still the n1 platform for games..

Indeed, luckily there are frameworks/libraries that remove that pain

more to the point, if it's possible to do incremental migration of an existing codebase to kotlin native (or becomes possible), then win32 is where it's at for a lot of big codebases

Where is debugging support right now?

IT'S COMING 😄

How stable is the EAP? i.e. when would Jetbrains feel good about putting kotlin-native code in production?

patience, young padawan

ok now you're just having too much fun teasing us 😉

Just reporting status 😉 In fact, curl interop was not as smooth as I expected it to be. All because

curl_easy_setopt

being variadic loosly-typed function, callback function signatures not declared anywhere, etc.

funny how I read yesterday that curl "does too much” https://www.reddit.com/r/programming/comments/61rh9j/curl_is_c/

I have a good feeling 😉

Not this week 🙂

okay… will have a slow weekend then

4th of April?