4 ms·
Tools to use, in case you aren't aware (like I wasn't, and Googled): * A Mac app - MonoMac 1.0 * An iOS app - MonoTouch * An Android app - MonoDroi
by jedsmith 16y ago
Tools to use, in case you aren't aware (like I wasn't, and Googled):
* A Mac app - MonoMac 1.0
* An iOS app - MonoTouch
* An Android app - MonoDroid
* A Windows Phone app - XNA/Silverlight
* Desktop apps on Linux - Mono/GTK#
* Desktop apps on Windows - regular SDKs
* XBox 360 games - XNA
* A production-level website - ASP.net
* An in-browser applet - Silverlight
* An embedded system (using .NET MF)
Did I get these right?
- daeken 16y agoYep. Also adding to that, Windows Phone 7 games are XNA as well (apps are Silverlight, games are XNA).
- xpaulbettsx 16y agoYep, the only thing I'd add was to specifically call out GTK# on Linux desktop apps
- j_s 16y agohere is miguel's post on the mobile options: http://tirania.org/blog/archive/2011/Feb-14.html http://tirania.org/blog/archive/2011/Feb-14.html i'm more interested in the cost for each; i think monotouch and monodroid will be $400/seat while the rest are free. edit: don't forget about the gaming-oriented platforms using c#: http://tirania.org/blog/archive/2011/Mar-07.html http://tirania.org/blog/archive/2011/Mar-07.html
- blub 16y agoInteresting to see Mr. DeIcaza's reaction. From publishing flawed benchmarks showing c# as faster then c++ back in the day, to jumping with joy to see that an open source project is suffering setbacks. Published on the Gnome com channels too. c# is a nice language, but not a lingua franca. Mono is at best controversial in the oss world, the iOs app gallery is damning the platform by faint praise and Mono on Android does not exist.
- jedsmith 16y agoFor a community that hates FUD about open-source, there is no shortage of FUD about Mono and Miguel de Icaza. It's ironic, really.
- blub 16y agoI have made a series of easily verifiable statements. Please point out where the FUD is in my message.
- migueldeicaza 16y agoIt was only flawed in that I compared C# with SIMD with plain C. But the point was to give a flavor of what our SIMD extensions could do. It would be great to redo the tests, now that we use LLVM as our optimizing compiler, and now that we have an option to disable array bounds checking altogether for speed junkies. Other than the GC intervening and perhaps some extra fine tuning requires for inlining, with LLVM/SIMD/UnsafeArrays we really should not be any different than C++/LLVM.