News for hackers. Stuff that matters.
Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @11:07AM (#6726088)
The scenario I keep hoping for is: ms buys xamarin, MIT licenses the entire xamarin cross platform ecosystem (while charging for build services like phonegap does), adds a "compile to html/css/js" feature so you can write your web frontend in c#.

This scenario leads to the following: C# wins as the "cross platform mobile language," window phone is the default first environment for cross platform apps, and as developers we get an elegant "write once* run everywhere" that's based on c#.

The asterisk: once plus ui customizations on each platform, so more like write (1 + (.1 * num_non_wp8_platforms)) times

Unfortunately, though I think these moves would make ms a dominating player in mobile and web for decades, I doubt they'll do this.

Re:Microsoft and Xamarin partner by shadowmint on Wednesday November 13, 2013 @11:15AM (#6726153)
There is no way that'll ever happen.

Much more likely; Xamarin is acquired, monodevelop development halts and the Xamarin offerings become VS pro features, giving Microsoft a foot hold in the mobile space (which they desperately need) and maintain VS revenue.

It's arguably not a terrible direction for things to go... If, unlike me, you dont passionately despise VS. :p

Re:Microsoft and Xamarin partner by LordIllidan on Wednesday November 13, 2013 @12:34PM (#6726795)
What about iOS where you definitely need OSX? Xamarin has some integration with VS (I've never used it myself), but it still needs a mac with OSX installed to work (even if it's just a macmini somewhere.

If Microsoft does buy Xamarin, I'd like the following to happen:

Xamarin and TestCloud become much cheaper. More attention given to the IDE - fix the hell out of it Better documentation

I also think it's a fantastic way of encouraging developers to work on WP 8. The less code you need to port from Objective-C/Java to .net, the better.

Re:Microsoft and Xamarin partner by skrebbel on Wednesday November 13, 2013 @02:19PM (#6727665)
> What about iOS where you definitely need OSX?

I predict Xamarin Build Cloud.

Devs who want to make WP apps on Mac or Linux have exactly thr same problem, just the other way around. A well integrated, "it just works" cross-platform build solution, straight from the IDE, has a lot of market value and fits perfectly in Xamarin's portfolio, Microsoft or not.

Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @05:18PM (#6729063)
Not quite the same problem as MS officially supports running win7/8 in a virtual machine.
Re:Microsoft and Xamarin partner by keithwarren on Thursday November 14, 2013 @08:25AM (#6732094)
I actually ask Miquel about this very thing at Evolve last April and he said they would love to do something like that but Apple TOS forbid it. That is your impediment.
Re:Microsoft and Xamarin partner by LordIllidan on Wednesday November 13, 2013 @04:34PM (#6728726)
That would be incredible. And they could use their test cloud infrastructure for automatic testing upon build..
Re:Microsoft and Xamarin partner by antihero on Thursday November 14, 2013 @03:33AM (#6731287)
It's an utterly terrible direction to go. It's basically forcing people back onto the Windows stack which we've been trying so hard to get away from.
Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @11:25AM (#6726251)
Sadly, I agree with you. I think Ms will continue to play the short game and wonder why they struggle to win the web and mobile.

The irony is, they'll give you $200 of swag at every event to grow their ecosystem 1 dev at a time, but they won't open source to grow their ecosystem 10x.

Re:Microsoft and Xamarin partner by PallarelCoedr on Wednesday November 13, 2013 @12:59PM (#6727011)
They have open-sourced quite a lot (aspnet webstack, reactive extensions, etc). The problem is that a lot of their compiled binaries, delivered via nuget packages have been restricted to windows. This is slowly being undone ( http://blogs.msdn.com/b/dotnet/archive/2013/11/13/pcl-and-ne... ).

Another problem is that they don't run their open source projects in an open manner. Contributing requires a CLA and a signature from your boss. Issues and planning are often behind closed doors, but that seems to be slowing changing too (see KatanaProject / signalr).

If they really wanted to grow their ecosystem 10x, and give windows phone the possibility of a fighting chance, making VS Pro free would be the required.

Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @01:52PM (#6727423)
I've never had to work so hard to find out _what_ license they're releasing things under. I followed about seven links and finally got it.

EDIT: Apparently they haven't updated their nuget packages and some of these components truly are licensed under FOSS, per: http://weblogs.asp.net/scottgu/archive/2012/03/27/asp-net-mv... and https://news.ycombinator.com/user?id=adolfojp

The license that used to cover all of these, and that may still cover some of the components is this:

http://www.microsoft.com/web/webpi/eula/aspnetcomponent_rtw_...

I like to think of things as copyright, copyleft and copy middle. This looks like an entirely new beast: copyquagmire

A few pieces of the license:

* For any Distributable Code you distribute, you must · add significant primary functionality to it in your programs; ... · indemnify, defend, and hold harmless Microsoft from any claims, including attorneys’ fees, related to the distribution or use of your programs. *

So, if you redistribute these libraries, you agree to be on the hook for MS legal bills.

* Distribution Restrictions. You may not · modify or distribute the source code of any Distributable Code so that any part of it becomes subject to an Excluded License. An Excluded License is one that requires, as a condition of use, modification or distribution, that

· the code be disclosed or distributed in source code form; or

· others have the right to modify it. *

So it is anti-GPL. I personally think this is a good thing, I hate the copy-virus in the GPL. Maybe this is even a poison pill that invalidates GPL code in a project, thereby protecting you from inadvertently letting your code fall under GPL (which I would consider to be a good thing). Whichever clause wins, this is a quagmire.

Lets continue.

* you must comply with any technical limitations in the software that only allow you to use it in certain ways. You may not

· work around any technical limitations in the software;

· reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;

· publish the software for others to copy;

· rent, lease or lend the software;

· transfer the software or this agreement to any third party; or

· use the software for commercial software hosting services. *

So, basically you can't modify it or change it.

* BACKUP COPY. You may make one backup copy of the software. You may use it only to reinstall the software. *

Why the hell is this in an "open source" license?

This isn't an open source license, this is a free commercial license with a bit of lipstick, a wink, and a head-fake towards openness.

Thankfully, it seems other divisions of msft (F# for instance) use the Apache License V2 which is in fact a copy-middle free as in beer and freedom open source license.

Re:Microsoft and Xamarin partner by adolfojp on Wednesday November 13, 2013 @02:20PM (#6727677)
>I've never had to work so hard to find out _what_ license they're releasing things under. I followed about seven links and finally got it.

Microsoft's open source software repository is codeplex. If you go to codeplex you'll find out that the projects that you mention are Apache 2 licensed too.

http://aspnetwebstack.codeplex.com/license

http://entityframework.codeplex.com/license

Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @02:24PM (#6727713)
Thank you for the correction!

I don't think it is unreasonable to believe that the license in the package manager operated by the company who is granting the license would be accurate.

Re:Microsoft and Xamarin partner by adolfojp on Wednesday November 13, 2013 @02:28PM (#6727757)
I agree with you 100%. I don't know why they're releasing the source code and the binaries under different licenses so hopefully someone who knows this will reply to these comments. If I find out I'll let you know.
Re:Microsoft and Xamarin partner by belorn on Thursday November 14, 2013 @03:10AM (#6731226)
Congratulations, you clearly found your perfect license. Since you clearly hate being given the right to copy, modify and redistribute (as in the GPL), have fun using a license that forbids modification, and only give you max 1 backup copy.

Oh wait, you want to make modifications, and then sue people who then dare to copy, modify or redistribute your version? Pity you can't use that GPL compatible Apache 2 licensed code. Better use that non-compliant free commercial license instead.

Re:Microsoft and Xamarin partner by thatthatis on Thursday November 14, 2013 @11:10AM (#6733087)
Uhm, what?

To me, perfect licences are: BSD, MIT, Apache2, WTFPL

I like copy middle far far better than copy right or copy left.

My entire comment was about how bad the MS free commercial license was and how I wished it was a real FOSS license. There was a tangent in there about hating the copy-virus of the GPL, but that was an aside.

Re:Microsoft and Xamarin partner by belorn on Friday November 15, 2013 @08:54AM (#6739383)
If you want to comment about how bad the MS free commercial license is, you should not bundle it with your desire to redistribute other peoples software and then sue your users if they dare to do the same by copy, modify or redistribute your version.

It takes away from your main arguments and distracts.

Re:Microsoft and Xamarin partner by tbirdz on Wednesday November 13, 2013 @12:20PM (#6726669)
F# is open source, and available on github.
Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @12:25PM (#6726714)
I haven't investigated F# much. I'll take a look.
Re:Microsoft and Xamarin partner by adolfojp on Wednesday November 13, 2013 @12:57PM (#6726992)
They have open sourced a bunch of their dev products including ASP.NET MVC, the Entity Framework, Web API, Web Pages, the Razor view engine, and SignalR.

And instead of reinventing libraries like they used to they started to embrace some open source libraries like modernizr, jQuery, Bootstrap, and Json.NET.

And to promote their Windows Azure initiative they released a platform installer that allows you to install open source products like PHP, MySQL, and Wordpress on your Windows box with just a few clicks.

Microsoft is a big company with many different clashing cultures. As a result some divisions shower you with software goodness and others with patents and lawyers.

Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @02:01PM (#6727509)
ASP.NET MVC, the Entity Framework, Web API, Web Pages, the Razor view engine, and SignalR are under this license: http://www.microsoft.com/web/webpi/eula/aspnetcomponent_rtw_...

Which I commented on here: https://news.ycombinator.com/item?id=6727423

At best, they are under a free commercial license. They are not available under FOSS licenses.

Re:Microsoft and Xamarin partner by adolfojp on Wednesday November 13, 2013 @02:11PM (#6727576)
Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @02:22PM (#6727703)
The current license linked at http://www.nuget.org/packages/EntityFramework/ is the one I commented about.

I'm glad to see they're moving more of these technologies over to truly FOSS.

Which pieces are on which license if you get it from which place?

I'll update the linked comment with that blog post -- I seriously scoured the other press release and couldn't find which license these were released under.

Re:Microsoft and Xamarin partner by knocte on Thursday November 14, 2013 @05:48AM (#6731649)
You guys are talking about different things.

The licences of the projects (EntityFramework, ASP.NET) are opensource, but the licence only applies to the sources.

Nuget packages, however, are binary. And they might have a different licence. So to avoid the latter, you just need to compile the sources yourself instead of using the Nuget packages.

EDIT: actually, the last paragraph is not true anymore, thanks to this: http://blogs.msdn.com/b/dotnet/archive/2013/11/13/pcl-and-ne...

Re:Microsoft and Xamarin partner by thatthatis on Thursday November 14, 2013 @11:13AM (#6733105)
I think we can all agree, how these are licensed is currently confusing.
Re:Microsoft and Xamarin partner by sanxiyn on Wednesday November 13, 2013 @12:26PM (#6726729)
TypeScript is open source (Apache 2.0).
Re:Microsoft and Xamarin partner by marshray on Thursday November 14, 2013 @01:07AM (#6730859)
Among other things mentioned here, .NET Micro Framework is now Apache 2.0 license http://netmf.codeplex.com/
Re:Microsoft and Xamarin partner by AUmrysh on Wednesday November 13, 2013 @11:14AM (#6726135)
If they came up with a unified, cross platform, UI format, it would make it so much easier. As it is now, you have to write your own view for each platform, instead of being able to use generic objects (buttons, cells, text, images, etc.) which wrap the native ones.

If they did that, they would very likely, as you say, dominate mobile for a long time. Nothing is more frustrating than jumping between android XML, Java, and eclipse (or whatever) and XCode, OBJ-C, and the iOS UI, while trying to not go insane.

Re:Microsoft and Xamarin partner by cek on Wednesday November 13, 2013 @01:25PM (#6727215)
"Write Once Run Anywhere" is Anti-Customer. [1]

Because of continued platform fragmentation WORA has been, is, and always will be a pipe-dream. People have been attempting to create WORA technologies since the beginning of time and they have all failed.

The nice thing about Xamarin's model is your UI code uses native constructs, allowing for the best possible, most natural (to the user) experience. But you get to stick with one language (if you want) and your core code is very portable.

[1] http://ceklog.kindel.com/2013/02/21/james-gosling-screwed-us...

Re:Microsoft and Xamarin partner by saidajigumi on Wednesday November 13, 2013 @04:39PM (#6728755)
> People have been attempting to create WORA technologies since the beginning of time and they have all failed.

Nice straw-man. Unity 3D does WORA very, very well. It's been used successfully for cross-platform development by many shipped products. To my initial astonishment, all built on Mono/C#.

This doesn't absolve the developer from QA for the targeted platforms, and this is where fragmentation is the killer IMO. That said, Unity provides a huge amount of leverage and tooling in support of seamless cross-platform deployment.

Re:Microsoft and Xamarin partner by fidotron on Wednesday November 13, 2013 @05:09PM (#6728989)
It's not a straw man at all as products with Unity aren't making any effort to appear native to the platform they're running on.

Unity is also notoriously painful when it comes to 2D UI style work as well, which is why there's a tools ecosystem around it just to deal with that problem.

Re:Microsoft and Xamarin partner by Karunamon on Wednesday November 13, 2013 @06:40PM (#6729443)
Does the enduser care? When I boot into a Unity game, it has its own UI and menu system, usually full-screening above the OS.

Saying that the apps generated don't look "native" doesn't support the assertion that WORA is a "failure". Doubly so considering the ubiquity of Java.

Re:Microsoft and Xamarin partner by cmircea on Wednesday November 13, 2013 @07:35PM (#6729708)
We're not talking about games here, we're talking about regular apps, with a regular UI, which needs to be native.

Otherwise it sucks.

Re:Microsoft and Xamarin partner by nightski on Thursday November 14, 2013 @12:33AM (#6730760)
So the web sucks?
Re:Microsoft and Xamarin partner by cmircea on Thursday November 14, 2013 @01:41AM (#6730969)
Yes.

Well the web doesn't have a native UI. But iOS and Android DO have one.

Re:Microsoft and Xamarin partner by alandarev on Friday November 15, 2013 @07:46AM (#6739082)
Games are way different segment. In a game you would like to impress person with non standard interface. In fact a game running on standard UI looks cheap and is a signal of design failure / low budget.

While the applications are other way around. New customers do not want to spend more than a minute to get familized with the interface. Moreover, your custom UI interface will be competing with Apple/Google designer's budget.

Re:Microsoft and Xamarin partner by bluefinity on Wednesday November 13, 2013 @07:40PM (#6729727)
Unity now has support for proper 2D in the engine. See here: http://unity3d.com/unity/whats-new
Re:Microsoft and Xamarin partner by gdc on Wednesday November 13, 2013 @10:40PM (#6730384)
Yes... for the past...... 24 hours.
Re:Microsoft and Xamarin partner by forgottenpaswrd on Thursday November 14, 2013 @04:08AM (#6731377)
"Nice straw-man. Unity 3D does WORA very, very well. It's been used successfully for cross-platform development by many shipped products. To my initial astonishment, all built on Mono/C#."

Not true. Unity engine is made using c/c++. You control those components using Mono/c#, which is totally different.

If Unity was made in Mono, it would be 1 frame per second. We made lots of experiments using mono for doing 3d and animation in our company as it is fast to program with, but with all the market machine of MS, c# is not designed for some things, but some people just can't stop trying to use the only hammer they have.

Re:Microsoft and Xamarin partner by fidotron on Wednesday November 13, 2013 @01:47PM (#6727383)
On top of that the proportion of code/development time involved with the UI or OS integration on a mobile client tends to dwarf the rest of the project, meaning reusing the guts is nothing like as big a net gain as it would appear.
Re:Microsoft and Xamarin partner by w0rd-driven on Wednesday November 13, 2013 @11:43AM (#6726388)
I think XAML is that format, but it isn't without its pain points. You pretty much can't do animation without a tool like Blend unless you're a sadist.

It looks like Xamarin uses .AXML for Android (maybe a XAML flavor) but has to adhere to Interface Builder for iOS (http://docs.xamarin.com/guides/cross-platform/application_fu..., specifically the Visual Designer section). XAML likely won't gain any traction on those platforms though due to NiH on all sides. HTML/CSS is likely as close as we get for now but that isn't a "native view" in any of the platforms mentioned.

Re:Microsoft and Xamarin partner by skrebbel on Wednesday November 13, 2013 @02:28PM (#6727751)
.AXML has no relation to XAML at all. It's just plain Android layouts: when doing plain Java Android dev, they're just .xml files. I believe that Xamarin made up a new extension for them because it allows them to easily associate the file extension with a special editor in the IDE (Visual Studio and Xamarin Studio/MonoDevelop).

Xamarin's Android interface builder is actually remarkably decent.

Re:Microsoft and Xamarin partner by jpobst on Wednesday November 13, 2013 @04:04PM (#6728496)
Hah, that's exactly why I did it. :)

I couldn't easily associate .xml with the designer in VS since everyone uses .xml.

Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @11:21AM (#6726209)
I think the key to a unified cross platform ui format is going to be another layer of separation of concerns, similar to HTML/CSS.

I think this because I believe that platform-level ui look and feel differences are going to be with us for a long time.

I think you can standardize "what it does" and "how it does it", but you'll have to keep platform specific "how to invoke" and "how it looks" for a long time.

Maybe a MVCP paradigm is what we need, where the controller is split into common controller and platform controller

Re:Microsoft and Xamarin partner by zanny on Wednesday November 13, 2013 @01:49PM (#6727396)
> able to use generic objects (buttons, cells, text, images, etc.) which wrap the native ones.

You mean QML?

Re:Microsoft and Xamarin partner by pnathan on Wednesday November 13, 2013 @11:43AM (#6726391)
That would be horrible.

C# is a pretty weak language[1], and .NET is layers of bad design choices (both of these problems stem from a aggressive OO design methodology combined with poor API taste + a policy of "never break".

Not only that, Microsoft is a monopolist by character, and an unpleasant competitor. It would be a disaster for the world if they regained dominance (much like other companies, but MS brings a particularly domineering flavor).

[1] It's adequate. It gets the job done, adequately. It doesn't shine except in being adequate. I would rather use pretty much any open source language than a .NET one.

Re:Microsoft and Xamarin partner by gjulianm on Wednesday November 13, 2013 @11:52AM (#6726456)
Well, I think MS has been drifting away from their monopolistic character. Look at Azure, for example. They give you documentation even to develop and deploy with Java. That's not something I'd expect from the old MS.

Apart from that, why is C# a weak language? I think it shines in features: dynamic typing, code by contracts, runtime code generation (you can generate assemblies in execution time with System.Reflection.Emit), LINQ... you can even use it as a functional programming language. I wouldn't say C# is pretty weak.

Re:Microsoft and Xamarin partner by michaelwww on Wednesday November 13, 2013 @12:59PM (#6727007)
> C# is a pretty weak language[1]

I like how you give a citation then cite yourself

Re:Microsoft and Xamarin partner by was_hellbanned on Thursday November 14, 2013 @12:50AM (#6730808)
Footnotes are used for more than just citation.
Re:Microsoft and Xamarin partner by michaelwww on Thursday November 14, 2013 @12:58AM (#6730840)
My tone was meant to be gently humorous, not seriously precise. I was reminded of a guy on another site who was backing up his arguments with quotes from a book -- that he wrote. When someone called him on it he didn't miss a beat; he said it was a good book four years ago when he wrote it and still a good book worth quoting.
Re:Microsoft and Xamarin partner by pnathan on Thursday November 14, 2013 @11:32AM (#6733245)
Sometimes parentheticals simply take away from the point of a paragraph.
Re:Microsoft and Xamarin partner by depr on Wednesday November 13, 2013 @04:42PM (#6728772)
-- Michael Scott
Re:Microsoft and Xamarin partner by thatthatis on Wednesday November 13, 2013 @11:49AM (#6726428)
Of Java, C#, and ObjectiveC the language I most want as the common language is Python.

That not being an option, C# is decently close to python in expressiveness, certainly better than the other two, and in my appraisal actually a pretty nice language.

Re:Microsoft and Xamarin partner by CmonDev on Wednesday November 13, 2013 @12:53PM (#6726956)
Supports both kinds of typing and most functional features. Let's just see what happens when Roslyn finally gets done (something that keeps them busy from keeping innovating on language side)!
Re:Microsoft and Xamarin partner by rayiner on Wednesday November 13, 2013 @12:37PM (#6726825)
What's wrong with the CLR? It seems to be better for a cross language runtime than the JVM.
Re:Microsoft and Xamarin partner by jlgreco on Wednesday November 13, 2013 @03:58PM (#6728456)
CLR does seem much better than the JVM, but my dislike of it comes from what I see of it in the wild. Any randomly chosen JVM program in the real world has a much greater chance of running on my platform of choice than anything that was developed for the CLR. The JVM has a culture of writing things that turn out to actually be cross platform, the CLR does not seem to.

I can count on one hand the programs written in C# that I use in Linux, and those projects have to explicitly support Linux. Compared to JVM targeting projects where the experience is typically "Linux? Well shit, I don't know. Here's the jar, try it out. Oh, it works? Great!"

If I were writing a new language and had to pick one to target, from a technical perspective the CLR would seem to be the clear choice. But I don't think that is the perspective most people are coming from.

Re:Microsoft and Xamarin partner by stusmall on Wednesday November 13, 2013 @01:09PM (#6727062)
I see people say this but I've never seen an actual reason. I know the CLR was built with this in mind with things like CLS but that doesn't seem like that huge of a deal. There are also some naughties in the JVM like how generics are handled, but that seems more like knocks against the JVM as a whole rather than its cross langauge support.

So legitimate question, is the CLR better than the JVM at cross language support and if so what makes it better?

Re:Microsoft and Xamarin partner by pjmlp on Wednesday November 13, 2013 @01:59PM (#6727493)
> So legitimate question, is the CLR better than the JVM at cross language support and if so what makes it better?

Yes in the early days, because JVM was initially designed just for Java and many bytecodes are directly related to Java semantics.

Meaning any language that targets the JVM has to adapt their semantics to Java semantics at the bytecode level, hence the tricks mapping closures to anonymous classes as one example from many.

This got better with the introduction of new bytecodes in Java 7 and the upcoming Java 8, but it is still a Java VM at heart.

The CLR was designed as language agnostic, meaning its design had to support a good implementation of VB, C# and C++ on day one, alongside other languages from Microsoft partners like Eiffel and COBOL as two possible examples.

There is inclusive a .NET ABI for interoperability between languages, CLS (Common Language Specification).

So the bytecode is much more generic and more low level than the JVM bytecode is.

Then thanks to the work done on IronPython and IronRuby, it got the DLR part with allows for better performance of dynamic languages implementations. Since initially CLR was mostly targeted for strong typed languages.

Nowadays both platforms are quite similar in terms of language support.

Re:Microsoft and Xamarin partner by rayiner on Wednesday November 13, 2013 @01:46PM (#6727380)
Tail calls, value types, and generics are the big ones.
Re:Microsoft and Xamarin partner by bad_user on Wednesday November 13, 2013 @06:25PM (#6729394)
Counter examples ..

1) On top of the JVM we've got Scala, Clojure, JRuby, Jython, Groovy, Fantom, very successful, very active, with big communities.

2) On top of the CLR, we've got IronRuby dead, IronPython dead, Clojure.NET almost dead, Scala.NET dead. VB is C# with a different syntax. The only partial success story is F#, executed by Microsoft and I say partial because its impact is less than Clojure, Scala or JRuby, in spite of Microsoft promoting it.

So you see, something is wrong with your assessment and you've been listening too much to marketing pamphlets.

Re:Microsoft and Xamarin partner by rayiner on Wednesday November 13, 2013 @07:14PM (#6729610)
That's not a technical argument. Nobody wants to build on the CLR because its closed source and Microsoft tightly controls it. But the person I replies to claimed it was full of design mistakes, which is different.
Re:Microsoft and Xamarin partner by bad_user on Thursday November 14, 2013 @04:22PM (#6735675)
True, I never read the parent comment, sorry.

The CLR is definitely not full of design mistakes, it's actually quite awesome. But in terms of technical arguments, the JVM is better for dynamic languages, as it can do all sorts of optimizations at runtime that the CLR is not capable of. It's not that Microsoft couldn't improve it, but C# would have nothing to gain as it was designed to not need runtime optimizations (e.g. on the JVM, AOT compiler optimizations can actually get in the way, whereas the C# engineers focus on optimizing the compiler). And the new InvokeDynamic from JDK 7 is amazing. Starting with Java 8, it will even have benefits for static languages, like Scala. Scala for example has the notion of "lazy val", which are final references initialized on first access. In the current implementation, lazy vals have a performance penalty on access, as the generated code implies synchronization on the underlying reference, however Java 8 will make it possible to declare the generated values as being effectively constants.

The JVM also has a more capable garbage collector(s) for more wasteful languages. It makes a world of difference for languages like Scala or Clojure (e.g. functional languages use a lot of persistent immutable data-structures which generate a lot more junk than their imperative counterparts).

On the community side, for the JVM there are more capable libraries for generating bytecode. Also the ECMA standard has been kind of incomplete. For example Mono had to use for a long time their own format for the debugging symbols, while slowly reverse-engineering Microsoft's format. The debugging symbols on the JVM are documented and directly a part of the generated bytecode. Sun made many good choices here too. A JAR is just a zip containing .class files and other resources. It's definitely easier to generate JARs than it is to generate DLLs. I think language developers have a much easier time generating code for the JVM.

There is one feature of the CLR that stands in the way of dynamic languages and that is the reified generics support. The JVM has fewer restrictions, although in truth both suck for languages that are not Java or C#.

Re:Microsoft and Xamarin partner by tedunangst on Thursday November 14, 2013 @12:09AM (#6730661)
IronPython is dead?
Re:Microsoft and Xamarin partner by pnathan on Thursday November 14, 2013 @08:49AM (#6732208)
Technically, I dunno. But I can pick up JVMs and JVM apps for pretty much any OS I want, can't say the same for Mono/.NET. I'd rather use the JVM for cross-platform JIT language work because of this. Further, the JVM has a broad base of development and support; many companies build products around it & there are multiple JVMs. That isn't really the case for .NET.

So in a head to head on tools + community + buyin from multiple vendors, the JVM wins, hard.

Re:Microsoft and Xamarin partner by tracker1 on Wednesday November 13, 2013 @02:44PM (#6727899)
P/Invoke vs JNI is probably the single biggest win for CLR... It's simply much easier to integrate with system libraries in .Net than it is with Java.
Re:Microsoft and Xamarin partner by ygra on Wednesday November 13, 2013 @04:20PM (#6728637)
Re:Microsoft and Xamarin partner by tracker1 on Thursday November 14, 2013 @12:27PM (#6733664)
Yeah, and that came out in 2007.. 6 years or so after .Net and Mono were started...
Re:Microsoft and Xamarin partner by Zigurd on Wednesday November 13, 2013 @11:56AM (#6726474)
Some people prefer C# over Java and VS over Eclipse, and the Xamarin team will probably do a better job of making cross-platform work than most others.

I suspect it will still lead to many lowest common denominator apps, but it's not like Android doesn't suffer from iOS-portitis and hordes of shoddy apps for other reasons, anyway.