4 ms·

That's JNI pain + C++ pain (this is coming from a guy who just did a C++ project full time for >year - C# and C++ aren't in the same league when it comes to pro

That's JNI pain + C++ pain (this is coming from a guy who just did a C++ project full time for >year - C# and C++ aren't in the same league when it comes to productivity) - and C++ has no access to android java api - xamarin is just a whole different kind of solution to this - you can literally have all code in one language across all platforms - C++ can't do this without a custom UI like QT

pjmlp 11y ago
What you are forgetting is that some guys at Xamarin already went through that pain for their customers. And if there is the need to use something that they have yet to wrap, there isn't any difference between C# and C++. Also in Android there is the additional pain of synchronising the .NET and JAVA GCs. C++ is a good language, except for the warts introduced due to C copy-paste compatibility.
- eropple 11y ago
  C++ is a straight-up awesome language, on that you and I fully agree. And I have been there with regards to the teeth-pulling pain of Xamarin projects when you want to do something nontrivial. So it kind of pains me to disagree with you, but I do. C++ is awesome. I love it. But I also recognize that I barely trust myself to write it, after ten years or so of exposure and a few years of steady writing it. I don't trust off-the-rack mobile developers to write it safely and correctly. To that end, something like Xamarin or the RIP'd RoboVM provide a significant benefit: by offering the kind of guardrails that C++ can't, they do significantly improve the ability of people who don't eat and breathe this stuff to get something out the door. (Whether or not that's a desirable trait...reasonable people can differ. But it is in demand.) Sure, Xamarin has done a lot of that work--but that's also kind of the point in the first place.
  - pjmlp 11y ago
    Don't get me wrong, I would like that more type safe languages were available for native cross platform development and I am getting myself deeper in Xamarin. However one thing that my likeness for Turbo Pascal and Oberon teached me was that making applications with languages which aren't first class on the platform SDKs opens the door to situations like these. So I rather be more pragmatic, even if it goes a bit against to my preferences and keep my code free of company politics, which may lead to porting the application to other languages.

pjmlp 11y ago

What you are forgetting is that some guys at Xamarin already went through that pain for their customers. And if there is the need to use something that they have yet to wrap, there isn't any difference between C# and C++. Also in Android there is the additional pain of synchronising the .NET and JAVA GCs. C++ is a good language, except for the warts introduced due to C copy-paste compatibility.

eropple 11y ago
C++ is a straight-up awesome language, on that you and I fully agree. And I have been there with regards to the teeth-pulling pain of Xamarin projects when you want to do something nontrivial. So it kind of pains me to disagree with you, but I do. C++ is awesome. I love it. But I also recognize that I barely trust myself to write it, after ten years or so of exposure and a few years of steady writing it. I don't trust off-the-rack mobile developers to write it safely and correctly. To that end, something like Xamarin or the RIP'd RoboVM provide a significant benefit: by offering the kind of guardrails that C++ can't, they do significantly improve the ability of people who don't eat and breathe this stuff to get something out the door. (Whether or not that's a desirable trait...reasonable people can differ. But it is in demand.) Sure, Xamarin has done a lot of that work--but that's also kind of the point in the first place.
- pjmlp 11y ago
  Don't get me wrong, I would like that more type safe languages were available for native cross platform development and I am getting myself deeper in Xamarin. However one thing that my likeness for Turbo Pascal and Oberon teached me was that making applications with languages which aren't first class on the platform SDKs opens the door to situations like these. So I rather be more pragmatic, even if it goes a bit against to my preferences and keep my code free of company politics, which may lead to porting the application to other languages.