News for hackers. Stuff that matters.
Re:Android Ported to C# by untog on Tuesday May 01, 2012 @05:09PM (#3916381)
Fascinating, especially in the light of the Google Java issues right now- the performance graphs are just the icing on the cake.

Mono has traditionally had a reputation as being a lot slower than .NET- perhaps that isn't the case any more either? It would be great to see some independent third party figures on this.

It's funny that the MS created C# is one of very few languages that lets you make native apps in iOS, Android and WP.

Re:Android Ported to C# by saurik on Tuesday May 01, 2012 @07:26PM (#3916807)
No one has made this specific point yet, which I've found surprising: it does not matter whether Mono is faster than .NET, it only matters whether Mono is faster than Dalvik.
Re:Android Ported to C# by azakai on Tuesday May 01, 2012 @09:01PM (#3917126)
Not necessarily. High-performance apps on Android are written in C++ and RenderScript anyhow, not Java/Dalvik.
Re:Android Ported to C# by shadowmint on Tuesday May 01, 2012 @09:07PM (#3917147)
Missing the point: you can write a blazingly fast android app in c++ with opengl; but it cant do anything useful because it can't use ui components, and will be stuck with sucky custom in-game ui components which, I think it's fair to say, are universally terrible (the QT port being the one exception to this).

If you can in _any way_ achieve a method of using the existing android ui components and making them faster, this is a massive win.

Re:Android Ported to C# by cageface on Tuesday May 01, 2012 @09:43PM (#3917245)
Actually the trend on both mobile platforms seems to be away from stock components to either heavily re-skinned components or completely bespoke components. Games in particular tend to go their own way on this, probably partly because they need to be x-platform.

Games (and often multimedia creation apps) have been rolling their own UI for a long time.

Re:Android Ported to C# by potatolicious on Wednesday May 02, 2012 @01:55AM (#3917797)
I think you still miss his point - games have been rolling their UIs out of necessity for a long time, in large part because in most OSes (mobile or otherwise) native UI widgets simply do not mix with a big real-time rendered DirectX/OpenGL surface.

So games have always been the fastest, most optimized performers on any platform.

This isn't about games though - this is about regular ol' apps, many of which are incredibly slow and could really use the 8x performance improvement that these folks have been able to achieve.

As a mobile dev myself, I don't think mobile platforms are moving away from Obj-C or Java. Sure, we have a lot of custom-built widgets to overcome shortcomings in what Google/Apple provides, but ultimately they're subject to the same performance limitations that plague the stock widgets. Nobody out there is digging into low-level OpenGL optimizations to write a custom navigation bar, for example.

Re:Android Ported to C# by cageface on Wednesday May 02, 2012 @02:13AM (#3917822)
Sure. Game devs don't build UIs in C++ and OpenGL because it's faster. It's because it's the lowest common denominator on the platforms they care about, which is why I was observing that it's funny that C++ is in a very pragmatic sense more portable than Java now.

Most devs use some kind of wrapper library like Cocos2d to take the pain out of raw OpenGL, of course, and they can usually get by with much simpler library of widgets than the OS itself has to provide.

Re:Android Ported to C# by saurik on Tuesday May 01, 2012 @10:05PM (#3917293)
That is useful for this discussion globally, but is irrelevant for my comment: with that in mind the performance of Mono vs. anything doesn't matter at all, much less specifically vs. .NET (which is the contention of the user I was responding to).
Re:Android Ported to C# by georgemcbay on Tuesday May 01, 2012 @09:25PM (#3917196)
Not if they want to run on Google TV, which doesn't support the NDK.
Re:Android Ported to C# by bad_user on Wednesday May 02, 2012 @02:05AM (#3917815)
Google TV has to support the NDK if they want games for it and I think they do.

