News for hackers. Stuff that matters.
Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by justthistime_ on Sunday June 28, 2015 @11:38AM (#9793882)
With .NET Core, is there any reason to not just drop IL2CPP completely?

(The whole thing only existed in the first place because they are stuck on a completely outdated Mono version, due to Xamarin changing the license of newer Mono versions trying to extract money from Unity.)

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by carussell on Sunday June 28, 2015 @12:01PM (#9793964)
Can we kill off the Mono libel already?

Mono changed the license so that it could be used in Unity to begin with. Mono was available under a copyleft license. To everyone. Including Unity. Unity couldn't/wouldn't accept it under those terms, so folks at now-Xamarin said, "We'll offer it to you under a commercial license if you won't take the copyleft offering." That's standard fare. Unity said, "Okay, deal." Mono continued to improve over the years. Unity was interested in those improvements. Mono said, "Okay. You can get those under a commercial license, too." Unity balked.

So what we're really talking about is that Unity wants the improvements that have been made to Mono, but doesn't want to pay for them.

Get this: They're still free at any point to accept Mono under the copyleft license that's available to literally everyone, but they won't accept it under any terms other than their own. That's it.

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by justthistime_ on Sunday June 28, 2015 @12:14PM (#9794003)
Dude, relax?
Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by azakai on Sunday June 28, 2015 @12:13PM (#9793999)
That seems like a very unfair description of the situation.

Do you know the specific licensing terms that Xamarin offered to Unity? Probably none of us here do. Given that, why would you assume Unity was the unreasonable party, and not Xamarin?

Regarding the copyleft license, while it is an option for everyone in general, it isn't an option for Unity, which needs to ship on platforms that do not allow such licenses (iOS, game consoles). Products like Unity will always need a commercial license as long as such platforms exist.

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by carussell on Sunday June 28, 2015 @12:24PM (#9794033)
> Given that, why would you assume Unity was the unreasonable party, and not Xamarin?

I don't know what this means. What we know of the situation is that Unity doesn't want to pay a commercial license for Mono. This is even the way that pro-Unity/anti-Mono folks frame the situation. What do you have in mind here?

> Regarding the copyleft license, while it is an option for everyone in general, it isn't an option for Unity

That's all well and good, but it doesn't have much to with any obligations Mono has. Those are completely synthetic restrictions that the platform vendors are placing on the people targeting them. How does Mono get the blame for Apple and Nintendo's choices here? Why do Apple and Nintendo get treated as bedrock? Even so, that's bedrock that Unity knows they're working with. It's their choice to target those platforms.

EDIT:

> That seems like a very unfair description of the situation.

Unfair. Every reference to the Unity/Mono relationhip I've ever come across has been from someone who heard Unity's creative retelling of the conflict and parroted it exactly, down to overtly identifying Mono as the bad guy.

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by azakai on Sunday June 28, 2015 @12:28PM (#9794052)
It means: Xamarin offered a commercial license to Unity for $X under Y terms. We don't know what X and Y are, since this was not a public negotiation. X and Y could be reasonable, or they could be totally unacceptable. They could be offered in good faith, or they could not.

We just don't know the answer, and you're assuming the party offering X and Y is reasonable. But it might not be. We don't know.

edit to your edit: if you heard people on the internet being wrong in some way, that doesn't justify you being wrong in the opposite way.

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by carussell on Sunday June 28, 2015 @01:00PM (#9794162)
There's no "opposite" emanating here. I'm making no assumptions beyond what we do know, and what I describe is what we do know, sans Unity's spin. There's only me saying, "I'm a little sick of seeing Unity's going swallowed without critique." You characterize that as unfair somehow.

Companies A and B couldn't come to agreement to license something under terms Y that include $X in payment. Okay. There's neutrality in that statement. My comment says that (and no more).

What let's not do is say, "That makes company B a bunch of jerks." That is what the comment I'm responding to does, and it exists in a sea of others with the same tack.

Overton window and that.

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by azakai on Sunday June 28, 2015 @01:07PM (#9794180)
You said

> So what we're really talking about is that Unity wants the improvements that have been made to Mono, but doesn't want to pay for them.

which paints Unity as the bad guy, when for all we know, it might not be. Perhaps Unity is totally OK with paying for a license, but the Xamarin terms would have bankrupted it.

But thank you for clarifying what you meant. I agree there is no point in saying either party is the bad guy, since there is not enough public information to know.

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by carussell on Sunday June 28, 2015 @01:15PM (#9794213)
> which paints Unity as the bad guy

In what way at all? Entity A doesn't want to pay entity B $X. That's the only thing the comment of mine that you quote says.

There are shops around that sell quadcopters for hundreds of dollars. I want a quadcopter. I don't want to pay hundreds of dollars. Have I just painted myself as a bad guy?

I repeat: the only reason my comment sounds pro-Mono is because, at neutral, it resists the spin of the one that paints Unity as a victim and Mono as a fiend.

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by azakai on Sunday June 28, 2015 @01:45PM (#9794309)
"X wants Z, but doesn't want to pay Y for Z" implies several things. Perhaps you didn't intend them. But almost every reader will make those assumptions.

In particular, it sounds like Y is offering Z at a standard rate, as in "Sam wants a Chipotle burrito, but doesn't want to pay Chipotle for the burrito." Sam doesn't look good here - does Sam expect to get the burrito for free? Why does Sam think he is entitled to that?

Readers may not realize that there isn't a standard, objective rate for commercial licenses for Mono. Especially for the single biggest consumer of Mono, Unity, which uses it in products that its customers ship - a particularly complex situation.

Again, maybe you didn't intend to, but it sounded like you were saying something very negative about Unity. A less biased way to say it might be

"Unity and Mono could not arrive at mutually acceptable terms for Unity to license newer versions of Mono."

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by carussell on Sunday June 28, 2015 @02:07PM (#9794388)
The only thing I'm saying are very negative things towards people who read (or heard the story of) Unity's PR-level attempt to make it sound like the people behind Mono are jerks, and then bought in to it full force and now repeat the line at every opportune moment (and then some inopportune ones, too, like the comment I replied to).

What we also don't know are the terms for the first negotiation. It's as possible that Mono made one offer and Unity countered with an insultingly lower one, then Mono accepted due to being a poor position to negotiate something "reasonable", but are no longer in a position to have to accept whatever is offered, now that Xamarin is off and running.

We don't know. Hypotheses non fingo.

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by felixgallo on Sunday June 28, 2015 @12:43PM (#9794109)
I'm aware of the terms, and they were ridiculous. Unfortunately, I can't disclose them, but they didn't make sense, and that's why Unity is on the path it's on now.
Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by azakai on Sunday June 28, 2015 @12:18PM (#9794022)
.NET's cross-platform support is still a work in progress. In particular, it doesn't have a web port, which is crucial for Unity. il2cpp is an AOT compiler to C++, which makes it trivially portable to practically everywhere, including the web, and unlike a VM there is no need to write a JIT for a new CPU, no need to port a runtime to a new OS, etc.

AOT-compiled code can also be very fast. I'm aware .NET has options there too, but il2cpp is literally focused on doing just that, and doing it very well.

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by justthistime_ on Sunday June 28, 2015 @12:31PM (#9794061)
Seriously?

The same people who couldn't maintain their fork of Unity are now writing their own home-grown runtime, complete with their own garbage collector.

I don't see a chance of this working out "well" for any sane or bizarre notion of "well".

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by natosha_bard on Sunday June 28, 2015 @01:20PM (#9794222)
il2cpp has advantages other than licensing (Mono is indeed open-source, but it is LGPL so it can only be used on platforms that comply with the LGPL; Unity runs on various non-LGPL platforms). il2cpp combines ease-of-use (C#) for Unity developers with native (C++) performance. What's not to love about that? :-P
Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by justthistime_ on Tuesday June 30, 2015 @04:52PM (#9808352)
Seriously?

The same people who couldn't maintain their fork of Unity are now writing their own home-grown runtime, complete with their own garbage collector.

I don't see a chance of this working out "well" for any sane or bizarre notion of "well".

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by reitzensteinm on Sunday June 28, 2015 @11:51AM (#9793924)
I was hoping for a switch to Microsoft's .Net, which would enable use of Arcadia (Clojure in Unity3D) for serious/big tasks.

Right now, the GC performance of Unity is horrible relative to what you'd get on the JVM and there's no reason to believe IL2CPP is going to be any better.

When you don't have a generational collector, you have to seriously constrain your allocations, crimping your immutable style.

The Unity roadmap suggests they're going ahead with a Mono upgrade (I believe they dynamically link every platform sans iOS):

http://unity3d.com/unity/roadmap/

So it's probably not on the cards (no pun intended). However, the Mono upgrade will bring a generational GC to the platforms on which it's usable (which will fall somewhere on the spectrum of Editor, PC, !iOS).

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by jebblue on Sunday June 28, 2015 @12:29PM (#9794054)
I helped build a web service product that ran on Mono in the early 2000's back when I was still also a Windows dev but with the significant improvements over the mid to latter 2000's to the speed and stability of the JVM I dare say (and consider Mojang's success) the JVM would be a better choice for future game engines than Mono. With so much work having gone into using Mono I doubt it would be changed to the JVM but also Microsoft to their credit is open sourcing some/a lot? of the .NET runtime to open platforms like Linux.

The only problem I have with Mono today is Miguel's decision to completely disrespect and disregard the Linux Desktop: http://tirania.org/blog/archive/2012/Aug-29.html

Re:Porting the Unity Editor to Linux: Stuff I Wish We’d Done... by GFK_of_xmaspast on Sunday June 28, 2015 @08:38PM (#9795788)
That blog post is correct tho?