News for hackers. Stuff that matters.
Re:Closed Source Engines Are a Big Risk by flipgimble on Friday September 16, 2016 @11:43PM (#12519017)
I fully agree with the author about the risk of Unity as a closed source engine.

Unity isn't just closed source, but your main access to the engine is through an ancient Mono .NET environment that hasn't been updated in years due to licensing issues. The latest re-licensing of Xamarin should help here, but as with many other features Unity will be afraid to make upgrades for fear of braking compatibility.

This means that most of the Unity game code that will set your game apart has to be written in C# 3.0, and your memory use and performance is heavily taxed, unless you resort to platform specific native plugins. As a game developer this scales down your ambition down to mostly casual games. The type of AAA games that Unity advertises are mostly distinguished by large amount of content, but nothing innovative in gameplay or technology besides what the engine provides. I can't imagine anyone starting a No Man's Sky or even a next Minecraft in Unity.

This is sad, because about 5 years ago I was cheering for Unity and having a lot of fun with some prototypes. They know they are a mill for casual clone games too, since they are shifting their business focus to online developer services like advertising and multiplayer hosting with per-player fees.

Re:Closed Source Engines Are a Big Risk by notoes on Saturday September 17, 2016 @07:06AM (#12520028)
The Mono compiler has been upgraded recently: http://forum.unity3d.com/threads/upgraded-c-compiler-on-5-3-...
Re:Closed Source Engines Are a Big Risk by bluesilver07 on Saturday September 17, 2016 @08:59AM (#12520302)
But this is just initial step and doesn't add any new language features.

From the link:

  The Mono runtime we use in our Editor and Players has not been upgraded.
  The compiler still targets the C# 4 language. This is approximately what our old compiler supported.
  The compiler still target the .Net 3.5 framework profile we previously supported.
Re:Closed Source Engines Are a Big Risk by bluesilver07 on Wednesday September 28, 2016 @07:47AM (#12596939)
Re:Closed Source Engines Are a Big Risk by jackmott on Saturday September 17, 2016 @10:12AM (#12520549)
.net 4.6 and runtime and gc upgrades are all in the pipeline. but that doesnt help anyone right now.
Re:Closed Source Engines Are a Big Risk by douche on Saturday September 17, 2016 @12:41AM (#12519152)
Microsoft really ought to buy Unity. Selfishly, it might prod them along to expand their .Net Core (or whatever they are calling it this week) offerings further.

XNA used to sit in this space, and it was a pretty nifty little game development platform for C#. Monogame has carried on, and expanded the target platforms nicely, but hasn't really made many other improvements, from what I've seen, getting back into it after a few years away.

Re:Closed Source Engines Are a Big Risk by Fr0styMatt88 on Saturday September 17, 2016 @02:25AM (#12519405)
It's unfortunate but Unity is a prime example of what technical debt can do to a product it seems.

https://feedback.unity3d.com/suggestions/change-font-size-in...

http://forum.unity3d.com/threads/when-will-unity-support-hig...

Re:Closed Source Engines Are a Big Risk by izym on Saturday September 17, 2016 @07:37AM (#12520100)
I'm not quite sure how those two threads indicate technical debt. Could you elaborate?
Re:Closed Source Engines Are a Big Risk by loup-vaillant on Saturday September 17, 2016 @08:19AM (#12520202)
First thread is asking for a simple fix ("change font size" feature), that would really improve the usability of the editor. It has not been done for 7 years, which suggests that it's not an easy fix at all. It should be.

Second threads ask for support for high DPI. It's a simple scale issue, but somehow hard to do it on Windows.

Stuff that should be easy but isn't is a strong indicator of technical debt.

Re:Closed Source Engines Are a Big Risk by user5994461 on Saturday September 17, 2016 @05:40PM (#12522613)
> Stuff that should be easy but isn't is a strong indicator of technical debt.

It can also be an indicator that there is noone working on it. It's common to have fix which are relatively easy but noone to implement them.

Re:Closed Source Engines Are a Big Risk by loup-vaillant on Saturday September 17, 2016 @07:01PM (#12522985)
Doesn't apply to obvious wins such as variable font sizes or high DPI. Those items are necessarily high priority, because of their low hanging fruit nature.

Or, they just get their priorities wrong, meaning, they're being stupid. Not a safe assumption in my opinion.

Re:Closed Source Engines Are a Big Risk by user5994461 on Saturday September 24, 2016 @10:29AM (#12571057)
font sizes and high DPI are far from trivial changes.

> Or, they just get their priorities wrong

Most open source projects have very few or no people working at all. It's common to find bug reports opened for years that were never fixed. They don't have to be complex, just non-trivial.

Re:Closed Source Engines Are a Big Risk by Fr0styMatt88 on Saturday September 17, 2016 @08:57AM (#12520296)
Yeah, I should have explained a bit better but that's exactly what I was getting at with those two links.