-
Notifications
You must be signed in to change notification settings - Fork 18
Description
We are happy to answer your questions about the code or discuss technical ideas.
Please complete the following checklist (by adding [x]):
- I have searched open and closed issues for duplicates
- This isn't a feature request
- This is not a report about my app not working as expected
I see a C# SDK is planned for non-web use cases.
Will the C# SDK work like a traditional library, meaning only C# apps will be possible without creating cumbersome language interop, and the .NET virtual machine will be required regardless?
Or will this be more like Proton Bridge for Protonmail, and C# will be used to create a standalone app that any language can communicate with via some network protocol, say HTTP?
I strongly hope it is the latter. The former seems a worse case design scenario, where dealing with the .NET virtual machine is obligatory. So pretty much anything other than that would be an improvement, except maybe .NET Native which to my knowledge still uses closed source compilers and hence isn't trustworthy for an app focused on privacy.
Some clarity on how developers are expected to use the C# SDK, and perhaps why C# was chosen, would be great.