IMHO, the biggest problem with Windows Phone 7 (that wasn't emphasized much in all comparisons to iOS or Android) is the lack of support for native code. Whether this was done for legitimate reasons (like portability between ARM and x86) is not really important, what's important is that C++ is the language most games are written in and if you lack the support for it, then most games will only get ported if your platform is a clear winner, which is not the case yet for Windows Phone or Google TV ... therefore from what I know, Windows Phone 8 will have support for native code, because it badly needs it.

So I wouldn't worry too much about it.

Re:Android Ported to C# by nextparadigms on Tuesday May 01, 2012 @09:49PM (#3917260)
Well it doesn't support the Intel Atom ones, but they are going to use ARM soon for all the new ones, and it should work then. If they move fast, it could become quite a nice mini-console platform for set top boxes that you can get for $100, allowing you to play all the native and emulator games from Android on your TV.
Re:Android Ported to C# by rabbitfang on Tuesday May 01, 2012 @06:13PM (#3916606)
Regular Java is currently faster (up to 3x) than C# on mono: http://shootout.alioth.debian.org/u64q/benchmark.php?test=al... ...but obviously on a phone it's going to be Dalvik not regular JVM

We need to consider memory consumption too. Dalvik obviously uses less memory than regular JVM, and probably less than mono if I were to guess.

Re:Android Ported to C# by migueldeicaza on Tuesday May 01, 2012 @10:06PM (#3917300)
Some observations:

In general, HotSpot is a more advanced VM that Mono is. They support dynamic recompilation at a higher optimization level, which we do not.

This is part of the debate in Google vs Oracle. Google could have used HotSpot had they figured out some agreement, but instead ended up with Dalvik which lacks many of the advanced optimizations of HotSpot.

That said, java -server compared against out of the box Mono 2.10.8 is not an apple's to apple's comparison, it is by no means "regular Java". That is Java tuned with some specific parameters. It comes at the expense of interactive time, Mono's default is fast-JIT, and fast startup.

Java -server uses a fixed heap, this means that you must preallocate how much memory the application will use during its entire lifetime. This is good for performance because the GC knows that it only has to scan for example memory between points A and B. 2 comparisons is all you need during GC to scan. Meanwhile, Mono is uses a dynamic heap, which means that it can grow its memory usage based on demand (no need to fine tune the maximum heap every time your app crashes due to a low setting) and can return the released memory to the OS. This complicates GC, because now we cant just compare against 2 values, we need to consider every object in the scope of a series of differently sized heaps.

With Mono 2.11, you can force your app to go fixed heap; The only people that really have a use for this are HPC people and a handful of server people. To be honest, most people dont want to configure the max heap of their server apps by crashing and trial and error.

The second component is that Mono's default is aimed for desktop/mobile configurations, not server loads. If you want to use server loads, run Mono with the --llvm flag: you will have very slow startup times, but you will get code quality that is essentially the same code quality that you get from an optimizing C compiler nowadays.

As for Mono vs Dalvik memory use, in practice people run Mono with Dalvik (Mono for Android), not in standalone mode, so we end up paying for Dalvik's memory footprint. But I agree, it would be nice to find out how much memory it actually uses.

Considering that we get the benefits of a more advanced GC, value types and generics while Java does not, it just seems like we would use less memory for comparable loads.

Re:Android Ported to C# by igouy on Wednesday May 02, 2012 @11:36AM (#3919585)
> java -server compared against out of the box Mono 2.10.8 is not an apple's to apple's comparison, it is by no means "regular Java"

Since at least Java 5 the default on machines with 2 or more processors and 2GB or more memory has been -server. That's what regular out-of-the-box Java is on those machines.

Do many new laptops not have 2 processors and have less than 2GB?

Re:Android Ported to C# by jeswin on Tuesday May 01, 2012 @09:56PM (#3917272)
Well, don't read too much into it.

Here is the Java source for binary-trees, which is 6x faster than c#. http://shootout.alioth.debian.org/u64q/program.php?test=bina... C#: http://shootout.alioth.debian.org/u64q/program.php?test=bina...

Notice that the Java code multi-threaded, while the C# version is single-threaded. And the Q6600 being used there has 4 cores.

Re:Android Ported to C# by igouy on Wednesday May 02, 2012 @11:43AM (#3919637)
Notice that there's another Java program which is single-threaded but still uses more than one-core (figure out why) -

http://shootout.alioth.debian.org/u64q/program.php?test=bina...

Re:Android Ported to C# by raverbashing on Tuesday May 01, 2012 @06:35PM (#3916673)
I'm guessing the JVMs have gone a long way on optimization (or maybe they're using JIT)

