Silverlight or Unity?
Posted: 17 Mar 2011, 01:06
Assuming that I stick to the C# programming language, for the game I'm trying to make (and sticking to it, despite being in way over my head), should I be really be using Silverlight, like I've been saying I will, or should I be using Unity?
Both are C#-based browser plugins, both have out-of-browser modes, as far as I know, and both are free, although Unity has add-ons that cost money.
If I go Silverlight, I'll definitely run into problems. I can only use TCP, for which there are no libraries to make things easier. I can't serialize to binary, forcing XML serialization (though that's not much of a problem). Mostly, I think, it's the lack of libraries for network communication for Silverlight.
Unity, on the other hand, has its problems currently as unknowns. Am I going to be able to transfer a 2D environment to a 3D-native engine? Am I going to run into some sort of problem where the only solution costs over $500? But at least I can use Lidgren.
Plus, Silverlight adoption seems to be higher than Unity. Then again, not every Silverlight user plays games on SL (probably very few, actually), while virtually every Unity user is playing games, since that's exactly what Unity was built for.
What other problems are there? What do you think I should use, for both my sake and yours (if you decide to play my game once it's ready)?
(Boy, I do talk a big game about my game, when I'm nowhere near ready for even the test version.)
Both are C#-based browser plugins, both have out-of-browser modes, as far as I know, and both are free, although Unity has add-ons that cost money.
If I go Silverlight, I'll definitely run into problems. I can only use TCP, for which there are no libraries to make things easier. I can't serialize to binary, forcing XML serialization (though that's not much of a problem). Mostly, I think, it's the lack of libraries for network communication for Silverlight.
Unity, on the other hand, has its problems currently as unknowns. Am I going to be able to transfer a 2D environment to a 3D-native engine? Am I going to run into some sort of problem where the only solution costs over $500? But at least I can use Lidgren.
Plus, Silverlight adoption seems to be higher than Unity. Then again, not every Silverlight user plays games on SL (probably very few, actually), while virtually every Unity user is playing games, since that's exactly what Unity was built for.
What other problems are there? What do you think I should use, for both my sake and yours (if you decide to play my game once it's ready)?
(Boy, I do talk a big game about my game, when I'm nowhere near ready for even the test version.)