stackotter

> I think this kinda causes a bit of distraction when observing sources from users' perspective. However it's a minor thing 💁‍♂️ Yeah, maybe it can be moved under the...

> Alright so for now I'll: > Rename Types to Core > Add Makefile Yep sounds good 👌 > And there is still an issue with docc 🤔 Hmm yeah...

> `@_exported import`s are not shown in docs Ah sad, fair enough. Yeah that's fine for now.

I love the idea of HydraKit integrating with SwiftCrossUI, I've been waiting for an opportunity to figure out how 3rd party libraries can work with individual backends to provide new...

> @stackotter after further review, is `type: .dynamic` along with a `.alwaysStatic` linking strategy something we want to be doing here? > > My C/C++ senses tell me this is...

Thanks for bringing this to my attention, I didn't realise that SwiftPM treated `0.x.0` and `0.(x+1).0` as compatible (because before `1.0.0`, people generally bump the minor version on breaking changes...

Ah, unfortunate, that may require making our own socket library in future then (or updating that old one), cause I'd like to eventually bring hot reloading to windows too. I'm...

Does ZeroMQ let you just use their cross-platform tcp socket wrapper?

Good to know! I've used that in the past and liked it. For now I think this issue can be closed on Windows cause I've disabled the hot reloading related...

I think SwiftCrossUI does kinda force ViewModel concept on devs at the moment (cause all state must go in the observable `state` property of the view), although I would probably...