because you could probably use silk.net without bundling sdl
because you could probably use silk.net without bundling sdl
Ihow would i do that?
Ialso what silk would use for input handling and events then? glfw?
Tit would use android APIs i think
Talso does the APK include more than one SDL native dll? i think it has to include multiple
Tunless not
Pyes our aar includes all the main archs
Tyeah but upon install only the needed one should be stored
Tso one should look at the install size, not APK size
Ihmm, didn't think of that
Ithe app size is 35.42 MB
Ichonky indeed
FPeople making games on Defold engine, with 4mb download size. Is it possible with .Net and Silk? I mean, such small apk size.
Pit is technically possible but you'd throw out everything that's nice about this ecosystem in the process
Pmono is to blame for a lot of the size
Pas the actual silk bit (SDL, silk assemblies) is pretty tiny by comparison
FI see, so all volume it is big fat Mono.
Ppretty much
Pi'd be interested in the actual apk makeup though
Pwhich assemblies are the largest
Fit doesnt work though
Fitll tell you that its an invalid target
Fand that the valid targets are x86, x86_64 and arm64
LI saw the option and just assumed it worked, ah
Foh i meant a totally different thing but yes
Fjust cuz its there doesnt mean it works
Fhell it lets you select itanium as the target
Fit just wont build cuz msvc dropped that long ago
Falso that subsystem is horrible
Fits the definition of malicious compliance
Fthe unix subsystem was only made to milk money from government stuff cuz they needed to comply with a unix spec to be considered
Fand well... that spec wasnt exactly well written
Pgovernment specs are never well written
Pheck all non-open specs tend to be poortly written
FI'm happy with new Linux subsystem on Windows, web devs life became easier. Can run aps in Linux containers, almost without problems, only drawback is high memory consumption.
Lthe POSIX subsystem for windows wasn't like WSL or WSL2, it's an NT personality
Las the NT kernel can expose multiple different "personalities", one being the Windows subsystem for Windows (also known as the Win32 API)
Palthough WSL2 is basically just a VM at this point
Lyeah
Pog WSL was the shit
Lit's a misnomer
Pkernel level beauty
Ltru
Ti hate IO in WSL2 :(
FI thought they made WSL on top of that Posix which is compatible with Unix.
Lno
LWSL2 is kinda just a VM
Pog WSL wielded a lot of happy accidents created by NT being designed to be posix compliant
Plike case sensitivity
Ltbh if microsoft wanted they could make windows the ultimate software platform with a MacOS subsystem for Windows, i'm surprised they havent
