@dustypaws I’m also lost at .NET, but I’d be lost with ruby also.
IMO the best option is to have a clear API definition so that people can create their own backends in different languages if they want. This being an open source project, and wanting to leave the door open to decentralization in the future (not MVP launch), making sure the design is not married to any one platform or language is important.
So from that perspective it doesn’t matter if it’s C# or Ruby or anything else, just as long as the API is clearly defined. Inputs and outputs are what matter; the rest is semantics.