Live data from Hacker News

Google joins .NET Foundation as Samsung brings .NET support to Tizen

techcrunch.com

241–250 of 341 posts

Re: Google joins .NET Foundation as Samsung brings .NET support to Tizen

#241
post #95
post #77

Earlier quoted context omitted.

Java's value is not some inherent superiority of language for mobile development, it is about throwing (100s of) millions of dollars and 100s of engineers to make it work. And I think it remains true for C# also. Unless someone sinks 100s of millions on C# too it seems non-starter to me. By the way Microsoft has already tried mobile ecosystem with .net/C# that did not work out very well.

The transition from Java to C# is pretty easy and pleasant as C# is similar but better.

> C# is similar but better

Oh really? Why?

Re: Google joins .NET Foundation as Samsung brings .NET support to Tizen

#242
post #169

Earlier quoted context omitted.

Silly idea that will never happen, but imagine Google and Microsoft* working together on Android and it becoming actually open (i.e. not a tool to protect google search on mobile) and easily targetable by Java, C#, Go, etc. apps. From a technical point of view it might sound difficult until you realize modern smartphones are veritable beasts compared to computers 10 years ago, and we've had general purpose OSes for d…

I'm sure it was difficult, but you can already ship C# code using Xamarin, no need to wait for Microsoft.

Just noting that Xamarin is part of Microsoft.

Re: Google joins .NET Foundation as Samsung brings .NET support to Tizen

#244
post #2

Nice. Now please make C# a first-class citizen in Android and start to migrate from Java to C#.

Android is deeply dependent on a runtime with Java semantics. The only realistic hope for an implementation language other than Java would be a VM language like Scala or Kotlin. Kotlin is a semi-official alternative, since it is supported by the IDE technology provider.

C# is close enough that ART could likely be extended to encompass it. But it would be somewhat more work than supporting an actual JVM language.

BUT the real question is, with modern IDEs, does it matter? How much do you need a prettier and/or more concise language? And if you do, why not Kotlin?

Re: Google joins .NET Foundation as Samsung brings .NET support to Tizen

#245
IF Microsoft makes another run at phones, the should use Tizen with .NET. That would be very much in the spirit of Android. Every Android OEM/ODM would know how to port it, so it might pull along some 3rd party hardware makers. Most importantly it would lose all the complexity of being Windows Everywhere while still running key MS apps.

Re: Google joins .NET Foundation as Samsung brings .NET support to Tizen

#247
post #11
post #6

Earlier quoted context omitted.

No thanks. I like Java, and esp Java 8 just fine.

Or have both. What's in Java 8 that isn't in C#? And last I checked you couldn't use Java 8 fully on Android (please correct me if I'm wrong).

Java enums are the one thing that I miss in other languages.

Re: Google joins .NET Foundation as Samsung brings .NET support to Tizen

#248

Earlier quoted context omitted.

Just go use Kotlin instead. Much nicer than C#, runs on any JVM.

In some ways it's nicely ahead of C#, but it's still missing some extremely desirable language features, namely async/await/yield.

kotlin 1.1 will have coroutines which cover generators/yield async/await stack-less continuations

https://github.com/Kotlin/kotlin-coroutines/blob/master/kotl...

Re: Google joins .NET Foundation as Samsung brings .NET support to Tizen

#249

Earlier quoted context omitted.

I always hear of the JVM's legendary capabilities, the result of so many million engineer-hours baked in. What would be required to bring the CLR into parity with it?

I don't know, but remember that Android does not run the JVM, it runs the now deprecated Dalvik or the more modern ART, both Google in house projects. None of them have all those million engineer hours baked in, not even close. My guess is that the CLR have more man hours spent on than both those two implementations combined.

This is no longer true.

http://arstechnica.com/tech-policy/2016/01/android-n-switche...

Post reply on HN