UnityScript to begin phase-out with 2017.2

[Schneider21]

From today’s blog post:

As of the beginning of June, we have amended the Asset Store submission policy to reject packages that contain UnityScript code. All new code that you’re writing for Asset Store packages should be in C#.

The Unity 2017.2 beta no longer has a ‘Javascript’ (a.k.a UnityScript) option in the Create Assets menu.

We have begun work on a UnityScript → C# automatic conversion tool.

Once we’re content that the usage level is low enough, Unity will no longer ship with the UnityScript compiler, and will no longer recognise .js files as user script code. We’ll also remove the UnityScript examples from the documentation, and remove UnityScript support from the Script Updater.

The removal of UnityScript support will also mean the final removal of the Boo compiler. At this point, only 0.2% of projects on 5.6 contain any .boo files, and only 0.006% of projects have more than 3 boo files in.

I think it’s about time. But also smart to phase it out slowly so as to not just break the projects of those still using it.

[Ryiah]

Awesome. I had been checking daily for the announcement, with the last time only an hour ago, so they must have only just put the blog post up. My favorite part of it is the actual breakdown of the percentages. Before we were told only about one-fifth of the developer base were using UnityScript.

https://blogs.unity3d.com/2014/09/03/documentation-unity-scripting-languages-and-you/

If we work on the assumption that they were determining the percentage of the users based on a single US file in the older blog post then I think it’d be safe to say that they likely could have removed it a long time ago. They just didn’t have an actual reason until they started bringing out a new compiler and framework.

Either way the new blog post is getting bookmarked for future reference and linking to new developers who have or are interested in picking up UnityScript. With 2017.2 having the ability to create them removed though it shouldn’t be necessary for much longer.

[LaneFox]

Again: we’re sorry, but its time has come.

[orb]

@Schneider21

also smart to phase it out slowly so as to not just break the projects of those still using it.

It’s already been slowly phased out, but you didn’t notice because you were smart enough to use C#. They’d already stopped making tutorials using UnityScript long ago

Ding, dong, the witch is dead!

[Kiwasi]

Bye-Bye UnityScript.

In a weird way I’ll miss the language once it’s gone. It was alway good for starting holy wars.

[neginfinity]

@Schneider21

From today’s blog post:

I think it’s about time. But also smart to phase it out slowly so as to not just break the projects of those still using it.

Now the only thing left is to add bindings for C++ …, Python, Common Lisp and Prolog and we can live happily ever after.

[orb]

@neginfinity

Now the only thing left is to add bindings for C++

Dropping in C++ MonoBehaviours the same way C# works has actually been considered as a possibility

[Schneider21]

@Kiwasi

In a weird way I’ll miss the language once it’s gone. It was alway good for starting holy wars.

We’ll always have the comparisons to Unreal’s lighting and why-is-the-dark-skin-not-included-in-free threads for that.

[orb]

@Schneider21

We’ll always have the comparisons to Unreal’s lighting and why-is-the-dark-skin-not-included-in-free threads for that.

Plus the number of spaces a tab represents, whether to use spaces or tabs in the first place and the glory/filth of singletons.

[LaneFox]

@orb

Plus the number of spaces a tab represents, whether to use spaces or tabs in the first place and the glory/filth of singletons.

Don’t forget bracket formatting.

[orb]

@LaneFox

Don’t forget bracket formatting.

A cause of many physical injuries.

[SaraCecilia]

Hey all, we would appreciate all feedback around this directly to our Scripting team. We’ve started a thread here.
Thanks!