Also not sure about how optimized are the C# sources in relation to the Java sources

For example, in the Mandelbrot benchmark there are several differences

- Java uses more arrays

- C# and Java use different break conditions

- Calculations are done differently (with similar results)

Overall they're doing the same things, the C# is more like I remember it, so I'm guessing the Java code has some smart tricks up its sleeve

Re:Android Ported to C# by gravitronic on Tuesday May 01, 2012 @05:36PM (#3916482)
I've been successful in using C++ (with libSDL) to write apps for Android, iOS, QNX (PlayBook) and WebOS (RIP).

Whats more bizarre is that windows phone 7 does not have a development kit for using C/C++. Only C#/XNA. I've heard on HN that this may change for WP8. I hope so.

Re:Android Ported to C# by HardyLeung on Tuesday May 01, 2012 @05:50PM (#3916537)
WP8 and Windows 8 are definitely very C++ friendly. I actually think that C++ may be the language to rule them all as the next generation of web application goes beyond what Javascript can handle. Well, that and C# given Miguel's effort.

I can develop ONE piece of core logic, and have it run on iOS, Android, Windows, Mac, even web (via NativeClient). I posted an AskHN about this earlier today (though not much interest). That sounds like a win.

Re:Android Ported to C# by cageface on Tuesday May 01, 2012 @07:10PM (#3916770)
It's ironic, but C++ does seem to be the best language to write portable code in right now. C is just too low level and everything else is either too slow or tied to one platform.
Re:Android Ported to C# by malkia on Tuesday May 01, 2012 @09:17PM (#3917173)
I don't get much of what you are saying here.. Any examples? Why would C code be less portable than C++? What C++ brings there that is more portable than C?

I would expect the opposite - some runtimes do not allow exceptions, RTTI, dynamic_casting, or simply ABI interworkings due to name mangling and calling conventions for methods. Also virtual inhertiance and it's interworkings (where the this pointer is stored, and how multiple virtual ihneritance is done).

Re:Android Ported to C# by cageface on Tuesday May 01, 2012 @09:42PM (#3917242)
For example: I currently develop my own musical software instruments. This requires a lot of custom DSP code that has to be fast and portable. My only real choice here is C/C++. C is definitely even more portable than C++ but it's too low level (IMO) for application development.
Re:Android Ported to C# by malkia on Tuesday May 01, 2012 @11:56PM (#3917548)
I'm sorry cageface. I've re-read it again, and I appologize.
Re:Android Ported to C# by Tloewald on Tuesday May 01, 2012 @11:13PM (#3917461)
He didn't say C wasn't cross-platform, just that it was "too low level" which I would dispute.
Re:Android Ported to C# by cageface on Wednesday May 02, 2012 @12:03AM (#3917571)
I like C, but you have to ask yourself why it's so rarely chosen for large-scale development. For instance, the Chrome team is certainly smart enough to write Chrome in C, but they chose C++. Why? Surely they understand the tradeoffs and the warts of C++ well enough to make an informed choice.
Re:Android Ported to C# by malkia on Wednesday May 02, 2012 @12:22AM (#3917610)
Firefox was written in C++, and WebKit too (coming from KDE). It could be that C++ is better fit for frameworks, while C for libraries.

V8 is also C++, but lots of other successfull VM's are written in "C"

I like "C" because it's more limiting, hence I won't see templates overused, or latest trick used (SFINAE). It's also easier for me to read.

Also at binary level things are simpler - here is your function, and it's name, it takes this and this as parameter, and returns this and that, also follows this convetion (stdcall, pascal, fortran, etc.)

With C++ my biggest pain has been name mangling. I'm not sure why this was not standartized. It's actually much better that the name of the function automatically contains what types it can take, which would've been much easier for dynamic binding, but then you have GNU, MSVC and others totally differs on how they mangle the name (and from version to version it changes a lot). Also exception handling (mingw/cygwin/msvc - there is big confusion there, and on binary compability level it's hard to combine one with another).

My last show-stopper for C++ was - on this platform you can' t use this feature. For example on certain game consoles exceptions are not allowed. So you go with longjmp/setjmp, but then this would not unwind the stack and call destructors.

Most of all, I got bitten by a heavily templated math library - it was much faster with optimizations than the one before, but without (debug) it was several times slower than same one before it. Why? Because it was relying on inlining everything, and back then gcc for playstation2 was not really inlining everything, even if it was forced.

So every overloaded operation (matrix by matrix, or matrix by vector) was actually function call.

There is another gotcha - sometimes overloaded C++ operators lose their ability to short-cut. For example overloading && and || would not longer short-cut, and many other gotchas.

Most of all, I can't stand boost - it's just too huge.

But I'm totally fine with C++ the simple way (whatever this is) - best example for me is ZeroMQ lib - it's C++ internally, they limit themselves to not use exceptions, and provide "C" interface by default. This makes it very easy to use from other languages - python, lua, ruby, etc.

Re:Android Ported to C# by dlubarov on Wednesday May 02, 2012 @04:58AM (#3918143)
Out of curiosity, which consoles don't support C++ exceptions? PS2? I would say it's a deficiency in the kernel rather than a language problem... but an understandable one, because the runtime support is tricky (see http://sourcery.mentor.com/public/cxx-abi/abi-eh.html).

You're right, a standardized mangling scheme would have been nice... but there's always 'extern "C"' if you need a C++ function from asm or a linker script.

Compilers really should short-circuit &&/||... were you using some kind of experimental compiler?

Re:Android Ported to C# by xyzzyz on Wednesday May 02, 2012 @05:10AM (#3918170)
Compilers cannot short-circuit overloaded && / ||.
Re:Android Ported to C# by malkia on Wednesday May 02, 2012 @06:11AM (#3918310)
Yup. As for exception - it's one of the console out in the market. It might be public information, but I haven't checked.
Re:Android Ported to C# by cageface on Wednesday May 02, 2012 @01:54AM (#3917794)
Yeah sure there are plenty of problems with C++. But I don't think writing in raw C is such a great answer either. What I really want is something in between but no such thing exists.
Re:Android Ported to C# by malkia on Wednesday May 02, 2012 @06:17AM (#3918320)
Same here... There is Vala, but just lazy enough to get into it.

My choice right now is Lua + C - for fun & experimentation. I also dabbled with Common Lisp, but haven't touched code in it in months, might get back at it later...

Re:Android Ported to C# by zanny on Wednesday May 02, 2012 @12:35AM (#3917649)
C++ is a superset of C, so being smart enough to write something in C++ usually implies the ability to write it in C, except with less language verbosity and much easier to read code without glyphic ampersands everywhere meaning different things @.@.

Then again, Linus said C++ developers were dumb and C was better.

Re:Android Ported to C# by steve-howard on Wednesday May 02, 2012 @02:19AM (#3917836)
C++ is not quite a superset of C, though most reasonable C code is valid C++. However, C++ includes a lot of facilities that make programming easier. They're easy to abuse, sure, but in most cases they help make things clearer and simpler.

Boost is almost a second standard library (it is one reference source used in the standards process), and it demonstrates a lot of what's cool and awful about C++. Boost invented a lot of the smart pointer classes that are now standard and save a lot of boilerplate that makes memory management in C annoying. Boost has things like Asio, which lets you write portable synchronous/asynchronous network code. On the other hand, it has Spirit, which is a massive abuse of operator overloading which is at once both impossibly complex and nifty/convenient.

Linus's opinion is worth noting, but he's hardly the best source.

Re:Android Ported to C# by cantankerous on Tuesday May 01, 2012 @07:52PM (#3916880)
I was about to say "Java!!!" then realized how misplaced that statement was given the circumstances. Oracle really is shooting themselves in the foot here.
Re:Android Ported to C# by Tloewald on Tuesday May 01, 2012 @11:15PM (#3917465)
How much does Oracle care about Java as a language or platform? I think they want to sue Google, and the effect on Java is a non issue.
Re:Android Ported to C# by zobzu on Tuesday May 01, 2012 @08:06PM (#3916937)
Bleh, C++ sux to code for =/

I like C# although mono always failed to be nearly as good as .NET and that hindered C# a lot.

If microsoft had realized it and made .NET multiplaform as well, and open source, we may live in a different world today. Heck, Microsft could be leading.

But then again, rewritting the past is easier said than done.

Re:Android Ported to C# by pcwalton on Tuesday May 01, 2012 @08:34PM (#3917037)
Native Client is only enabled for the Chrome Web Store at the moment. But you could use Emscripten.
Re:Android Ported to C# by ConstantineXVI on Tuesday May 01, 2012 @07:26PM (#3916808)
No details on WP8 are out yet, correct? I've heard from the rumor mill that it'll be derived from Win8, but nothing confirmed at all about the SDK.
Re:Android Ported to C# by HardyLeung on Tuesday May 01, 2012 @07:39PM (#3916846)
You are right that details are not out. What I said was purely conjecture on the part of WP8. However, given the roadmap, rumors, hints, discussions, the kind of people in charge (Sinofsky, known .Net hater), etc... I am pretty sure that WP8 will be like W8 in many regard. There were already some rumors (+ non-denial from MS) that WP8 may not run WP7.5 code so this seems a strong indication that it will be more like W8.

And that's not a bad thing. I love C#/.Net (one of my projects, Tagxedo, was built with Silverlight), but given Microsoft doesn't have even the slightess will to push it, we may as well move on, or find some way to ride Mono. C++ is currently on my mind since it covers all ground (sans UI, which you still have to do anyway), probably in a way more straight-forward than Mono.

Re:Android Ported to C# by randomfool on Wednesday May 02, 2012 @02:05AM (#3917816)
Lack of C++ code is a significant limitation for high end mobile games- both from performance and porting costs. MS absolutely knows this (and hears it regularly from game dev houses). Dunno if it'll be solved in WP8, but they have something in the works.

Derived from Win8 != WinRT- could just be the kernel and not app model.

Re:Android Ported to C# by bratsche on Tuesday May 01, 2012 @06:46PM (#3916703)
Interestingly enough, you can also run C# on NativeClient via Mono.
Re:Android Ported to C# by yread on Tuesday May 01, 2012 @05:53PM (#3916553)
Some of the more high profile apps on WP7 have huge native blobs in them. So if youre important enough MS might choose to share their toolkit
Re:Android Ported to C# by cageface on Tuesday May 01, 2012 @08:01PM (#3916919)
How do you bootstrap an SDL app on iOS? I've been considering taking this route myself because I really hate multi-language development and all my DSP code is in C++.
Re:Android Ported to C# by HardyLeung on Wednesday May 02, 2012 @12:19AM (#3917605)
Your objective C code in iOS can directly call your C++ code. Your C++ code just need to be renamed with extension .mm.
Re:Android Ported to C# by cageface on Wednesday May 02, 2012 @02:16AM (#3917828)
Yeah this is how I use my C++ code on iOS now. I'm more interested in exactly what you do to bootstrap a C++/SDL app from nothing.

I guess Armin Ronacher's blog post here makes a pretty good introduction:

http://immersedcode.org/2011/4/25/sdl-on-ios/

Re:Android Ported to C# by jlawer on Tuesday May 01, 2012 @05:40PM (#3916501)
Well microsoft didn't make C# cross platform, that was all really the mono guys.
Re:Android Ported to C# by saurik on Tuesday May 01, 2012 @07:21PM (#3916796)
Back when .NET was still in beta, I was flown up to Redmond to provide some feedback on Managed C++. I specifically asked them why their Socket API was "crippled" in comparison to WinSock (which has some really beautiful mechanisms for handling things like cross-protocol addressing), and the answer I got was "portability to non-Windows systems".
Re:Android Ported to C# by bad_user on Wednesday May 02, 2012 @02:14AM (#3917825)
On the other hand the asynchronous parts of the Socket API was modeled after the Windows kernel, which has true support for asynchronous sockets.

That's one reason why the Mono implementation was always suboptimal, because implementing that API on top of poll, epoll, kqueue and the like is not really straightforward. It's also the reason for why the attempts to build alternative web servers are using bindings straight to libevent, bypassing the socket API.

The original plan was indeed for .NET to be portable to non-Windows platforms, but Windows-specific details have leaked in nonetheless.

Re:Android Ported to C# by MichaelGG on Tuesday May 01, 2012 @09:00PM (#3917123)
Not to detract from the Mono team's awesome achievements but:

- Microsoft has released a cross-platform CLR ("Rotor"). Win/Mac/BSD I believe. - C# and the CLR are ECMA specifications. - A lot of the class libs are definitely not Windows only. - Microsoft also has Silverlight (CLR) running on Mac, if that counts.

The whole .NET stack, apart from some Windows specific libraries (some COM+ management stuff, Win Forms) were definitely made to be cross-platform.

Re:Android Ported to C# by lloeki on Wednesday May 02, 2012 @01:48AM (#3917785)
Not to detract from the Microsoft team, but:

IIRC Rotor was more of a proof of concept, only supporting .Net 1, and later 2.0. It could not be built that easily either, and not bootstrapped.

Early C# (1.1 and 2.0) and the CLR specs were posted to ECMA, then it stopped. I think they published some more of it to ECMA much later, and some of the class platform too but it's still incomplete for .Net to be even remotely called an ECMA standard.

Silverlight does work on Mac, but on Linux you have to use Moonlight.

All in all, the Mono team went much, much farther than Microsoft, but it is impressive for Microsoft to have shown so much effort and so clear intent towards cross-platform support.

Re:Android Ported to C# by moonchrome on Tuesday May 01, 2012 @06:09PM (#3916597)
But they made it an open standard (and are regularly updating it), which goes against the general perception of "M$".
Re:Android Ported to C# by aespinoza on Tuesday May 01, 2012 @05:41PM (#3916508)
You are right, but it is still funny though.
Re:Android Ported to C# by acak on Tuesday May 01, 2012 @05:47PM (#3916529)
Forgive my ignorance. Which application lets you write native iOS apps in C#? Thanks.
Re:Android Ported to C# by untog on Tuesday May 01, 2012 @05:51PM (#3916541)
The guys who made this blog post make some software called MonoTouch.

http://xamarin.com/

It costs $400 for a license, though. But boy I am tempted... I know, I know- you need to go with the native languages for the best experience. But keeping a huge chunk of my codebase between platforms is a very, very interesting idea to me.

Re:Android Ported to C# by Fizzer on Tuesday May 01, 2012 @06:05PM (#3916585)
you need to go with the native languages for the best experience.

With MonoTouch, you still write against the native iOS UI. Therefore, from the user's perspective, your app is native.

Since the UI is the same, the only thing that could be different between an ObjC and MonoTouch app is performance. In my experience there's no noticeable performance hit with MonoTouch except for app startup time (my MonoTouch app takes about 2 seconds to startup on a 3gs)

Re:Android Ported to C# by bratsche on Tuesday May 01, 2012 @06:48PM (#3916707)
MonoTouch does give you a native experience. It's basically a C# binding for native APIs. It also has a few nice extras like MonoTouch.Dialog which provides a much nicer API for doing iPhone dialogs than using UITableView (although you can definitely use the UITableView API directly if you prefer).
Re:Android Ported to C# by fuzzythinker on Tuesday May 01, 2012 @08:35PM (#3917041)
I'll be great if they support F#, but seems like not, 0 answers from googling, except for this request: https://xamarin.uservoice.com/forums/144858-xamarin-suggesti...
Re:Android Ported to C# by migueldeicaza on Tuesday May 01, 2012 @09:54PM (#3917267)
F# on Android is doable, and on our list of things to do.

iOS is more challenging, since F# depends on some dynamic-ish features of .NET that are not currently supported by MonoTouch on iOS.

Re:Android Ported to C# by MichaelGG on Tuesday May 01, 2012 @11:45PM (#3917531)
I'm curious what F# features are you referring to? The generic hash/compare type functions?
Re:Android Ported to C# by malkia on Tuesday May 01, 2012 @11:58PM (#3917558)
Just guessing here, but code generation is not allowed on iOS.
Re:Android Ported to C# by alexrp on Wednesday May 02, 2012 @11:16AM (#3919479)
Right, which means we can't handle generic virtual methods, since we cannot JIT compile them. See: http://docs.xamarin.com/ios/about/limitations#Generic_Virtua...
Re:Android Ported to C# by cageface on Tuesday May 01, 2012 @07:11PM (#3916772)
The thing holding me back is Monodevelop. It's even worse than Xcode.
Re:Android Ported to C# by ConstantineXVI on Tuesday May 01, 2012 @07:28PM (#3916817)
Kind of surprised we haven't seen JetBrains step up with a Mono IDE yet. They've already got the IDEA platform and ReSharper, combining the two seems a logical next step.
Re:Android Ported to C# by henrikschroder on Wednesday May 02, 2012 @06:20AM (#3918325)
Interesting! Going from VS 2005 to 2008 to 2010, Resharper has gone from must-have to nice to not needed anymore for me, since most of the features I relied on have been implemented natively in VS.

But MonoDevelop could sure use a lot of love...

Re:Android Ported to C# by mdaniel on Wednesday May 02, 2012 @01:57PM (#3920330)
I would bet they are bumping up against a developer bandwidth issue. Don't forget, they have about 6 commercial products, plus their own language now (and IDE, natch).

The good news is that the community edition of IJ is Open Source (Apache licensed, IIRC) and there are quite a few existing language editors built on top of it. It isn't a rich client platform à la Eclipse or NetBeans, but I doubt such a thing would be required to win the affections of those who are unhappy using MonoDevelop.

Re:Android Ported to C# by jbrechtel on Tuesday May 01, 2012 @06:45PM (#3916701)
"I know, I know- you need to go with the native languages for the best experience."

What about doing this improves the experience?

Re:Android Ported to C# by stouset on Tuesday May 01, 2012 @06:05PM (#3916582)
A very interesting idea to you, but one your users couldn't care less about.

Never forget about the users.

Re:Android Ported to C# by untog on Tuesday May 01, 2012 @06:08PM (#3916596)
It would be an interesting idea to them if they have an Android phone and I wouldn't have the time to code for two platforms otherwise.

I get that there is a tradeoff involved, but the Mono-x products are in an interesting space. They aren't webviews (like PhoneGap), they aren't a weird JS hybrid (like Titanium)- they're full native experiences. You'll get some newly released features later (I imagine), but the user experience really shouldn't be affected that much.

Re:Android Ported to C# by cageface on Tuesday May 01, 2012 @07:12PM (#3916774)
The Mono guys have been very quick to support new iOS features so far.
Re:Android Ported to C# by josephcooney on Tuesday May 01, 2012 @06:15PM (#3916614)
How is this bad for 'the users'?
Re:Android Ported to C# by bryanl on Tuesday May 01, 2012 @06:54PM (#3916727)
People have responded with MonoTouch, but there is also Unity3d http://www.unity3d.com. You can author games for quite a few platforms with it.
Re:Android Ported to C# by moonchrome on Tuesday May 01, 2012 @06:59PM (#3916740)
Uses same VM - Mono, but has no bindings to native API's like monotouch/droid have
Re:Android Ported to C# by d503 on Tuesday May 01, 2012 @05:50PM (#3916536)
Re:Android Ported to C# by sambeau on Tuesday May 01, 2012 @07:30PM (#3916820)
Re:Android Ported to C# by philjohn on Tuesday May 01, 2012 @05:54PM (#3916554)
MonoTouch
Re:Android Ported to C# by jurre on Wednesday May 02, 2012 @05:53AM (#3918274)
Lately I've been thinking that Haskell might be a really good language to write cross platform native apps in. It's super fast but also high level so you can be really productive. I know there are some libs for iOS but if some sort of cross platform framework existed I think it could be really powerful.